Discussion Locked

TCP/IP takes long time to find Domain

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

Our LAN consist of only TCO/IP protocols and contains 53 users. We also have AS/400 connecting(using Rumba) through TCP/IP. ..the problem is when user need to shutdown their PC for a extended period of time, it takes forever for them to log on because it caan't find domain. I tried adding NetBeui and it seems to help but it takes a very long time to connect to AS/400.

Is their something that I am doing wrong ?

Thank You

5 replies

by dc1

Make sure you are running WINS or DNS or at the least have the PDC and the AS/400 in you lmhost or host file

by viperian

Do not use Netbeui, because it will be th efirst protocol the machines use. So connecting over TCP/IP with the AS400 will take a very long time. I agree with DC that you could use Wins or DNS. You could also use a hosts file or a lmhosts file (both without extension)

Example hosts file:

server1 192.168.0.1
as400 192.168.0.8

Example Lmhosts file:

192.168.0.1 server1 #PRE #DOM:DOMAINNAME
192.168.0.1 domainname #PRE
192.168.0.8 as400name #PRE

These files belong for windows 9x in the windows directory and for windows nt/2000 in
\WINNT\system32\drivers\etc

This discussion is closed to new replies.