networking configuration problem

A friend of mine got a D-Link router to hook up his two computers to the cable modem. As far as the internet goes everything is kosher. Both computers can surf the web and recieve email without any trouble.

He also wants to use one folder for images and MP3's and access it from both computers. This is where the problem comes in.

The upstairs computer (WinXP home) can see both computers in network places without any trouble and even pull shared files from the downstairs computer. It will also ping the downstairs computer without any trouble.

The downstairs computer however will not see anything in network neighborhood. The flashlight just looks around and eventually locks network neighborhood up. I can't ping the upstairs computer at all from downstairs. It just times out. I unistalled the protocols and network drivers on the downstairs computer and reinstalled everything, but it still won't work.

A side note is that I can ping the router (192.168.0.1) with no trouble from the downstairs machine.

If I ping the upstairs computer by using the computer name "ping darra" it will resolve the IP address "pinging darra [192.168.0.112] with . . . " but then the request times out. I would think that if it couldn't see the computer at all it would return would be "unknown host."

I recommended that he try a different network cable, and do an install in place of windows 98 just in case. Is there anything else I'm missing besides a possible re-format re-install??

could it be a bad cable even though the router works great sharing the internet and I can see both computers on the XP box and even download shared files from the 98 box?

I made sure both cables were plugged into ports 1&2 of the hub/switch side of the router.

[quote]Originally posted by kato2274:
<strong>
I made sure both cables were plugged into ports 1&2 of the hub/switch side of the router.</strong><hr></blockquote>

First off that shouldn't matter. I was actually gonna suggest that you try the 98 machine in a different port. Also make sure you have the latest drivers. I assume you are using the DHPC server from the router correct? If you are try setting static ip's for both computers. Another thing you might try instead of messing your tcp settings up (since they work fine right now with the internet) is install netbeui. Also make sure that both computers are on the same workgroup. Good luck.

Thanks for the reply. He's using the DHCP from the router and I agree with you about not screwing with the TCP/IP settings as it's working fine on the internet.

both computers are on the same workgroup, and the XP box can see them both from network places.

I didn't think the ports should matter, but he had them on like 2 and 6, and I've seen a couple switches where computers wouldn't show up unless you had them plugged next to each other.

I also thought about netbui and installed it on the win98 box. When I tried to install the protocol on the winxp box, but it didn't list netbui as a MS protocol when I tried to add a protocol. any one have any info on how to get netbui installed on XP.

just read some info online that states that netbui isn't an option in winxp home edition but it's available in professional. So I guess I'm going to have to help him figure this out with TCP/IP.

Why would they leave NETBUI out of the home version. Isn't NETBUI more of a peer to peer small network protocol? Seems to make more sense in the home edition to me.

Remove NETBEUI from the 98 machine.

Make sure BOTH Pc's use DHCP under the TCP/IP properties for the network card. Make sure they are on the same Workgroup. Make sure they have different computer names. Enter the routers properties and make sure both are leasing an IP.

Do not give the devices static IP's (except to test) unless you want to loose the internet conectivity.

I had the very worst problems getting 98 to speak peer to peer with TCP/IP and will never use it again. Still, this doesn't mean that 98 is at fault. Make sure to check the settings on the XP machine. It's made for networking whereas the 98 machine is not. My 2000 machines can often see things on a network where 98 can not.

Try connecting by clicking Start, Run, and type \\computername\shareddrivename to see if you can connect that way - or map a drive and see if that gets you what you need.

Try disabling the firewall option on the XP machine for the LAN connection.
Set up a local user on the XP machine to match the username on the 98 machine.

I don't get how this helps me. the win98 box can't see anything under network neighborhood. not even itself.

but for the sake of being thorough, can you give direction on how to disable the firewall (which is not needed anyway due to the router) and why would a user account under the win98 box be something I'd want to do? I'm not following the logic.

[quote]Originally posted by kato2274:
<strong>...and why would a user account under the win98 box be something I'd want to do? I'm not following the logic.</strong><hr></blockquote>

Well on win2k and XP you have to create an account in the username and password applet in the control panel to allow access to that user (kinda like a server). So let's say your 98 machine logs onto the network with "thebeast" for a username and "123456" as the password. You would have to go and create a user called "thebeast" on the XP (or 2k for that matter) system to allow it access to your shared resources (i.e. hd, printer) Hope that cleared things up. Cheers.

I was at work and didn’t properly read all of you posts before originally posting a reply – sorry.


Well, lets look at what you have here.

98 machine that cannot see itself or other computers on the network.

XP machine that can see all machine on the network and browse their files and can connect to Internet.
This confirms that the ports, cables, NIC’s and the router are fine and dandy. Also notes that the settings on the XP machine are most likely correct and do not need to be changed.

98 can ping the router but not other devices and can connect to Internet. It cannot see itself in Network Neighborhood and TCP/IP is the only protocol.
This would lead me to wonder if it is leasing an IP and I would do a WINIPCFG and then do a release and renew for the network card and see if it can renew. If it cannot then you have your problem and there is something wrong with way it is leasing it’s IP from the DHCP. If not, well – I am at a loss then.

As a side note, my neighbor who uses my network with a 98 machine could not see other machines on my network (2000) though I could see it(98) from them(2000) and may transfer files to it(98) from them(2000). I resolved an IP for the 98 machine with WINIPCFG and set up permissions on the 2000 machines so they had shared folders with permissions for the 98 machine logon. I enabled Windows Logon and had them log on to the 98 machine. I could then open a network connection via UNC (\\computername\sharename). To date I cannot see things through the Network Neighborhood and MS knowledge base has been fruitless for this issue. The only thing I can thing is that the Network Neighborhood in 9.x uses UDP signals out when you open the Network Neighborhood and looks for items on the network by referring to what is out there with a master browser list that is populated in a way I do not yet understand/know. Perhaps the 2000/XP architecture has no form of this old style of using UDP and the master browser to view other computers on a peer to peer network and thus the 98 machine just does not see it.

Can anyone else shed any light on this issue? I know it is not uncommon and have experienced it will several 98 machines on peer to peer networks.

[quote]Originally posted by Gollo:
<strong>

Well on win2k and XP you have to create an account in the username and password applet in the control panel to allow access to that user (kinda like a server). So let's say your 98 machine logs onto the network with "thebeast" for a username and "123456" as the password. You would have to go and create a user called "thebeast" on the XP (or 2k for that matter) system to allow it access to your shared resources (i.e. hd, printer) Hope that cleared things up. Cheers.</strong><hr></blockquote>

Thanks for clearing that up Stang.
I had troubles with the ADSL connexion earlier and couldn't reply.
As far as the XP firewall goes, it tends to screw a lot up in the network connections.
To disable it, go to the the advanced options under the network properties for your connection and uncheck the firewall box...might fix a few things for you Kato.

thanks guys,

I'll give this stuff a try next time I see him. It's nice to have a few more angles to work from.