Windows XP SP2, "Limited or no Connectivity"

[JetKit]

I am currently trying to network 2 pc's directly, and am unable to repair connections or view either PC. Each of which has there own dial up connection.In the taskbar I get the Network Icon With an exclamation mark ("Limited or no Connectivity")I have installed Update KB884020 and tried running WinsockXPFix.exe, and using both static and dynamic IP addresses, but none of this has resolved my problem.When I attempt to ping a pc I get the response"Request Timed Out" I have disabled the firewalls on both pc's (Windows and ZoneAlarm). And this has had no effect. Please Help One of the PC's is running Windows XP Pro SP2, and the other Windows XP Home SP2.What Can I do??

[bAdWaYz]

When you say that "Each of which has there own dial up connection." do you mean that both dial up in order to get an internet connection? Also what are you trying to do with these computers? Do you want to share the dialup connection between the two or just share files/folders between them? Knowing this will help us to better point to a fix that fits what you want to do.

[JetKit]

I want to be able to share files/folders and also network gaming between the two. There is no need to share the intyernet connection, as they are set up to individuall dial the internet as required.

[z1p]

Your best bet is to configure each PC with a static IP address (let's say 192.168.1.10 an 192,168,1,20). Also, make sure that you are using a crossover cable NOT a patch cable. Once you do that try to ping each PC (open a command window and run 'ping 192.168.1.10' replace the IP with the IP addresses that you use. Once ping is working, you have the TCP/IP network working and you can go on to setting up the windows networking and file sharing.

The starting point for file sharing is:
make sure netbios over TCP is installed.
make sure both PCs are in the same workgroup
make sure that the 'computer browser' service is running on each PC
enable sharing

Try this as the starting point and let us know how it goes. If things are still not working we can take it from there.

PS.

If your pings fail post the output of ipconfig/all and netstat -rn. This will show us your IP configs and routing.

[JetKit]

I am Using a Crossover Cable (Which has worked on other PC's). And have ensured the "Computer Browser" Servise is enabled. The two PC's will still not connect. Below is a copy of what IPconfig brought up on both PC's

PC 1) WINDOWS XP PRO SP2

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Chris>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : CHRIS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-05-1C-1F-6D-27
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : ?
?
?
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled


PC 2)WINDOWS XP HOME SP2


C:\Documents and Settings\RhysD>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Rhys
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810X Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-20-ED-6E-6C-BC
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : ?
?
?
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

[z1p]

Your IPv6 doesn't seem to be configuring correctly. You shouldn't really need it, so I'd remove it and see if things get better. You can find it under protocols for each interface. If you still have problems, post the output of 'net -rn'. I'd like to see how your PCs think they should be sending out packets for your local IPs. In the netstat output you should see a line something like this on the PC with 192.168.1.10 IP:

192.168.1.0 255.255.255.0 192.168.1.10 192.168.1.10 20

If it is not there I can tell you how to add the route manually...

[JetKit]

I hve removed IPv6. Still no response from other PC. "netstat -rn" output is as follows:

PC 1)


C:\Documents and Settings\Chris>netstat -rn
Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 05 1c 1f 6d 27 ...... Realtek RTL8139/810x Family Fast Ethernet NIC -
Packet Scheduler Miniport
0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 210.55.86.118 210.55.86.118 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.10 192.168.1.10 20
192.168.1.10 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.10 192.168.1.10 20
192.168.9.237 255.255.255.255 210.55.86.118 210.55.86.118 1
210.55.86.118 255.255.255.255 127.0.0.1 127.0.0.1 50
210.55.86.255 255.255.255.255 210.55.86.118 210.55.86.118 50
224.0.0.0 240.0.0.0 192.168.1.10 192.168.1.10 20
224.0.0.0 240.0.0.0 210.55.86.118 210.55.86.118 1
255.255.255.255 255.255.255.255 192.168.1.10 192.168.1.10 1
255.255.255.255 255.255.255.255 210.55.86.118 210.55.86.118 1
Default Gateway: 210.55.86.118
================================================== =========================
Persistent Routes:
None
C:\Documents and Settings\Chris>

PC 2)


C:\Documents and Settings\RhysD>netstat -rn
Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 20 ed 6e 6c bc ...... Realtek RTL8139/810X Family Fast Ethernet NI
C - Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.20 192.168.1.20 20
192.168.1.20 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.20 192.168.1.20 20
224.0.0.0 240.0.0.0 192.168.1.20 192.168.1.20 20
255.255.255.255 255.255.255.255 192.168.1.20 192.168.1.20 1
================================================== =========================
Persistent Routes:
None
C:\Documents and Settings\RhysD>

[z1p]

jet, sorry I disappeared for a bit, but work has gotten a bit crazy...

your default route seems off. It has a metric of 1, so traffic will be routed out there....

What is the 210.55.86.118 IP, the IP you got for dial up?
did you do the netstat while dialed out? It shouldn't be getting a metric of 1?

Check out this link for M$ site (http://support.microsoft.com/default...b;en-us;299540). I'm not familar with this feature myself and I don't have a XP mahine here to look at it, but it might be the problem. Check what the metric settings are for your dialup connection. According to the the KB, a dialup should have a metric of 50. Actually the lowest metric it shows is 10, so I don't know where the 1 is coming from.


UPDATE:
Just saw this page (http://www.help.perle.com/index.asp?a=4&q=200). I guess the default route for PPP normally gets set up with a metric of 1. Look at this to see how to define a static route for your LAN and set its metric to 1. Let me know if this helps. Use the -p option for route so that the route will persist.

[JetKit]

This is how "netstat -rn" reads whil not connected to dial up



C:\>netstat -rn
Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x40002 ...00 05 1c 1f 6d 27 ...... Realtek RTL8139/810x Family Fast Ethernet NI
C - Packet Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.10 192.168.1.10 20
192.168.1.10 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.10 192.168.1.10 20
224.0.0.0 240.0.0.0 192.168.1.10 192.168.1.10 20
255.255.255.255 255.255.255.255 192.168.1.10 192.168.1.10 1
================================================== =========================
Persistent Routes:
None
C:\>

I tried "route add 192.168.1.10 192.168.1.10" Gave Metric value of 1, but didnt solve my problem

[z1p]

the routes seem fine, the IPs seem fine. You don't have a FW up. I'm starting to think a hardware problem. Your NICs are reporting problems. It may be time to try a new cat5 cable. If I'm following this correctly, you cannot ping either PC, correct?

[JetKit]

I have swapped one of the PC's. This seems to haev rectified the problem, So Im guessing a faulty ethernet card? Thank you very much for your time, I have learnt alot through this experiance.