Networking Problem

[BaldEagl]

I've got a networking issue and for the life of me I can't figure it out.  My network consists of:

Gaming Desktop (Win XP - wired to router) - No shared files

Old Desktop (Win98 - wired to router) - Shared storage drive, shared external drive, shared printer

Laptop (Win98 - wireless to router) - Shared storage drive

Network Printer (wired to router)

From my gamig desktop I have access to the old desktop's shared resources through network neigborhood.  I can read and write to the old desktops shared drives and have access to it's printer and to the network printer.  The laptop never shows up in network neigborhood but I can locate it using find computers.  I can read and copy from it's shared drive but can't write to it even though it is set for full access.

From my old desktop I can see my gaming laptop in network neighborhood and have access to the network printer.  The laptop never shows up in network neigborhood but I can locate it using find computers.  I can read and copy from it's shared drive but can't write to it even though it is set for full access.

From my laptop I can see my old desktop in network neighborhood but have no access to the shared files (when I double click on it I get a "file or share name cannot be found" message).  I cannot even locate my gaming computer using find computers.  I do have access to the network printer.

Any ideas what I have messed up?  They are all set up for file/print sharing and the drives/printers I listed are set for sharing at full access.  All three machines are running versions of McAfee firewall but settings are the same among them.  I tried turning McAfee firewall off on all machines with the same results.  I'd really like read/write access to both the old desktop and the laptop since they are in different rooms.

Thanks

[Fulmar]

What did they say about Windows 98 on South Park?

sorry I'm no help

[1701E]

This can at times be cause by conflicting hardware, although rare.  One thing to check: Make sure all computer have the same Network Protocols. If one is using an older Protocol, it will limit access from other computers, and remove all access to newer versions of the protocol on the network.

[[Network connections>View network connections>[Network used] right click>Properties>Install>Protocols]] it is best to install the newest of everything available.  I wouldn't suggest installing anything but the protocols as the "Client and "service" can cause some other annoying problems (not sure how it ties in but one removes the normal log-in screen).  Make sure they all have the same things installed.

If this isn't it, I am out of idea, but this is what I have learned in my network adventures.  I had this same trouble not long ago, we have a network consisting of 6 computers, and 2 printers.

[Ghosth]

Might be something as simple as having different "workgroup" names.

Sounds like its probably something simple that your missing.

[WilldCrd]

What type of router are you using?e  as stated above it could be the names of your workgroup or that they arent all in the same workgroup

[Denholm]

Have you tried installing NetBIOS on the two 98s and the XP? I heard that particular protocol increased compatibility between 2000's + with Win 95's and 98's. You should be careful, though. Enabling NetBIOS allows people outside of your network unprecedented access to your shared files. You might consider adding password authentication to your computer's shared files.

[TilDeath]

Make sure to have the same user name and password on each machine

[BaldEagl]

My workgroup names are all the same.  Apparently, as soon as you set file and print sharing it enables NetBios in at least specific protocols (the I want to enable NetBios check box is checked and greyed out).

I've got a Linksys router and I'm using 128 bit encryption for wireless access.  In the site survey it shows it as secure.

I did manage to map the laptop drive to my old desktop and using the re-connect at logon option it's shared drive is in my drive list but i still can't write to it.

I haven't set up a domain or network logon.  I'm using the Microsoft Family Logon.  I was hoping to not have to type user names and passwords all the time thinking that as long as all access was through a secure router I'd be ok.

The only thing I can think of is that the router firewall is somehow blocking certain network functionality for the laptop but I can't see where in the router set-up I could change anything to make it work.  I tried a few things last night to no avail.

I really am baffled by this one. 

[Irwink!]

You may need to edit a "hosts" file for each machine, adding the name and tcp/ip address of each machine in the network, in the absence of a WINS or DNS server to locate different computers in your home network. Google "netbios tcp/ip hosts file" or some similar search. It's been awhile since I tried to mingle W98 machines in a network.

Edit: This is a start:  http://support.microsoft.com/kb/102725

[BaldEagl]

I got it to work!!!!!

After almost 10 hours between last night, and today I finally got it all working as I'd like.

Here's how simple the fix was; instead of typing in the computer name under find computers I typed in the IP addresses and there they were.  Then I used map network drives typing in the IP addresses and the share names instead of using the computer names and share names and it mapped them perfectly allowing full read/write access.

Thanks for the suggestions.  I am so happy. 

[Denholm]

...I haven't set up a domain or network logon.  I'm using the Microsoft Family Logon.  I was hoping to not have to type user names and passwords all the time thinking that as long as all access was through a secure router I'd be ok...

I know you have your issue resolved (congratulations), however I wanted to take a moment to let you know about this one. No, you are not safe behind that router if you have NetBIOS enabled. NetBIOS can be helpful yet is a massive security flaw if your system is not password-protected (including users attempting to access your system from the network). I am quite serious in this, I actually tested it on my system. I enabled NetBIOS, went to someone else's computer (not on my network or connected to my router), made a special file which added my computer as a mapped drive, and logged into my C:\ drive (Win 2000 flaw, C is shared by default). Thankfully I require any user to authenticate themselves before logging on, so NetBIOS isn't much of a security risk for my system, yet it is still disabled.

[BaldEagl]

I still haven't set up a domain or network logon but I have set passwords individually for each shared resource.  Of course once I have them open on each computer they are open.

[715]

How do you set up passwords for shared folders without setting up a Domain?  I have just a Workgroup network and I don't see any way of requiring a password for shared folders.  [Edit]Nevermind- found it (you have to clear "Use Simple File Sharing" in Folder View options).

Also, how can someone outside your router get through its firewall and into your shared folder?  Wouldn't the firewall ignore such an external request?

[BaldEagl]

How do you set up passwords for shared folders without setting up a Domain?  I have just a Workgroup network and I don't see any way of requiring a password for shared folders.  [Edit]Nevermind- found it (you have to clear "Use Simple File Sharing" in Folder View options).

I didn't do that.  Just right click on the shared resource, click properties and under sharing assign a pssword.

[715]

I didn't do that.  Just right click on the shared resource, click properties and under sharing assign a pssword.

That's weird.  With "Use Simple File Sharing" selected I get no option for passwords under the Sharing Tab.  With "Use Simple File Sharing" deselected (Folder Options, View, Advanced Settings) I get a very complex set of permissions, groups, etc that appears to be valid for Domain not WorkGroup networks.  I guess this is because it's XP not 98.  I guess the safest thing to do is set up a Domain, but that looks mind numingly difficult, so I'll just continue with the "unsafe" WorkGroup.