Forum Home
Press F1
 
Thread ID: 55050 2005-03-01 09:44:00 TCP/IP issue - very frustrating nzsp (6931) Press F1
Post ID Timestamp Content User
329310 2005-03-01 09:44:00 I have a problem trying to set up my home network. I have two PC's going into my Telecom Nokia ADSL modem/router. Both running XP SP2.

I have set up the network with the XP wizard on both computers. One can see the other computer fine including shared folders (but cannot access the folders). The problem is with the other PC. I think I have traced it back to the network controller. Using the ping command I cannot ping the local computer. According to Microsoft help that means I have to reset the TCP/IP protocol stack. I did that but no luck.

I have no problem accessing the internet through the modem.

I am using the nvidia network controller on my Gigabyte GA-K8NF-9 motherboard, with the latest driver from the Gigabyte website. According to the device manager it is working fine.

I am stumped where to go from here. If I can get the local network controler working I think the network should fall into place. Should I consdider a nerwork card?

Any ideas? 		nzsp (6931)
329311 2005-03-01 09:47:00 On the computer that is having problems, do two things:

1) ping localhost
2) ping 127.0.0.1

If either fails, (more importantly if the bottom one fails) you have a hardware issue.

3) Reset CMOS - this usually involves removing the power, removing the onboard battery and switching a jumper for about 10 seconds, then putting the battery back and replacing the power - it should be outlined in your user manual.

This will take care of hardware issues - then you can look at the network setup.

/Edit: If things are playing up, and aren't acting as they should, then definitely consider a network card -they're so cheap it shouldn't matter.

Also, type ipconfig on each PC in Start -> Run -> cmd, and tell us the result :D 		Growly (6)
329312 2005-03-01 09:56:00 "ping localhost" works OK
"ping 127.0.0.1" works OK

ipconfig gives:

IP address: 192.168.1.2
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.254


"ping 192.168.1.2" times out 		nzsp (6931)
329313 2005-03-01 09:58:00 Firewall, what are you using, have you allowed the connection on both PC's?

Still no luck, cables ok, ditch the XP networking wizard and set them up manualy via Control Panel > Network Connections > Properties >Network Adapter TCP/IP Properties > (for sharing internet) set the Gateway in both PC's to your routers IP (say 192 . 168 . 1 . 1 or whatever your router is set to), give each PC a it's own IP (say, 192 . 168 . 1 . 2 & 192 . 168 . 1 . 3), subnet in both is 255 . 255 . 255 . 0, put your ISP's DNS numbers in the field provided > Click OK, OK, OK . Now check out the PF1 Networking FAQ on sharing folders and permissions, make sure your firewall is configured to allow the network .

Come back if you have any problems or queries . 		Murray P (44)
329314 2005-03-01 09:59:00 What are the settings on the other device?

Firewalls? 		Chilling_Silence (9)
329315 2005-03-01 10:02:00 Further info:

1) XP firewall is off on both PC's

2) on the "OK" computer I have McAfee firewall, but as I can see the whole network from there it should not be getting in the way

3) On the "problem" PC I have Norton firewall configured to have the network in the trusted zone

I will have a try at the manual approach 		nzsp (6931)
329316 2005-03-01 10:07:00 Murray,

Can you confirm where I find the ISP DNS server number

Cheers 		nzsp (6931)
329317 2005-03-01 10:24:00 "ping localhost" works OK
"ping 127.0.0.1" works OK

ipconfig gives:

IP address: 192.168.1.2
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.254


"ping 192.168.1.2" times out

Usually indicates that a firewall is preventing communication. Temporarily diasble ALL firewalls and try again. If the PC IP address 192.168.1.2 then you should be able to ping it unless a firewall prevents the ping on the port.
Maybe you are running something else that has closed off IP ports 		Big John (551)
329318 2005-03-01 20:20:00 the other way is to simply don't use tcp/ip for the lan. install ipx/spx, set the frame type type to 802.3 on both and your away (don't forget to turn netbios off for tcp/ip). tweak'e (69)
329319 2005-03-01 21:39:00 Big John,

Thanks for that idea - I tried that already but with no luck. I will double check tonight, but that is what led me to thinking it was a network controller issue.

How can I check for other programs other than firewalls that might be closing the ports?

Cheers 		nzsp (6931)
1 2 3