Windows 2000 Workstation can't login to WinNT4 Domain

[Sean123]

I connect two networks throught Wingate VPN. Win2k on remote network can ping the domain server (NT4) and map to the shared drive from the domain server, but it can't login to the domain, with the following error:

The system cannot log you on now because the domain CC is not availalble.

Any idea how to fix it?

Thanks a lot!

[erwin]

Hi Sean

I connect two networks throught Wingate VPN. Win2k on remote network can ping the domain server (NT4) and map to the shared drive from the domain server.

Since you have already established a working VPN then joining the domain should be a simple process.

Firstly you need to make sure that the remote machine(s) that you want to log in on are members of the domain.

Since you can establish the VPN and reach shares etc on the domain controller at the other end , you should be able make the machines join the domain in the normal way in Windows 2000 (i.e through System properties/Network id tab etc...) while the VPN is connected.

Once they are members then when you restablish a VPN connection
these should be able login to the domain fine from Windows login.

If you wish these machines to be able to login to the domain from startup then the machine that is used to join the VPN will have to connect whenver it starts up so (so the VPN is established and the DomainController is available to validate logins.). In this case the Joining VPN should be configured to connect on "engine start".
There may be a little delay as the WinGateVPN connects and establishes the VPN behind the scenes while Windows is starting up

WinGate VPN merely passes the data and doesnt interfere with it so shouldnt affect the login process. I have checked this today and found it to work fine in this scenario.

Hope this helps

Regards
Erwin

[Sean123]

Thank you for the reply!

I just double checked and found out that I failed to describe the problem correctly. (I am sorry.)

On local network there are two servers, srvr1 (NT4, domain PDC) and srvr4 (w2k). Both of them are behind the Wingate Proxy server.

Computers at remote network can map to the shared drive of srvr4, but none of them can map to the shared drive of srvr1. Neither can them login to domain. But they all can ping srvr1 through computer name.

srvr1 has RIPClient.exe running.

How can I bring srvr1 visiable to remote network? Your help is greatly appreciated!

[erwin]

Hi Sean

I take it since you can ping the PDC and this machine has its default gateway set to the IP of the WinGate Server (or at least has a route so it knows how to get to the other end of the VPN).

If you have it set up like the other machine(srvr4) then another thing that might be causing this is the MTU size of the data packets that are being sent and recieved.

You could try reading our knowledgbase article (Under the VPN section) about finding out the best MTU size for the VPN here:

http://support.qbik.com/index.php?_a=kn ... ubcat&_i=2

Once you have found the right MTU size you can set this by opening up each Network connection properties in GateKeeper (found at the bottom of the Network tab)

At the top of the Advanced tab youll see an "Overide MTU setting"
Enter here you optimum MTU size.

Hope this helps

Erwin

[Sean123]

I solved the problem by assigning the gateway of the PDC to Wingate server. Thanks a lot!