We recently upgraded our Windows NT4 server to Win2K and implemented AD. Previous to the upgrade, we had a Win2K acting as a VPN routing with two nics, and all clients had access to the Windows NT4 controlled network (life was good).
After upgrading to Win2K, and not changing a thing on the win2k VPN, we discovered only win2K and above (XP) clients could login in and have full access to the network, on the VPN side (LAN connectivity is fine). Win9x (and ME) can obtain a proper address from DHCP, sign-on, get authenticated, browse the network, drill down on the folders on the server - BUT if any form of data manipulation (copy file, rename file, move, delete) is attempted, explorer freezes and eventually comes back with a stupid error such as "folder no-longer available" - but am not kicked off the network - could still move around just fine.
If I have the same account attempt the dial-in with a win2k or higher - no problem.
Any ideas would be much appreciated.
After upgrading to Win2K, and not changing a thing on the win2k VPN, we discovered only win2K and above (XP) clients could login in and have full access to the network, on the VPN side (LAN connectivity is fine). Win9x (and ME) can obtain a proper address from DHCP, sign-on, get authenticated, browse the network, drill down on the folders on the server - BUT if any form of data manipulation (copy file, rename file, move, delete) is attempted, explorer freezes and eventually comes back with a stupid error such as "folder no-longer available" - but am not kicked off the network - could still move around just fine.
If I have the same account attempt the dial-in with a win2k or higher - no problem.
Any ideas would be much appreciated.