Re: Unable to resolve hostname (winsock problem?)

Tech-Archive recommends: Fix windows errors by optimizing your registry

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.



"Charlie Tame" wrote:

> 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
>
>
> "RonGGGG" <RonGGGG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:B199A097-E90A-4071-99CA-C7DB7B788F46@xxxxxxxxxxxxxxxx
> >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.
> >
> > "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)
> >>
> >>
> >>
> >>
> >>
>
>
>
.

Quantcast