[TC]

-- Hello,

I'm having a strange network issue and was wondering if someone can help
me out. I'm having it on 2 systems. I'll describe the problem first then
describe the system/network setups.


I'll boot the computer up and let it's do it's thing. AIM and YIM will
load and connect and I'll be able to talk to people. However, when I go to
view a web page (google, MS, etc) and I get an error can't find server. It's
a basic DNS look up error. On occation I also get a time out error.

What confuses me is that AIM and YIM can get connected nothing else. I
have tried PINGing and it has it's equivalent of the errors.

Slowly applications get access in part of whole. IE: Eudora will be able
to resolve one pop server but not the others then the others slowly come up.
This Happens with Thunderbird as well. This happens with MS applications and
non-MS applications.

System setups:

1st System:
XP Pro SP2 in a domain. While on my home network no problem. Static IP
addresses configured as an Alternate IP address.
While away at work. DHCP addresses. With a netgear. Not sure of the model
since I have no control over it. However, NAT is being used and the internal
IP's are RealWorld not assigned to the company.

I can get around the issues by makeing a VPN connection to home and have
everything routed that way.

2nd System:

XP (not sure if it's home or pro). Only DHCP. No work around possible.
Connecting via LinkSys routers. No idea of the IPs at this time.


Thank you,

TC

Please reply to the newsgroup so we can all learn from others.
The obvious fake address is not meant to offend.
Rather it is for protection. I have been using Usenet for appox. 15 year and
have had some undesirable outcomes.
Please post all replies to the News Group.
Thank you.

[allan_grossman@hotmail.com]

Hi -

I think what might be happening is Windows XP is removing slow DNS
servers from your list of available DNS resources, eventually leaving
you with no way to do name resolution until the DNS cache expires.
Here's a way to check it -

Next time you have this problem, open a command prompt and type
'ipconfig /flushdns' and hit the enter key. If this solves your
problem, disable the DNS Client service on the XP Professional
machine(s). The service isn't required on machines that only connect
to workgroups and/or the Internet.

Hope this helps -

[TC]

I will give this a try when I go into work on Friday. Thank you so much.

One quick followup. If this turns out to be the problem. Do you know if it's
possible to create a script or a GPO that will turn off the DNS client when
not connected to a domain.

Thank you,

TC

<allan_grossman@hotmail.com> wrote in message
news:1118148368.304076.311920@o13g2000cwo.googlegroups.com...
> Hi -
>
> I think what might be happening is Windows XP is removing slow DNS
> servers from your list of available DNS resources, eventually leaving
> you with no way to do name resolution until the DNS cache expires.
> Here's a way to check it -
>
> Next time you have this problem, open a command prompt and type
> 'ipconfig /flushdns' and hit the enter key. If this solves your
> problem, disable the DNS Client service on the XP Professional
> machine(s). The service isn't required on machines that only connect
> to workgroups and/or the Internet.
>
> Hope this helps -
>

[TC]

I totally brain farted. I know I can make a GPO that will turn off the DNS
Client. That's a given.
Is it possible to have that GPO only be implimented when on a network that
is not the same as the domain.

TC

"TC" <travelclarkie@gmail.com> wrote in message
news:OSWJCF4aFHA.3184@TK2MSFTNGP15.phx.gbl...
>I will give this a try when I go into work on Friday. Thank you so much.
>
> One quick followup. If this turns out to be the problem. Do you know if
> it's possible to create a script or a GPO that will turn off the DNS
> client when not connected to a domain.
>
> Thank you,
>
> TC
>
> <allan_grossman@hotmail.com> wrote in message
> news:1118148368.304076.311920@o13g2000cwo.googlegroups.com...
>> Hi -
>>
>> I think what might be happening is Windows XP is removing slow DNS
>> servers from your list of available DNS resources, eventually leaving
>> you with no way to do name resolution until the DNS cache expires.
>> Here's a way to check it -
>>
>> Next time you have this problem, open a command prompt and type
>> 'ipconfig /flushdns' and hit the enter key. If this solves your
>> problem, disable the DNS Client service on the XP Professional
>> machine(s). The service isn't required on machines that only connect
>> to workgroups and/or the Internet.
>>
>> Hope this helps -
>>
>
>

[TC]

Allan,

I'm at work as I type. This did not work. Do you have any more thoughts?

TC

<allan_grossman@hotmail.com> wrote in message
news:1118148368.304076.311920@o13g2000cwo.googlegroups.com...
> Hi -
>
> I think what might be happening is Windows XP is removing slow DNS
> servers from your list of available DNS resources, eventually leaving
> you with no way to do name resolution until the DNS cache expires.
> Here's a way to check it -
>
> Next time you have this problem, open a command prompt and type
> 'ipconfig /flushdns' and hit the enter key. If this solves your
> problem, disable the DNS Client service on the XP Professional
> machine(s). The service isn't required on machines that only connect
> to workgroups and/or the Internet.
>
> Hope this helps -
>