Slow Network Connection

[riverbr]

Hi everyone,
NT is coming with an error that it detected a slow network connection at authentication. However, everytime I test all the servers, their speed is fine and fast. However I am starting to notice that not everyone in the New York Site is authenticating with the BDC in the New York site. They are authenticating in NJ, which might explain the slow network connection.
my question are:
1.- Why is it doing this? ( I thought it was automatic)

2.- How can i force it to authenticate in the BDC?

Please any assistance will be appreciated.

Note: my network consist of a router between NJ and NY. we are running TCP/IP as the main Protocol. and We are using NT4.0 at all the workstation and server.


Thanks,

Regards,
riverbr

[Jin Vitas]

Create a LMHOSTS file on the clients and input the entry for the BDC. or install Wins on the BDC. Also I would check the default gateways for the client systems.. run a winipcfg or ipconfig and see what the gateway is.. if the gateway is the BDC in NJ then that may also be the problem.

forgot to mention check server manager on the PDC to make sure that is a BDC.

[This message has been edited by Jin Vitas (edited 07-23-99).]

[Jin Vitas]

Things Any Network Admin might want to think about....

Takes load off PDC.

If you have Windows 95 clients, there is an additional step you should take to further ensure the PDC is not
overwhelmed when your 200 users logon at 8:00 a.m.Remember, the 95 client machine is hard-coded to look for the CONFIG.POL policy file in the netlogon share on the primary domain controller. Although you have replicated from the primary domain controller to the backup domain controller(s), you must still guide the 95 machine to the BDC to receive its policies. Otherwise, 95 machines will continue going to the PDC to parse the policy file, swamping the PDC with traffic. The solution is to enable Load Balancing on Windows 95 client machines. Here’s how you set up load balancing in the policy file:

Launch the System Policy Editor and click Open Registry on the File menu.
Double-click Local Computer.
Expand the Network branch.
Expand the Update branch and make sure the Remote Update checkbox is selected.
Click Remote Update.
In Settings for Remote Update, ensure the Load-balance checkbox is selected, then click OK.
Copy the System Policy file to the netlogon share on all domain controllers.
This reduces traffic on the PDC by allowing 95 machines to parse the policy file on
any domain controller.


If you occasionally experience the subject problems or your clients receive any of the following error
messages:
- Semaphore timeout period has expired
- Network path cannot be found.
- Insufficient system resources.

you should consider scheduling the following batch on your PDC each evening :
@echo off
C:
cd %SystemRoot%\System32
net sess /delete /y
net sess /delete /y
net stop Server /y
net stop Server /y
net start Server
net start netlogon
net start Browser
net start Schedule
net start Spooler
net start RemoteCMD
exit


Jin-Vitas