home network headaches

Steve-O · Post by **Steve-O** » Tue Dec 30, 2003 7:43 pm

When I first got a DSL router, I connected three computers via LAN. One was Windows XP, the other two Win 98. Everything worked fine until I bought a new computer. When trying to install a network through the XP wizard, it always comes up with a "bridged connection". Well I never had a bridged connection before, nor do I desire one now. Does anyone know how to get around this using the Win XP network creation wizard? BTW, the two Win 98 PCs have Linksys LNE 10/100 NICs and the XP machine has internal Gigabit LAN. When querying the router, the DHCP client list shows all the computers, but no computer can browse the network. Thanks in advance, it may take me awhile to get back up to speed on the network jargon, so please be gentle

qball15j · Post by **qball15j** » Tue Dec 30, 2003 8:20 pm

You don't really need to run the networking wizard just go to your TCP/IP properties and make sure obtain IP address and DNS automatically.

Also make sure your workgrup is set the same as the rest of the computers on the network. Right click on my computer>properties>Computer name tab... Your workgroup will be displayed. If it's the same as the rest of them don't worry about it, if it's different click change...

Hopefully the information I provided helps you. If you have any questions just ask.

Steve-O · Post by **Steve-O** » Tue Dec 30, 2003 9:32 pm

Thanks qball for a speedy reply. I changed the workgroup name that XP installed by default (MSHOME) and was able to see the other Win 98 machine that was up and running. I went to that Win 98 machine and tried to look back at the XP machine, but could not browse the network. I verified the items in your post on the 98 machine and noticed that one of the devices under network properties did not have MS Family Network and File and Print Sharing loaded. I added these, restarted the 98 machine and was able to browse the network and see the XP machine. So far, so good. However, when I tried to access the XP machine from the 98 machine, it asked for a password. I entered the same password we have always used but it said "incorrect password". When accessing the 98 machine from the XP machine, the same password allowed access. Since I have never set a password from the XP machine, any ideas on why the 98 machine cannot access the XP machine due to a password anomaly? Thanks in advance...

qball15j · Post by **qball15j** » Tue Dec 30, 2003 9:50 pm

To make thing easy for a home setup just enable the guest account on the XP machine. It's under users in the XP control panel. You should see enable guest account or somthing like that when you click on it. I don't really remember XP Home that well but I beleive that's right.

Steve-O · Post by **Steve-O** » Tue Dec 30, 2003 10:26 pm

OK, thanks, but I was able to resolve it another way. I really feel dumb for not finding this sooner. The 98 machine could not access any files on the XP machine because none were shared yet! It's a new OS install due to a new motherboard and I haven't yet shared any folders. So I went to the XP machine and shared one folder and sure enough, I was able to access it from the 98 PC. Now here's where things stand. I can browse the network and see all three computers from both the XP PC and the 98 PC and access files to and from both these machines. However, the third computer is a 98 laptop and even though the other two can see it and access it, it's a one-way deal. The 98 laptop cannot browse the network at all. I set the laptop beside the 98 desktop and compared and verified all network devices, services and protocols. Everything is identical except of course for the laptop having PCMCIA devices. It's getting late here and I'm heading off to bed. I'll check for any updates tomorrow. Until then, thanks for your advice, qball. You got me up and running on 2 of 3 machines. I appreciate it. Later...

qball15j · Post by **qball15j** » Tue Dec 30, 2003 11:03 pm

Try restarting the laptop. You can also type \\COMPuTERNAME\ in the addres bar of any window to see the shares on the other system. That's a simple work-around.