Stickie
asked on
ping timeout
I have 2 computers which are on a network. One is running on windows XP and the other on Windows 2000. My problem is that as soon as both of them are connected to a server they both timeout. I tried disabling any firewalls but no luck. Any ideas? I have a 2mb dsl connection
thanks
thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
OK, now ipconfig /all from the other machine please
what firewall(s) are installed on each?
and as sirbounty asked
what is it you can't ping, the server, each other or both?
and as sirbounty asked
what is it you can't ping, the server, each other or both?
May help to get the server ipconfig info as well...depening on your answer to the above...
ASKER
When one computer is connected to a server its fine but as soon as the other computer joins the same or any other server both timeout and my latency spikes.
Here is info for the other comp
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Asif>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
C:\Documents and Settings\Asif>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : khan
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adap
ter
Physical Address. . . . . . . . . : 00-0E-A6-52-89-D9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : January 8, 2005 11:08:56 AM
Lease Expires . . . . . . . . . . : January 15, 2005 11:08:56 AM
Here is info for the other comp
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Asif>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
C:\Documents and Settings\Asif>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : khan
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adap
ter
Physical Address. . . . . . . . . : 00-0E-A6-52-89-D9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : January 8, 2005 11:08:56 AM
Lease Expires . . . . . . . . . . : January 15, 2005 11:08:56 AM
OK, I think I understand the problem
when either is connected alone, all is cool, but when you connect the other, then the problem arises?
sound like a broadcast storm
now we need to isolate it
first connect kahn
and run it and see, then while it's conencted connect the other one and see if the problem arises
then shut down both
reboot and connect the other one and run it, and then connect kahn and see
let us know
You could also get ethereal
www.ethereal.com
free packet sniffer (you will also need wincap, also free)
install on both machines
and capture some packets when both are connected
I also advise scanning for sumware with some of these tools
spybot
http://patrick.kolla.de/spybotsd.html
PestPatrol
http://pestpatrol.com/
ad aware
www.lavasoft.de
CoolWebShredder
http://www.spychecker.com/program/coolwebshredder.html
BHO demon
http://www.definitivesolutions.com/bhodemon.htm
Download HijackThis v1.98.2 from here, run it and Save the log file:
http://tools.radiosplace.com/HijackThis.exe
Then Post that log at this site
http://www.hijackthis.de/en
click analyze
then check anything marked as nasty and click fix
new tool (beta)(originally GIANT)
http://www.microsoft.com/athome/security/spyware/software/default.mspx
free and is proactive
will scan and then help protect
scumware can cause these storms
when either is connected alone, all is cool, but when you connect the other, then the problem arises?
sound like a broadcast storm
now we need to isolate it
first connect kahn
and run it and see, then while it's conencted connect the other one and see if the problem arises
then shut down both
reboot and connect the other one and run it, and then connect kahn and see
let us know
You could also get ethereal
www.ethereal.com
free packet sniffer (you will also need wincap, also free)
install on both machines
and capture some packets when both are connected
I also advise scanning for sumware with some of these tools
spybot
http://patrick.kolla.de/spybotsd.html
PestPatrol
http://pestpatrol.com/
ad aware
www.lavasoft.de
CoolWebShredder
http://www.spychecker.com/program/coolwebshredder.html
BHO demon
http://www.definitivesolutions.com/bhodemon.htm
Download HijackThis v1.98.2 from here, run it and Save the log file:
http://tools.radiosplace.com/HijackThis.exe
Then Post that log at this site
http://www.hijackthis.de/en
click analyze
then check anything marked as nasty and click fix
new tool (beta)(originally GIANT)
http://www.microsoft.com/athome/security/spyware/software/default.mspx
free and is proactive
will scan and then help protect
scumware can cause these storms
ASKER
They can connect to eachother fine its just when i try to connect to another server. Basically only one can connect to a server if both connect to a server then it timesout.
Any servers with dual/multiple adapters?
Where's the dhcp server and how is it configured?
Where's the dhcp server and how is it configured?
ASKER
My dsl connection is dynamic
sirbounty
i was just connecting to random servers
sirbounty
i was just connecting to random servers
You mean connecting to servers over the internet?
what router are you using?
internet ---modem----router----pc's
what router are you using?
internet ---modem----router----pc's
I thought this was a lan problem :-)
ASKER
It was a lan problem but then i resolved it, the dsn ip was wrong. As for the server issue i also fixed that. I had to create a new port for each computer and now it works fine.
ASKER
thanks guys i couldnt of solved my problem without your help
Glad it's working, and thanks!
ASKER
Do i have do that to both computers?
stevenlewis
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\assif>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : bss-v1d05qsiwkj
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0D-87-54-8B-9A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Saturday, January 08, 2005 10:19:14
AM
Lease Expires . . . . . . . . . . : Saturday, January 15, 2005 10:19:14
AM