Hello all,
We are having a bizare situation here - First, the truely bizare part:
Every Friday, our VPN users cannot connect to the file server anymore. They can connect to the Exchange server no problem, but if they try to access a shared drive, XP bounces back with a message indicating multiple shared connection aren't allowed, etc...
This occurs only on Friday's, every week. Furthermore, everyone in the office has no problems accessing the services.
Now, to diagnose the problem, the first thing I did was run DCDIAG.exe with no flags. I also double checked our primary and secondary DNS servers and both had the correct enteries for the server. The DCDIAG output I recieved follows:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVERADC
Starting test: Connectivity
The host 8e9146b0-f318-4452-b294-2c7c6c6b2710._msdcs.company.local could
not be resolved to an IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(8e9146b0-f318-4452-b294-2c7c6c6b2710._msdcs.company.local) couldn't be
resolved, the server name (serveradc.company.local) resolved to the IP
address (192.168.1.30) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... SERVERADC failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVERADC
Skipping all tests, because server SERVERADC is
not responding to directory service requests
Any thoughts on this? Any help is much appreciated, thanks!
S
We are having a bizare situation here - First, the truely bizare part:
Every Friday, our VPN users cannot connect to the file server anymore. They can connect to the Exchange server no problem, but if they try to access a shared drive, XP bounces back with a message indicating multiple shared connection aren't allowed, etc...
This occurs only on Friday's, every week. Furthermore, everyone in the office has no problems accessing the services.
Now, to diagnose the problem, the first thing I did was run DCDIAG.exe with no flags. I also double checked our primary and secondary DNS servers and both had the correct enteries for the server. The DCDIAG output I recieved follows:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVERADC
Starting test: Connectivity
The host 8e9146b0-f318-4452-b294-2c7c6c6b2710._msdcs.company.local could
not be resolved to an IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(8e9146b0-f318-4452-b294-2c7c6c6b2710._msdcs.company.local) couldn't be
resolved, the server name (serveradc.company.local) resolved to the IP
address (192.168.1.30) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... SERVERADC failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVERADC
Skipping all tests, because server SERVERADC is
not responding to directory service requests
Any thoughts on this? Any help is much appreciated, thanks!
S