• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Heres One for All you Guru's

S

strates

Senior member
Let me start at the beginning. I have 3 WinXP clients on a wireless network NATing through a cable modem. Let us call these 3 clients .100, .101, and .102.

The ultimate goal is to connect to a pop3 email server on my primary machine, .101, so that I don't have to go to a secondary machine, .100, to read my mail. As you may have guessed, .100 is already configured and working with the pop3 server.

In trying to configure .101 to connect, I get a connection error. So I try to ping, from .101, my pop3 server. I get Destination host unreachable.

A similiar ping from .100 is successful. I also try the ping from .102 to see what I get. It is also successful.

The question is why can't I ping the pop3 server from .101, but I can ping it from .100 and .102?

To give some more information, I tried broadening the ping to the entire domain which contains the pop3 server. Any address in the same domain as my target pop3 server is unreachable (unpingable) to .101. However, they work fine from .100 and .102. It should also be noted that I can navigate with my browser to this target domain just fine from .101. So the only problem is with the ping (and, in turn, with my email.)

Finally, I have also disabled all software firewalls and antivirus on .101 to make sure that wasn't the issue. It wasn't.

Let me know if you need more details, but I think this should be enough to get your gears grinding.
 

"Destination host unreachable" tells me your answer is likely in your ipconfig/all or route print outputs.
 
Well here is the outputs from my ipconfig/all and route print. Nothing stands out to me.

ipconfig/all

Windows IP Configuration



Host Name . . . . . . . . . . . . : hop

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : dc.dc.cox.net



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : dc.dc.cox.net

Description . . . . . . . . . . . : Hawking HWP54GR Hi-Speed Wireless-G PCI Card

Physical Address. . . . . . . . . : 00-0E-3B-04-9A-F3

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Friday, May 19, 2006 1:56:45 AM

Lease Expires . . . . . . . . . . : Friday, May 26, 2006 1:56:45 AM

print route


IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x4 ...00 0e 3b 04 9a f3 ...... Hawking HWP54GR Hi-Speed Wireless-G PCI Card - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.101 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.101 192.168.0.101 25
192.168.0.101 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.0.255 255.255.255.255 192.168.0.101 192.168.0.101 25
224.0.0.0 240.0.0.0 192.168.0.101 192.168.0.101 25
255.255.255.255 255.255.255.255 192.168.0.101 192.168.0.101 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None
 
post the IPCONFIG /ALL from either .100 or .102 (whatever machine is working with the pop server). Also, try pinging something else, like google.com. Sounds like a DNS resolution problem...
 
pinging google works fine. It's not a DNS problem, as the ping command resolves the domain name to a ip address, and I can't ping the ip address either.

<b>here's the result of ping www.gmu.edu:</b>



Pinging jiju.gmu.edu [129.174.1.52] with 32 bytes of data:



Destination host unreachable.

Destination host unreachable.

Destination host unreachable.

Destination host unreachable.



Ping statistics for 129.174.1.52:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

<b> Here's the ipconfig/all from .102</b>



Windows IP Configuration



Host Name . . . . . . . . . . . . : thinkpad

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : dc.dc.cox.net



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

Physical Address. . . . . . . . . : 00-16-36-37-A8-A2



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : dc.dc.cox.net

Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapter II

Physical Address. . . . . . . . . : 00-14-A4-8A-AC-9B

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.102

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Monday, May 22, 2006 1:33:35 PM

Lease Expires . . . . . . . . . . : Monday, May 29, 2006 1:33:35 PM

I just noticed that the node type on .101 was unknown, but it is hybrid on the other two. So I tryied following this microsoft article: http://support.microsoft.com/kb/310570 I had to add the EnableProxy dword value, because I simply didn't have one. But either way, it still says unknown for node type. I know what the EnableProxy value does, but I have no real idea if this node type would have any relation to this problem or not. Thanks for all the help though, I really appreciate it.

Strates
 
Have you tried releasing and renewing the IP address on the bad machine? How about setting it to a static address momentarily instead of using DHCP? You are right, it is definitely not a DNS issue since you say you can browse the net from the affected machine. I missed that part of your post.
 
Yes, I have released, renewed, and staticically assigned. I would plug directly into the back of the cable modem, if I could, but I don't feel like that would make a difference, anyways.
 
Well, I would say your next step is to completely uninstall the wireless card and its software and then reinstall it. Seems like something has become corrupted somewhere. Also, plugging straight into the cable modem or router would tell you if the problem is isolated to just the wireless NIC, or if both adapters on the machine are affected. If the wired connection exhibits the same problems, you may want to reinstall the TCP/IP stack.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top