|
||||||||
|
|
#1
|
|
I have a user in a branch office that can only access the SYSVOL share on one
server, but can access every other share on every other computer/server. The branch office has 3 users behind a Watchguard Firebox which is set to create a VPN between the 2 offices. The other 2 users only occasionally have problems which are usually related to network traffic (through DSL). All users have the same network settings, although the other two computers are Windows XP and the problem one is Windows 2000. Digital signing has been disabled on the server which is a DC and the primary DNS server that this computer points to. There are no problems with name resolution; the user has rights to the folder but can't open them. They receive a message stating "The network name is no longer available." The event viewer log states "Windows cannot establish a connection to <domain name> with (<error code> = 0 ). WINS is enabled, a lmhosts file is on the computer, and it picks up the correct master browser. Any other suggestions on what to check or, better yet, how to fix this annoying problem? Daniel Sommerfeld |
![]() |
| Tags |
| accessible, folder, sysvol |
| Thread Tools | |
| Display Modes | |
|
|