Slow login Win2k Clients on Win2k Server

[Guest]

I have a problem about DNS and Win 2k Server and was wondering if you had any ideas

I am working on a job at a company and they have 2 Windows 2000 Servers, on the network they have a number of Win 2000 machines and a single XP machine. When we try to log on with the clients it seems to take a long time before the system will actually allow them into windows (We are also using Novell clients on each of the machines) and it takes a while to open up a drive on the network especially the servers. I have looked up the problem on the internet and the only ideas seem to be fix the DNS of the machines. As far as anyone knows the DNS is correct, they all point to the internal server IP address and can all access the network fine. The problem is apparent on both Win2k and XP machines.

Any Suggestions?

 

[Danny Sanders]

Does your AD DNS server that the clients point to for DNS have the correct
records?
See:
How to Verify the Creation of SRV Records for a Domain Controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;241515



hth

DDS W 2k MVP MCSE

I have a problem about DNS and Win 2k Server and was wondering if you had any ideas

I am working on a job at a company and they have 2 Windows 2000 Servers,

on the network they have a number of Win 2000 machines and a single XP
machine. When we try to log on with the clients it seems to take a long
time before the system will actually allow them into windows (We are also
using Novell clients on each of the machines) and it takes a while to open
up a drive on the network especially the servers. I have looked up the
problem on the internet and the only ideas seem to be fix the DNS of the
machines. As far as anyone knows the DNS is correct, they all point to the
internal server IP address and can all access the network fine. The problem
is apparent on both Win2k and XP machines.

 

[Bill Johnson]

Are you sure that it is a DNS issue? Slow logins with
Netware clients could also be an SLP problem. What version
of Netware are they using? What client? Are they using
Zenworks management agent?

-----Original Message-----
I have a problem about DNS and Win 2k Server and was wondering if you had any ideas

I am working on a job at a company and they have 2

Windows 2000 Servers, on the network they have a number of
Win 2000 machines and a single XP machine. When we try to
log on with the clients it seems to take a long time
before the system will actually allow them into windows
(We are also using Novell clients on each of the machines)
and it takes a while to open up a drive on the network
especially the servers. I have looked up the problem on
the internet and the only ideas seem to be fix the DNS of
the machines. As far as anyone knows the DNS is correct,
they all point to the internal server IP address and can
all access the network fine. The problem is apparent on
both Win2k and XP machines.

 

[Ace Fekay [MVP]]

In

I have a problem about DNS and Win 2k Server and was wondering if you
had any ideas

I am working on a job at a company and they have 2 Windows 2000
Servers, on the network they have a number of Win 2000 machines and a
single XP machine. When we try to log on with the clients it seems
to take a long time before the system will actually allow them into
windows (We are also using Novell clients on each of the machines)
and it takes a while to open up a drive on the network especially the
servers. I have looked up the problem on the internet and the only
ideas seem to be fix the DNS of the machines. As far as anyone knows
the DNS is correct, they all point to the internal server IP address
and can all access the network fine. The problem is apparent on both
Win2k and XP machines.

Any Suggestions?

Besides a possible issue with Zenworks, you need to insure that ALL your
machines aree only using your internal DNS server that is hosting the AD
zone. If you are using a Netware DNS server, then this guy needs to go. It
cannot support SRV records, which is a requirement of AD. During many domain
communication and functions, the clients and DCs query the DNS server for
the location of domain services and resources, which is what the SRV records
store. If using an ISP's DNS in your IP properties, then numerous numerous
errors will abound, one of which long logon times or cannot logon, will
occur. So what's happening probably is that they maybe trying to query the
external DNS for that domain name's LDAP services, which it does not have an
answer for, so the need to point to your own DNS that's hosting the AD zone
is essential in an AD infrastructure, no matter how small.

So, if using an external DNS or the Netware DNS, they need to be removed and
only use your own internal DNS. To achieve efficient Internet resolution (if
required if not using Proxy), then suggested to configure a forwarder

Here's how to configure a forwarder. If the option is grayed out, delete the
root zone. This will show how:
http://support.microsoft.com/?id=300202

Here's more info on DNS and AD's requirements:
http://support.microsoft.com/?id=291382

Here's an AD and DNS troubleshooting guide:
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Michael Johnston [MSFT]]

In addition to all the DNS suggestions, check the binding order. Make sure that the Client for Microsoft Networks is bound first. Ensure that all machines have
the lasted patches and updates applied. There are several SMB signing issues that can cause slow logons. These are resolved in the critical updates. If
possible, try disabling NCP/IP in the Novell client. Lastly, remove the Novell client and see if the performance improves.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.