S
Sly
Hi,
ISP -> Broadband modem -> D-Link DI-624
Computer 1 (C1) - WinXP Pro Wired
Computer 2 (C2) - WinXP Pro Wireless
Computer 3 (C3) - WinXP Pro (ASUS P5K Premium MB) Wired or wireless
Never had any connectivity problem with C1 and C2.
C3, my new computer, could never connect to the Internet. It is certainly
"connected" to the D-Link in static mode because I can browse C1 and C2
from C3. Here is what I have tried so far:
If I force a static IP (this works well for C1 and C2, my D-Link is then
providing a static address and I set the TCP/IP accordingly):
C3 IP = 192.168.0.103 (any given static address will give same results)
Connection status = Connected
Ping 192.168.0.1 = fails
Ping any outside physical (XXX.XXX.XXX.XXX) address = fails
Ping and browse C1 and C2 = successful
If I try to get a dynamic IP (this works well for C1 and C2):
C3 will try to acquire IP for several minutes and then...
C3 IP = 169.254.XXX.XXX (one of those useless internal IPs)
Connection status = "Limited or no connectivity"
Ping 192.168.0.1 = fails
Ping any outside physical (XXX.XXX.XXX.XXX) address = fails
Ping and browse C1 and C2 = fails
I tried switching cables from one computer to another. I tried using other
LAN ports on the D-Link. I tried shutting down C1 and using its IP address
and name on C3 (remembering to change MAC on static DHCP of D-Link). I
tried hooking C3 directly to the broadband modem. I tried the three
different adaptors (1 wireless and 2 regular LAN) on the MB of C3 and they
all give the same results as above. I also restored C3 (with XP Pro) to a
state where absolutely nothing is installed but WinXP Pro. I then
reinstalled each adapter one by one with testing connectivity between each
install. All results as above.
The WinXP Pro install of C3 should be quite optimal since I installed it
myself. I have done so for many years at work and I have never hit that
sort of a problem.
I am beginning to run out of options here.
Is there a good network diagnostic tool that I could download? MS network
diagnostic is not helping much.
Is there a clean and simple way to force XP Pro to reinitialize its network
components (as it does when you first install it)? I could just reinstall
XP Pro, but I am getting a little tired of all this work with no good
results to show for.
Anyone feels inspired?
Thanks... And Happy New Year to All!
Sly
ISP -> Broadband modem -> D-Link DI-624
Computer 1 (C1) - WinXP Pro Wired
Computer 2 (C2) - WinXP Pro Wireless
Computer 3 (C3) - WinXP Pro (ASUS P5K Premium MB) Wired or wireless
Never had any connectivity problem with C1 and C2.
C3, my new computer, could never connect to the Internet. It is certainly
"connected" to the D-Link in static mode because I can browse C1 and C2
from C3. Here is what I have tried so far:
If I force a static IP (this works well for C1 and C2, my D-Link is then
providing a static address and I set the TCP/IP accordingly):
C3 IP = 192.168.0.103 (any given static address will give same results)
Connection status = Connected
Ping 192.168.0.1 = fails
Ping any outside physical (XXX.XXX.XXX.XXX) address = fails
Ping and browse C1 and C2 = successful
If I try to get a dynamic IP (this works well for C1 and C2):
C3 will try to acquire IP for several minutes and then...
C3 IP = 169.254.XXX.XXX (one of those useless internal IPs)
Connection status = "Limited or no connectivity"
Ping 192.168.0.1 = fails
Ping any outside physical (XXX.XXX.XXX.XXX) address = fails
Ping and browse C1 and C2 = fails
I tried switching cables from one computer to another. I tried using other
LAN ports on the D-Link. I tried shutting down C1 and using its IP address
and name on C3 (remembering to change MAC on static DHCP of D-Link). I
tried hooking C3 directly to the broadband modem. I tried the three
different adaptors (1 wireless and 2 regular LAN) on the MB of C3 and they
all give the same results as above. I also restored C3 (with XP Pro) to a
state where absolutely nothing is installed but WinXP Pro. I then
reinstalled each adapter one by one with testing connectivity between each
install. All results as above.
The WinXP Pro install of C3 should be quite optimal since I installed it
myself. I have done so for many years at work and I have never hit that
sort of a problem.
I am beginning to run out of options here.
Is there a good network diagnostic tool that I could download? MS network
diagnostic is not helping much.
Is there a clean and simple way to force XP Pro to reinitialize its network
components (as it does when you first install it)? I could just reinstall
XP Pro, but I am getting a little tired of all this work with no good
results to show for.
Anyone feels inspired?
Thanks... And Happy New Year to All!
Sly