Slow response when connecting to network

[Guest]

I have a Windows Small Business Server 2003 with ISA Server 2004. After I
have upgraded it to SP1, when ISA Server 2000 was upgraded to ISA Server 2004
two out of my machines, running Windows XP Pro started out taking around 30
minutes to log on the network.

Both machines tell me "Applying user settings" and here they wait for that
long.

Any suggestions on what should I do to solve this?

 

[Richard G. Harper]

Check the domain DNS configuration to ensure that DNS is working properly,
then make sure that the clients are looking only at the domain DNS server
for name resolution.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

Hi Richard,

its strange because if I type "nslookup" it answers me it didnt find any
server, byt if I type "ipconfig", its there. Any clue?

Check the domain DNS configuration to ensure that DNS is working properly,
then make sure that the clients are looking only at the domain DNS server
for name resolution.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

I have a Windows Small Business Server 2003 with ISA Server 2004. After I
have upgraded it to SP1, when ISA Server 2000 was upgraded to ISA Server
2004
two out of my machines, running Windows XP Pro started out taking around
30
minutes to log on the network.

Both machines tell me "Applying user settings" and here they wait for that
long.

Any suggestions on what should I do to solve this?

 

[Malke]

Hi Richard,

its strange because if I type "nslookup" it answers me it didnt find
any server, byt if I type "ipconfig", its there. Any clue?

Did you check the DNS settings like Richard suggested? What are they?
The server should look to itself for DNS with forwarders set for
Internet access. The workstations should only look to the server for
DNS.

Malke

 

[Guest]

Hi Malke,

well I believe I did that but just in case, could you please, tell me
step-by-step what should I do to check on that?

 

[Malke]

Hi Malke,

well I believe I did that but just in case, could you please, tell me
step-by-step what should I do to check on that?

Here is information from MVP Ron Lowe (applicable whether the server is
running Win2k or Win2k3):

XP differs from previous versions of windows in that it uses DNS as it's
primary name resolution method for finding domain controllers:

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS. ( Which may or
may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the Win2k
server itself. They should NOT be pointing to an ISP's DNS server. An
'ipconfig /all' on the XP box should reveal ONLY the domain's DNS
server. You should use the DHCP server to push out the local DNS server
address.

2) Ensure DNS server on Win2k is configured to permit dynamic updates.

3) Ensure the Win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS
server not on the clients, but in the 'forwarders' tab of the local
Win2k DNS server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root
Hints' tabs because they are greyed out, that is because there is a
root zone (".") present on the DNS server. You MUST delete this root
zone to permit the server to forward unresolved queries to yout ISP or
the root servers. Accept any nags etc, and let it delete any
corresponding reverse lookup zones if it asks.

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke

 

[Guest]

Hi Malke,

well I did it all, but guess what?? Same problem. Any other thing that
should I try?

Regards,

Carlos.

 

[Malke]

Hi Malke,

well I did it all, but guess what?? Same problem. Any other thing that
should I try?

Sorry, but I don't know. However, since you have several servers in
operation, you undoubtedly have a support contract with Microsoft. I
would call their server tech support - which is excellent - and have
them help you.

Malke

 

[Guest]

Hi Malke,

no I dont have several servers only one Small Business Server 2003 and
unfortunatelly I dont have paid support. I tried to most uncommon things
already. Runned an antivirus, MBSA and nothing. Everything points to my ISA
Server but I simply dont know on what it could be doing this to me...

 

[Malke]

Hi Malke,

no I dont have several servers only one Small Business Server 2003 and
unfortunatelly I dont have paid support. I tried to most uncommon
things already. Runned an antivirus, MBSA and nothing. Everything
points to my ISA Server but I simply dont know on what it could be
doing this to me...

You might try posting in a newsgroup for SBS server:

microsoft.public.windows.server.sbs

Malke