Re: Unable to resolve hostname (winsock problem?)
- From: "Charlie Tame" <charlie@xxxxxxxxx>
- Date: Sun, 25 Sep 2005 15:14:20 -0500
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" <RonGGGG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7C49A2F4-D7CE-45D0-839E-986D769808BA@xxxxxxxxxxxxxxxx
> 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" wrote:
>
>> 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" <RonGGGG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:99FB0CA0-2E12-4F67-90CC-98184001558E@xxxxxxxxxxxxxxxx
>> >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
>> >
>> > "siljaline" wrote:
>> >
>> >> "RonGGGG" wrote:
>> >> >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)
>> >>
>> >>
>> >>
>> >>
>> >>
>>
>>
>>
.
- Follow-Ups:
- Re: Unable to resolve hostname (winsock problem?)
- From: RONGGGG
- Re: Unable to resolve hostname (winsock problem?)
- References:
- Re: Unable to resolve hostname (winsock problem?)
- From: siljaline
- Re: Unable to resolve hostname (winsock problem?)
- From: Charlie Tame
- Re: Unable to resolve hostname (winsock problem?)
- Prev by Date: Re: Opening PDF File
- Next by Date: Re: Unable to resolve hostname (winsock problem?)
- Previous by thread: Re: Unable to resolve hostname (winsock problem?)
- Next by thread: Re: Unable to resolve hostname (winsock problem?)
- Index(es):