Discussion Locked

Slow login after adding wrkstn to domain

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After setting up a wireless LAN using Dell's TrueMobile 1150 NIC's, I have normal performance while the machines are linked as a workgroup. (One 2000 Server, Two 2000 Professional Workstations). However, once I add a workstation to the domain, the boot-up time to get to the login screen on that workstation, and then the sign-on process goes from about 10-15 seconds to 10-15 MINUTES!. The server machine seams uneffected.

Once in, I seam to have normal network performace. File transfers go at a reasonable speed, but anything to do with user authentication seam to take forever.

For example, if I try to add a domain user to the local workstation Administrator group, it eventually sees the domain, but times out when trying to check the name before completing the addition.

7 replies

by stillatit

The difference between being in the domain and not is the need to contact the server. It sounds like your workstation is trying to do a lookup on your server and failing. Eventually enough discovery methods time out that broadcast is used, and that works.

Things to check:

What protocols are used on each box, and what is their binding order? The protocol at the top of the list should be the same for both. Worst case is that the one at the top of the list on the workstation is not used by the server.

How is your workstation finding the domain controller?

If you are using DNS, is the first DNS server listed for the workstation a working server, and can it find the domain controller by the name the workstation knows? Putting an entry in the HOSTS file will probably solve the problem.

If you are using DHCP, verify the DNS names that DHCP is giving out, and check the node type that DHCP is setting.

If you are using netbeui, put an entry for the controller in the LMHOSTS file on the workstation, and use the #PRE and #DOM: tags.

Good luck.

by fajarpri

This is definitely the data transfer problem. I had similar problem with my network. Some of the w2k clients took forever to login into the domain.

So, I looked under the table and Woah! The cable was in mess!!! The power cable and network cable was crossing each other. So, I sorted it out and the login process run faster.

In your case, I think it relates to the wireless frequency being interfered with other equipments that emits electromagnetic frequency, such as Network Switch.

Good luck,
Fajar.

by blue ice

With the limited information that has been supplied, I would definitely suggest that it is a name resolution problem.

Do we have a DNS on WINS server running on this network?

What protocols are you using?

Ensure that the binding order is the same (doesnt matter on the server on NT4 - not sure about Y2K)

Also, what messages are appearing in the NT server logs? They may indicate what the problem could be.

Good luck.

This discussion is closed to new replies.