Unable to resolve hostname (winsock problem?)

G

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.
 
S

siljaline

RonGGGG said:
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.
Click to expand...

Eliminate the router as the culprit by removing from you LAN set-up and see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
 
G

Guest

I will try that. But...if the other computer on the router has no problem, no
errors occur, and the internet is available (pinging and email) why would the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a hostname, I
assume that the string contains a hostname it is passed first to the nearest
DN server so the name can be resolved and then forwarded to the resulting IP
address.

The IP Address part works perfectly. It is only the address resolution which
fails. I don't know enough about IP protocol to know if the address the
hostname resolves to has to be passed back to the caller (me) and then the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON
 
C

Charlie Tame

Try searching for a file called "HOSTS" without the quotes and without an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking place.
If you can use a numeric address and reach websites it's no likely an IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to localhost are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost, which
without a web server running is the same as nowhere. is also possible for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the computer
until we can establish otherwise. :)

Charlie
 
G

Guest

I did an experiment last nght and continually pinged a web site using ping
<hostname>. There were no problems this morning. So, apparently, the inabilty
to resolve hostnames only occurs after a period of inactivitiy.
 
C

Charlie Tame

Try tools>internet options>connection tab and hit the button LAN settings.

See if that's the same as the other machine that's working better, if not
try changing it.

You could also check the "Network" settings (properties) on both for the
TCP/IP protocol and see if they are both the same. If one is set to manually
detect settings from DHCP and the other isn't I think it's vaguely possible
that could be a cause. If they are manual then you can eliminate any
differences there too.

Charlie
 
G

Guest

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no problem. Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my XP
computer has the problem.

Charlie Tame said:
Try searching for a file called "HOSTS" without the quotes and without an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking place.
If you can use a numeric address and reach websites it's no likely an IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to localhost are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost, which
without a web server running is the same as nowhere. is also possible for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the computer
until we can establish otherwise. :)

Charlie




RonGGGG said:
I will try that. But...if the other computer on the router has no problem,
no
errors occur, and the internet is available (pinging and email) why would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a hostname, I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the resulting
IP
address.

The IP Address part works perfectly. It is only the address resolution
which
fails. I don't know enough about IP protocol to know if the address the
hostname resolves to has to be passed back to the caller (me) and then the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON
Click to expand...
Click to expand...
 
C

Charlie Tame

Did you find the start>settings>network connections>local area whatever it
is and check both machines by clicking the properties button and then double
clicking on the TCP/IP protocol line? See if they are the same settings in
there and if not make them the same? I suppose it's also possible that some
spyware as yet undiscovered could be trying to redirect your inquiries and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better days
(weeks)? :)

Charlie

RonGGGG said:
The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my XP
computer has the problem.

Charlie Tame said:
Try searching for a file called "HOSTS" without the quotes and without an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost, which
without a web server running is the same as nowhere. is also possible for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




RonGGGG said:
I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address resolution
which
fails. I don't know enough about IP protocol to know if the address the
hostname resolves to has to be passed back to the caller (me) and then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

The connection tabs for both machines are the same: Automatically detect
settings.

The TCP/IP Properties for both connections are the same.

Some great mystery, right!

You just know the culprit is something totally trivial.

Thing is: I haven't installed anything on the XP machine for quite some
time. MS does do automatic updates, but as a cause, that's a very very remote
possibility. Still, it's the only change. I have AntiSpyware and CA Virus
detection running on both.

This just happened out of the blue.
 
F

Frank Saunders, MS-MVP OE

RonGGGG said:
The connection tabs for both machines are the same: Automatically
detect settings.

The TCP/IP Properties for both connections are the same.

Some great mystery, right!

You just know the culprit is something totally trivial.

Thing is: I haven't installed anything on the XP machine for quite
some time. MS does do automatic updates, but as a cause, that's a
very very remote possibility. Still, it's the only change. I have
AntiSpyware and CA Virus detection running on both.

This just happened out of the blue.
Click to expand...

On the problem machine go to Start | Run and type
netsh winsock reset

--
Frank Saunders, MS-MVP OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/
 
G

Guest

Thanks. I already did; no effect.

All yesterday, I had a cmd window open and was pinging a website; that
seemed to keep the problem away. This morning, that cmd window was still
working just fine but the problem was back.

So, I was looking at a cmd window where ping <hostname1> was continuing to
respond and opening another cmd window with ping <hostname1> failed!!

I also tried a little html page on a website I have which refreshed every 3
seconds, again no avail. The pinging helped for a while.

This evening after I'm back from work, I'll try connecting the computer
directly into the modem, bypassing the router. But I just think that's a
waste of time. The other computer on the router works fine (even when the
first one couldn't resolve hostnames).

I just wish someone could direct me to some other tests.

Frankly, I'd pay $100 to fix this problem.
 
G

Guest

Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning, describing
the problem and ended with "you'll just never believe this." and he said, "I
believe it. It happens to me." He has a laptop (mine is a desktop), and he
uses a Verizon Aircard when he's on the train going to work. If he doesn't
keep a cmd window open, constantly pinging a hostname, the machine loses its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc., but
very similar situation.

Charlie Tame said:
Did you find the start>settings>network connections>local area whatever it
is and check both machines by clicking the properties button and then double
clicking on the TCP/IP protocol line? See if they are the same settings in
there and if not make them the same? I suppose it's also possible that some
spyware as yet undiscovered could be trying to redirect your inquiries and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better days
(weeks)? :)

Charlie

RonGGGG said:
The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my XP
computer has the problem.

Charlie Tame said:
Try searching for a file called "HOSTS" without the quotes and without an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost, which
without a web server running is the same as nowhere. is also possible for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address resolution
which
fails. I don't know enough about IP protocol to know if the address the
hostname resolves to has to be passed back to the caller (me) and then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
C

Charlie Tame

Okay I found another thing that "Might" be of interest.

First of all under the network > TCP/IP properties - probably the advanced
button (Not sure as I am using 2003 server and it's a bit different layout)
there is a tab for WINS (Windows Incomprehensible Name Service) that has a
checkbox for using LM Hosts - seems that applies to all TCP/IP devices if
you set it for one. Maybe that is set on one machine not the other and maybe
that makes a difference?

I also looked for some way to increase the DNS timeout values and although I
found an article for a program to do it on the MSDN site I don't see that
doing much good in general - however I am looking for clues here
http://www.downloadjunction.com/product/software/62595/index.html

I mean I can't for the life of me see why WINS stuff should affect anything
at all but after all this is IE we're talking about :) Heck, even clearing
the temporary files might make a difference if it's a timeout thing.

I guess you could take the IP of the site and put it in your HOSTS file to
see if that helps any... about lost for a sure bet here are we not?

I did see something somewhere about a DNS difference between XP and 2000
with more gripes about XP so have a feeling it's in DNS.

Have you tried just typing the IP address into IE... e.g. just
xxx.xxx.xxx.xxx should do the trick if it's a single website server.

Charlie

RONGGGG said:
Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and he
uses a Verizon Aircard when he's on the train going to work. If he doesn't
keep a cmd window open, constantly pinging a hostname, the machine loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc., but
very similar situation.

Charlie Tame said:
Did you find the start>settings>network connections>local area whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

RonGGGG said:
The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and without
an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also possible
for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
C

Charlie Tame

Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk or
wait for other suggestions these came from the help file on that little
program mentioned in previous post so it looks like the authors did some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your problem.

Charlie

RONGGGG said:
Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and he
uses a Verizon Aircard when he's on the train going to work. If he doesn't
keep a cmd window open, constantly pinging a hostname, the machine loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc., but
very similar situation.

Charlie Tame said:
Did you find the start>settings>network connections>local area whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

RonGGGG said:
The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and without
an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also possible
for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

First, I GREATLY GREATLY APPRECIATE all the time and effort you are devoting
to this, whatever the outcome.

One thing: the failure of hostname resolution applies to all websites. Even
when I have one cmd window open with ping -t <hostname1>, when the failure
occurs, this cmd window can keep pinging returning different values and all,
and I can open another cmd window, and be unable to ping the same site. THAT
HAS TO MEAN SOMETHING, right?????

As for LMHOSTS: On the XP machine, it is enabled on the WINS tab and the
default button is selected.

On the Options table, optional settings are TCP/IP filtering but it is not
selected on the properties dialog box.

On IP Settings: DHCP Enabled.

DID I MENTION THAT my boss has an almost identical problem with a laptop
running XP Pro when he uses his Verizon Aircard, in order to keep the ability
to resolve hostnames, he has to keep the same cmd window open and ping some
hostname, he thinks so the connection won't go stale.

I'm using a Linksys router with Vonage VoIP (over the broadband Timewarner
cable modem).

RON

Charlie Tame said:
Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk or
wait for other suggestions these came from the help file on that little
program mentioned in previous post so it looks like the authors did some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your problem.

Charlie

RONGGGG said:
Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and he
uses a Verizon Aircard when he's on the train going to work. If he doesn't
keep a cmd window open, constantly pinging a hostname, the machine loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc., but
very similar situation.

Charlie Tame said:
Did you find the start>settings>network connections>local area whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and without
an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also possible
for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

One more thing: The "good" Win2K machine has "Enable NetBIOS over TCP/IP"
selected and the XP machine did not (it had the default, "Use NetBIOS setting
from DHCP server. If static IP address is used or the DHCP server does not
provide NetBIO setting enable NetBIOX over TCP/IP" (this was enabled; now I
selected Enable NetBIOS over TCP/IP. I'll try!!!

Charlie Tame said:
Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk or
wait for other suggestions these came from the help file on that little
program mentioned in previous post so it looks like the authors did some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your problem.

Charlie

RONGGGG said:
Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and he
uses a Verizon Aircard when he's on the train going to work. If he doesn't
keep a cmd window open, constantly pinging a hostname, the machine loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc., but
very similar situation.

Charlie Tame said:
Did you find the start>settings>network connections>local area whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no DNS
activity for a while. I've been piniging a website all night using ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and without
an
extension. The default file is a simple example with the instructions
briefly included in it, you can open it with notepad when you find it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and if
that's been screwed up it may be stopping your resolution from taking
place.
If you can use a numeric address and reach websites it's no likely an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also possible
for
the router to be blocking something for one machine and not the other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email) why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
C

Charlie Tame

Well there's a large amount of guesswork on my part here and I guess NetBIOS
and LAN Manager (the dos networking system that I think WINS might be
derived from) might interact in some unforeseen way with something... honest
I am not trying to waste your time or mine so I appreciate your patience
too.

Someone is going to step in soon with a blindingly obvious answer to this
I'm sure, but darned if I can see it right now. I mean I can see a number of
things that might cause this, even at random, but I can't see the "Timeout"
issue at all. Did anyone suggest checking in Administrative tools>services
to see what's running in there? I had something odd going on with 2000 once
where it seemed to want the DNS server running as well as the DNS client...
never found out what that was but it came and went for no apparent reason so
I am not sure it even was that :) In the services control panel you can have
services disabled, manual or automatic. Auto basically means when the system
starts, manual means on demand (say another program) and disabled means
never, so you don't want to disable that which you are not sure about :) You
can also find some info by looking at Event Viewer. I'd copy a shortcut to
the desktop for Admin tools and maybe event viewer and services so you can
quickly look and see if anything changes.

Meanwhile if anyone who knows the answer is watching and thinking "Idiots"
please don't, enlighten us eh?

Charlie

RonGGGG said:
One more thing: The "good" Win2K machine has "Enable NetBIOS over TCP/IP"
selected and the XP machine did not (it had the default, "Use NetBIOS
setting
from DHCP server. If static IP address is used or the DHCP server does not
provide NetBIO setting enable NetBIOX over TCP/IP" (this was enabled; now
I
selected Enable NetBIOS over TCP/IP. I'll try!!!

Charlie Tame said:
Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk or
wait for other suggestions these came from the help file on that little
program mentioned in previous post so it looks like the authors did some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your
problem.

Charlie

RONGGGG said:
Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he
said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and
he
uses a Verizon Aircard when he's on the train going to work. If he
doesn't
keep a cmd window open, constantly pinging a hostname, the machine
loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc.,
but
very similar situation.

:

Did you find the start>settings>network connections>local area
whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same
settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no
DNS
activity for a while. I've been piniging a website all night using
ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when
my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and
without
an
extension. The default file is a simple example with the
instructions
briefly included in it, you can open it with notepad when you find
it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and
if
that's been screwed up it may be stopping your resolution from
taking
place.
If you can use a numeric address and reach websites it's no likely
an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names.
Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least
one
# space.
# Additionally, comments (such as these) may be inserted on
individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by
Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also
possible
for
the router to be blocking something for one machine and not the
other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email)
why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to
the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the
address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN
set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

I changed the WINS tab setting to Enable NetBIOS over TCP/IP (which the
default setting is supposed to also support), but that didn't help. It
*appeared* to make a difference in that I had hostname resolution for the
entire evening without ping running in a cmd window, but this morning, it was
back to the usual.

I am continuing to examine the software environment.

$100 to ANYONE WHO SOLVES THIS!!! NO KDDING.



Charlie Tame said:
Well there's a large amount of guesswork on my part here and I guess NetBIOS
and LAN Manager (the dos networking system that I think WINS might be
derived from) might interact in some unforeseen way with something... honest
I am not trying to waste your time or mine so I appreciate your patience
too.

Someone is going to step in soon with a blindingly obvious answer to this
I'm sure, but darned if I can see it right now. I mean I can see a number of
things that might cause this, even at random, but I can't see the "Timeout"
issue at all. Did anyone suggest checking in Administrative tools>services
to see what's running in there? I had something odd going on with 2000 once
where it seemed to want the DNS server running as well as the DNS client...
never found out what that was but it came and went for no apparent reason so
I am not sure it even was that :) In the services control panel you can have
services disabled, manual or automatic. Auto basically means when the system
starts, manual means on demand (say another program) and disabled means
never, so you don't want to disable that which you are not sure about :) You
can also find some info by looking at Event Viewer. I'd copy a shortcut to
the desktop for Admin tools and maybe event viewer and services so you can
quickly look and see if anything changes.

Meanwhile if anyone who knows the answer is watching and thinking "Idiots"
please don't, enlighten us eh?

Charlie

RonGGGG said:
One more thing: The "good" Win2K machine has "Enable NetBIOS over TCP/IP"
selected and the XP machine did not (it had the default, "Use NetBIOS
setting
from DHCP server. If static IP address is used or the DHCP server does not
provide NetBIO setting enable NetBIOX over TCP/IP" (this was enabled; now
I
selected Enable NetBIOS over TCP/IP. I'll try!!!

Charlie Tame said:
Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk or
wait for other suggestions these came from the help file on that little
program mentioned in previous post so it looks like the authors did some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your
problem.

Charlie

Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he
said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop), and
he
uses a Verizon Aircard when he's on the train going to work. If he
doesn't
keep a cmd window open, constantly pinging a hostname, the machine
loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network, etc.,
but
very similar situation.

:

Did you find the start>settings>network connections>local area
whatever
it
is and check both machines by clicking the properties button and then
double
clicking on the TCP/IP protocol line? See if they are the same
settings
in
there and if not make them the same? I suppose it's also possible that
some
spyware as yet undiscovered could be trying to redirect your inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is no
DNS
activity for a while. I've been piniging a website all night using
ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even when
my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and
without
an
extension. The default file is a simple example with the
instructions
briefly included in it, you can open it with notepad when you find
it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention and
if
that's been screwed up it may be stopping your resolution from
taking
place.
If you can use a numeric address and reach websites it's no likely
an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names.
Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
name.
# The IP address and the host name should be separated by at least
one
# space.
# Additionally, comments (such as these) may be inserted on
individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by
Kerio
Personal Firewall to divert popup calls in web pages to localhost,
which
without a web server running is the same as nowhere. is also
possible
for
the router to be blocking something for one machine and not the
other,
although I think it's more likely spyware / crapware damage to the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has no
problem,
no
errors occur, and the internet is available (pinging and email)
why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first to
the
nearest
DN server so the name can be resolved and then forwarded to the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the
address
the
hostname resolves to has to be passed back to the caller (me) and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN
set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
C

Charlie Tame

Well I am amazed nobody has yet come up with something so simple that... oh
well.

You have obviously looked at the properties for both network cards a lot by
now, I don't suppose there's an huge difference in protocols in use?

I suppose having another command window open with ipconfig /all in it might
tell you if anything keeps changing but again you'd have to keep doing
ipconfig /release and then /renew to see the changes. I'm wondering if
something is giving you a lease that's timing out in session or something. I
don't know what would happen if your router is doing DHCP and the 2000
machine had the DHCP server running too, or even XP Pro doing something of
that nature. My brain ain't working much better tonight than it was last
night to be honest :)

Charlie



RonGGGG said:
I changed the WINS tab setting to Enable NetBIOS over TCP/IP (which the
default setting is supposed to also support), but that didn't help. It
*appeared* to make a difference in that I had hostname resolution for the
entire evening without ping running in a cmd window, but this morning, it
was
back to the usual.

I am continuing to examine the software environment.

$100 to ANYONE WHO SOLVES THIS!!! NO KDDING.



Charlie Tame said:
Well there's a large amount of guesswork on my part here and I guess
NetBIOS
and LAN Manager (the dos networking system that I think WINS might be
derived from) might interact in some unforeseen way with something...
honest
I am not trying to waste your time or mine so I appreciate your patience
too.

Someone is going to step in soon with a blindingly obvious answer to this
I'm sure, but darned if I can see it right now. I mean I can see a number
of
things that might cause this, even at random, but I can't see the
"Timeout"
issue at all. Did anyone suggest checking in Administrative
tools>services
to see what's running in there? I had something odd going on with 2000
once
where it seemed to want the DNS server running as well as the DNS
client...
never found out what that was but it came and went for no apparent reason
so
I am not sure it even was that :) In the services control panel you can
have
services disabled, manual or automatic. Auto basically means when the
system
starts, manual means on demand (say another program) and disabled means
never, so you don't want to disable that which you are not sure about :)
You
can also find some info by looking at Event Viewer. I'd copy a shortcut
to
the desktop for Admin tools and maybe event viewer and services so you
can
quickly look and see if anything changes.

Meanwhile if anyone who knows the answer is watching and thinking
"Idiots"
please don't, enlighten us eh?

Charlie

RonGGGG said:
One more thing: The "good" Win2K machine has "Enable NetBIOS over
TCP/IP"
selected and the XP machine did not (it had the default, "Use NetBIOS
setting
from DHCP server. If static IP address is used or the DHCP server does
not
provide NetBIO setting enable NetBIOX over TCP/IP" (this was enabled;
now
I
selected Enable NetBIOS over TCP/IP. I'll try!!!

:

Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk
or
wait for other suggestions these came from the help file on that
little
program mentioned in previous post so it looks like the authors did
some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your
problem.

Charlie

Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he
said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop),
and
he
uses a Verizon Aircard when he's on the train going to work. If he
doesn't
keep a cmd window open, constantly pinging a hostname, the machine
loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network,
etc.,
but
very similar situation.

:

Did you find the start>settings>network connections>local area
whatever
it
is and check both machines by clicking the properties button and
then
double
clicking on the TCP/IP protocol line? See if they are the same
settings
in
there and if not make them the same? I suppose it's also possible
that
some
spyware as yet undiscovered could be trying to redirect your
inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my
better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is
no
DNS
activity for a while. I've been piniging a website all night
using
ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for
a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even
when
my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and
without
an
extension. The default file is a simple example with the
instructions
briefly included in it, you can open it with notepad when you
find
it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention
and
if
that's been screwed up it may be stopping your resolution from
taking
place.
If you can use a numeric address and reach websites it's no
likely
an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for
Windows.
# This file contains the mappings of IP addresses to host names.
Each
# entry should be kept on an individual line. The IP address
should
# be placed in the first column followed by the corresponding
host
name.
# The IP address and the host name should be separated by at
least
one
# space.
# Additionally, comments (such as these) may be inserted on
individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE
URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by
Kerio
Personal Firewall to divert popup calls in web pages to
localhost,
which
without a web server running is the same as nowhere. is also
possible
for
the router to be blocking something for one machine and not the
other,
although I think it's more likely spyware / crapware damage to
the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has
no
problem,
no
errors occur, and the internet is available (pinging and
email)
why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first
to
the
nearest
DN server so the name can be resolved and then forwarded to
the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the
address
the
hostname resolves to has to be passed back to the caller (me)
and
then
the
url re-issued or it is just forwarded to the IP address.

It it is returned, then perhaps there is something wrong with
the
downlink
part of the stack...I'm way out of my depth here.

Just very weird.

I will directly connect the computer to the modem.

RON

:

:
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.

Eliminate the router as the culprit by removing from you LAN
set-up
and
see if
the problem persists - please post back your findings.

Silj

--
siljaline

MS - MVP Windows (IE/OE) & Security, AH-VSOP
_________________________________________
Security Tools Updates
http://aumha.net/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

Really, I greatly appreciate your help, even if it didn't resolve the issue.
I'm probably going to use Geek Squad, if you can believe that. I spoke to an
operator yesterday who wants to assign it to their "covert ops" section, but
if they fix the problem (which I STRONGLY doubt they can), the laugh wil be
on me.

STILL: $100 (cash) to ANYONE WHO CAN FIX THIS PROBLEM.

RON

Charlie Tame said:
Well I am amazed nobody has yet come up with something so simple that... oh
well.

You have obviously looked at the properties for both network cards a lot by
now, I don't suppose there's an huge difference in protocols in use?

I suppose having another command window open with ipconfig /all in it might
tell you if anything keeps changing but again you'd have to keep doing
ipconfig /release and then /renew to see the changes. I'm wondering if
something is giving you a lease that's timing out in session or something. I
don't know what would happen if your router is doing DHCP and the 2000
machine had the DHCP server running too, or even XP Pro doing something of
that nature. My brain ain't working much better tonight than it was last
night to be honest :)

Charlie



RonGGGG said:
I changed the WINS tab setting to Enable NetBIOS over TCP/IP (which the
default setting is supposed to also support), but that didn't help. It
*appeared* to make a difference in that I had hostname resolution for the
entire evening without ping running in a cmd window, but this morning, it
was
back to the usual.

I am continuing to examine the software environment.

$100 to ANYONE WHO SOLVES THIS!!! NO KDDING.



Charlie Tame said:
Well there's a large amount of guesswork on my part here and I guess
NetBIOS
and LAN Manager (the dos networking system that I think WINS might be
derived from) might interact in some unforeseen way with something...
honest
I am not trying to waste your time or mine so I appreciate your patience
too.

Someone is going to step in soon with a blindingly obvious answer to this
I'm sure, but darned if I can see it right now. I mean I can see a number
of
things that might cause this, even at random, but I can't see the
"Timeout"
issue at all. Did anyone suggest checking in Administrative
tools>services
to see what's running in there? I had something odd going on with 2000
once
where it seemed to want the DNS server running as well as the DNS
client...
never found out what that was but it came and went for no apparent reason
so
I am not sure it even was that :) In the services control panel you can
have
services disabled, manual or automatic. Auto basically means when the
system
starts, manual means on demand (say another program) and disabled means
never, so you don't want to disable that which you are not sure about :)
You
can also find some info by looking at Event Viewer. I'd copy a shortcut
to
the desktop for Admin tools and maybe event viewer and services so you
can
quickly look and see if anything changes.

Meanwhile if anyone who knows the answer is watching and thinking
"Idiots"
please don't, enlighten us eh?

Charlie

One more thing: The "good" Win2K machine has "Enable NetBIOS over
TCP/IP"
selected and the XP machine did not (it had the default, "Use NetBIOS
setting
from DHCP server. If static IP address is used or the DHCP server does
not
provide NetBIO setting enable NetBIOX over TCP/IP" (this was enabled;
now
I
selected Enable NetBIOS over TCP/IP. I'll try!!!

:

Aha, found some more info

http://support.microsoft.com/default.aspx?kbid=263558

http://support.microsoft.com/default.aspx?kbid=813827

Now I have NOT had time to read these properly Ron so at your own risk
or
wait for other suggestions these came from the help file on that
little
program mentioned in previous post so it looks like the authors did
some
comprehensive research, all credit to them for this info.

I don't have time to go break my XP to see if I can duplicate your
problem.

Charlie

Yes, I did all that. The setting are identical.

The ODDEST THING is that I was speaking to my boss this morning,
describing
the problem and ended with "you'll just never believe this." and he
said,
"I
believe it. It happens to me." He has a laptop (mine is a desktop),
and
he
uses a Verizon Aircard when he's on the train going to work. If he
doesn't
keep a cmd window open, constantly pinging a hostname, the machine
loses
its
ability to resolve hostnames. TOTALLY DIFFERENT SYSTEM, Network,
etc.,
but
very similar situation.

:

Did you find the start>settings>network connections>local area
whatever
it
is and check both machines by clicking the properties button and
then
double
clicking on the TCP/IP protocol line? See if they are the same
settings
in
there and if not make them the same? I suppose it's also possible
that
some
spyware as yet undiscovered could be trying to redirect your
inquiries
and
causing a delay so it times out.

Sorry I don't have any more ideas right now, it's not one of my
better
days
(weeks)? :)

Charlie

The only thing in my hosts file is localhost.

The odd thing is that the problem seems to occur after there is
no
DNS
activity for a while. I've been piniging a website all night
using
ping
<hostname> to force DNS hostname resolution and this morning, no
problem.
Of
course, I can't do this forever.

So, the problem occurs when I don't try to resolve hostnames for
a
while.

There are no errors written to the event log.

The other computer attached to my linksys works perfectly even
when
my
XP
computer has the problem.

:

Try searching for a file called "HOSTS" without the quotes and
without
an
extension. The default file is a simple example with the
instructions
briefly included in it, you can open it with notepad when you
find
it.

Some spyware puts odd things in there.

This can be used to resolve names just like the DNS you mention
and
if
that's been screwed up it may be stopping your resolution from
taking
place.
If you can use a numeric address and reach websites it's no
likely
an
IP
problem.

Here is a sample of a hosts file


# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for
Windows.
# This file contains the mappings of IP addresses to host names.
Each
# entry should be kept on an individual line. The IP address
should
# be placed in the first column followed by the corresponding
host
name.
# The IP address and the host name should be separated by at
least
one
# space.
# Additionally, comments (such as these) may be inserted on
individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
127.0.0.1 www.f1organizer.com #REMOVED ADWARE URL
127.0.0.1 www.netpalnow.com #REMOVED ADWARE URL
127.0.0.1 www.addictivetechnologies.com #REMOVED ADWARE
URL
127.0.0.1 www.mindseti.com #REMOVED ADWARE URL
127.0.0.1 www.mindsetinteractive.com #REMOVED ADWARE URL
127.0.0.1 coolwebsearch.com
127.0.0.1 stats.coolwebsearch.com
127.0.0.1 www.coolwebsearch.com #[CWS/IEFeats]


The lines starting with # and the one line below referring to
localhost
are
in there by default, the lines added below there were added by
Kerio
Personal Firewall to divert popup calls in web pages to
localhost,
which
without a web server running is the same as nowhere. is also
possible
for
the router to be blocking something for one machine and not the
other,
although I think it's more likely spyware / crapware damage to
the
computer
until we can establish otherwise. :)

Charlie




I will try that. But...if the other computer on the router has
no
problem,
no
errors occur, and the internet is available (pinging and
email)
why
would
the
router be a possible culprit.

What I don't understand is this: when I use ping to resolve a
hostname,
I
assume that the string contains a hostname it is passed first
to
the
nearest
DN server so the name can be resolved and then forwarded to
the
resulting
IP
address.

The IP Address part works perfectly. It is only the address
resolution
which
fails. I don't know enough about IP protocol to know if the
address
the
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

$100 to anyone who can fix my problem: unable to resolve hostnames 4
XP cannot resolve hostname (winsock problem?) 13
IE 6.0 Acting Funny 3
Internet explorer will only let me go to secure sites 2
Problem with IE - Not allowing to more than One IE Window to remain opened 1
Can ping by IP address but not by domain name or hostname 1
IE 6 doesn't display everything on some website I visited 3
fatal "nohup" error 3

Top