Cicso VPN client worked but now does not on Win2k server domain

[sbroskie]

Hello,
I had the following configuration:
Win NT 4.0 PDC
Win 2k Prof workstation 1
Win 2k Prof workstation 2
Red Linux 7.2 firewall/router using IPTables, has cable modem attached

My wife uses Cisco VPN Client 3.1 for connecting to work (which really stinks by the way). Before I upgraded my NT 4 box to Win 2k everything worked fine.

The following now are the symptoms of my problem using a Win 2k Server as my domain controller:

I can connect to the remote VPN w/ no issues
I can ping the NT servers on their side by IP and by NetBios name with no issue.
I can attach to a pc on the VPN end with PC Anywhere.
I can open up a Telnet session of the VPN end.
I -cannot anymore- attach to a share on any of those remote servers.

I receive the following error after a lengthy amount of time:

"\\ServerName is not accessible.
There are currently no logon servers available to service the logon request."

I went ahead and installed the VPN client on the second workstation by the same symptoms occur.

Nothing else has changed other than the upgrade to the NT Server box. Is the Win 2k server 'imposing' some policy down on the workstation?

Any ideas/comments are welcome.

Thanks in advance!

 

[LastWords]

Yes I am having the same problem, I can ping and do most things, except resolve host names, and hence i cant either see network shares or make network shares.
I have got the VPN working on a client 98 machine but not on a windows 2000 client, it looks like it is a bug with windows 2000 pro. by Lastwords,

Maentwrog (n.Welsh): Celtic word for a computer spelling mistake.

 

[ronnieppsi]

I stopped the netlogon service, changed it to manual, rebooted and hey presto I could map drives.However, I thougt my user will not be able to logon whilst in the office via the network as the logon service is not running. Amazingly enough he can! So I think the answer appears to be stop the service and put it onto manual.
More news on net logon service.This service is used for nt domains. If you have a Windows 2000 domain using active directory, the authentication protocol is kerberos. W2k client uses kerberos if it exists then looks for net logon if not. So the solution will work with no detriment if the client is logging on to a windows 2000 domain.Hope this helps!