XP cannot resolve hostname (winsock problem?)

[Guest]

I have two computers on a lan connected via a linksys router, using Time
Warner's cable modem. Until recently, no problems.
Now, on the XP machine (6.0.2900.2180.xpsp_sp2_gdr.050301-1519) from time to
time (i.e., several times a day), the computer cannot resolve hostnames. The
other computer (Win2K) on the lan has no problem, but the XP machine can't.
Email is unaffected; I can ping IP addresses but not hostnames. Rebooting
solves the problem for a while.
There are no other obvious problems.

ANY HELP IS **GREATLY** APPRECIATED.

PS: I cross posted this on on the IE6->General forum. Sorry about that. My
mistake.
Ron

 

[Lanwench [MVP - Exchange]]

In

I have two computers on a lan connected via a linksys router, using
Time Warner's cable modem. Until recently, no problems.
Now, on the XP machine (6.0.2900.2180.xpsp_sp2_gdr.050301-1519) from
time to time (i.e., several times a day), the computer cannot resolve
hostnames. The other computer (Win2K) on the lan has no problem, but
the XP machine can't. Email is unaffected; I can ping IP addresses
but not hostnames. Rebooting solves the problem for a while.
There are no other obvious problems.

DNS issue, probably. What DNS servers do you point to on each computer?
Compare them.

ANY HELP IS **GREATLY** APPRECIATED.

PS: I cross posted this on on the IE6->General forum. Sorry about
that. My mistake.
Ron

I think you mean, you multiposted - crossposting means, one message sent at
one time to multiple groups.

 

[Guest]

How would I make this comparison?

In

DNS issue, probably. What DNS servers do you point to on each computer?
Compare them.

I think you mean, you multiposted - crossposting means, one message sent at
one time to multiple groups.

 

[Lanwench [MVP - Exchange]]

In

How would I make this comparison?

Start, run...
Type
cmd <enter>

ipconfig /all

or if you want to see the output in a file:

ipconfig /all >c:\temp\myIPinfo.txt

 

[Guest]

I compared the two machines:

Win2K (good machine)
Connection Using: Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
IPConfig: Node Type = Broadcast
No Primary DNS Suffix
DHCP Server is 192.168.15.1
DNS Server is 24.29.103.10

XP Home(Problem machine)
Connection Using: RealTeck 8139 Family PCI.... (differs from Win2K...why?)
Same DHCP and DNS Servers
Node Type is hybrid (differs)

all other elements are the same.

This is really bumming me out. I have to reboot 5-10x a day now.

Event Log shows nothing wrong.

ANY HELP IS GREATLY APPRECIATED!!!

RON

 

[Guest]

One other thing: I have a cmd window endlessly pinging a website I know. This
has been going on for a few hours and during that time, I have not
experienced the problem. Why would continually pinging (and forcing a
hostname resolution) keep the problem from occurring?

RON

 

[Lanwench [MVP - Exchange]]

In

I compared the two machines:

Win2K (good machine)
Connection Using: Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)
IPConfig: Node Type = Broadcast
No Primary DNS Suffix
DHCP Server is 192.168.15.1
DNS Server is 24.29.103.10

XP Home(Problem machine)
Connection Using: RealTeck 8139 Family PCI.... (differs from
Win2K...why?)

Because that's your NIC in the home machine.

Same DHCP and DNS Servers
Node Type is hybrid (differs)

all other elements are the same.

Have you tried a winsock repair utility? I don't think that's your problem,
but it can't hurt (and it's good to have this on your computers, anyway, for
emergencies) - http://www.majorgeeks.com/download4372.html

Is there really only one DNS server listed? Usually, home/consumer routers
give out their own LAN IPs as the primary. I'd suggest changing the DHCP
scope on your Linksys - a) make sure it doesn't give out its own IP as the
primary DNS server and b) try different DNS servers. Change it so you
specify the DNS servers manually, and enter two of your ISP's DNS servers
there. Do ipconfig /release, and ipconfig /renew, on each machine, and see
how it goes.

This is really bumming me out. I have to reboot 5-10x a day now.

Event Log shows nothing wrong.

ANY HELP IS GREATLY APPRECIATED!!!

Let us know how it goes. If this doesn't work, go to the NIC manufacturer's
website, download & install the latest NIC drivers.

 

[Lanwench [MVP - Exchange]]

In

One other thing: I have a cmd window endlessly pinging a website I
know. This has been going on for a few hours and during that time, I
have not experienced the problem. Why would continually pinging (and
forcing a hostname resolution) keep the problem from occurring?

Can't say for sure from here. If you also open a cmd window and ping the LAN
IP of the other computer on the network, does it fail at all?

 

[Guest]

I can ping it no problem. But pinging it does not cure the problem as does
pinging a web hostname. I tried that last night by stopping the web pinging
and just pinged the other computer using ping <hostname> endlessly but after
a while I again could not resolve web-based hostnames. After I rebooted, I
again pinged that web address and have since this morning (it's now 1:44pm
here, so about 5 1/2 hours) and no problems resolving hostnames. So for some
reason that does the trick but it's sure a lousy way to operate.

Any other thoughts: Something I could look at? I plan on directly connecting
the computer to the cable moden, bypassing the router, but frankly, I
strongly doubt the router is the issue. The Win2K computer is fine on the
router (and was OK when the XP machine was bad).

I tried netsh refresh winsock command, which did something like refresh the
winsock catalog, but that too had no effect.

 

[Lanwench [MVP - Exchange]]

In

I can ping it no problem. But pinging it does not cure the problem as
does pinging a web hostname.

Meaning, you can successfully ping www.google.com ?

I tried that last night by stopping the
web pinging and just pinged the other computer using ping <hostname>
endlessly but after a while I again could not resolve web-based
hostnames. After I rebooted, I again pinged that web address and have
since this morning (it's now 1:44pm here, so about 5 1/2 hours) and
no problems resolving hostnames. So for some reason that does the
trick but it's sure a lousy way to operate.

Sure. Agreed.

Any other thoughts: Something I could look at?

See my other reply in here.

I plan on directly
connecting the computer to the cable moden, bypassing the router, but
frankly, I strongly doubt the router is the issue. The Win2K computer
is fine on the router (and was OK when the XP machine was bad).

I suspect you're correct.

I tried netsh refresh winsock command, which did something like
refresh the winsock catalog, but that too had no effect.

Did you try an updated NIC driver from that hardware mfr's website?

 

[Guest]

I can successfully ping www.google.com. In fact, pinging a website
continually (ping -t <hostname>) keeps the problem away. What does that mean?

I have not tried to update my NIC driver. Why would that help?

 

[Lanwench [MVP - Exchange]]

In

I can successfully ping www.google.com. In fact, pinging a website
continually (ping -t <hostname>) keeps the problem away. What does
that mean?

Interesting - I'm wondering if you have this identical problem when the
other computer is powered off or disconnected entirely....do you?

I have not tried to update my NIC driver. Why would that help?

Why would it hurt?
When I have a problem I try everything (nondestructive). And making sure you
have the latest supported NIC driver directly from the manufacturer.

 

[Guest]

Hi. For some reason, I didn't get notified of your reply.

The problem occurs on the XP Home machine regardless of what the other
machine is doing or is powered on or off.

When I have the cmd window open and pinging a hostname, that **seems** to
fix the problem, but only for several hours. By morning, or when I'm back
from work, even if the ping in one cmd window is working, I cannot resolve
hostnames again and if I open a second cmd window and try to ping the same
location on the web, ping fails. Bizarre, right!!

I've fiddleld with the TCP/IP settings on the WINS tab; no positive effect
(in fact, no effect at all: Both the Win2K and XP Home machines are now set
to NetBIOS over TCP/IP, but that didn't do anything.

I'm exactly where I was before.

$100 TO ANYONE WHO CAN FIX THIS PROBLEM. CASH!!!

RON

 

[Guest]

HI. Again, I must have not checked the notify me button, so I didn't see your
reply. I'm downloading Winsock repair now and will check out specifying the
DNS servers of my ISP. Will let you know!

THANKS!!!!!