Windows Server 2003 Enterprise accessbility problem
Hi,
I'm really getting frustrated because one of the server that I am in charge of, goes offline for some reason, only for determined computers.
And the same way it goes down, it comes up.
The computer affected aren't always the same, and it has not any kind of server side indication regarding errors or warnings.
Apreciate any sugestions.
May 18th, 2011 12:48pm
Hello,
what exactly does go offline mean, please describe in detail how you realize it.
Additional let's exclude some settings with posting and unedited ipconfig /all from the problem machine and the DC/DNS servers of the domain and a client not able to connect to the server.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 6:23pm
Sorry.
What i ment by "goes down" is that it becomes inacessible through network, and only to certain computers.
The clients aren't always the same, and the configs are passed through DHCP.
Here goes the affected server ip config
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER1
Primary Dns Suffix . . . . . . . : web.intra
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : web.intra
Ethernet adapter Network Team:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network T
Physical Address. . . . . . . . . : 00-16-35-7E-
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . : 192.168.1.25
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2
Secondary WINS Server . . . . . . : 192.168.1.1
May 19th, 2011 4:12am
Hello,
what machine is 192.168.1.1? Not a DC/DNS of the domain, as i asked about all DC/DNS server ipconfig's? Just a client ipconfig to compare, doesn't matter if that machine has problems at the moment.
For teamed NICs on a DC it is important to configure the team ONLY for FAILOVER, load balancing is not supported from Microsoft.
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2011 6:57am
Hi,
Here is the config of the Primary DC (the SERVER1 also has DC enabled, but is for failover pourposes only)
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER2
Primary Dns Suffix . . . . . . . : web.intra
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : web.intra
Ethernet adapter Network Team:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-16-35-05-99-F5
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.2
194.79.69.129
194.79.69.131
195.23.129.126
Primary WINS Server . . . . . . . : 192.168.1.1
Secondary WINS Server . . . . . . : 192.168.1.2
Now the client config
Configuração IP do Windows
Host Name . . . . .: 83SI
Primary Dns Suffix . . . . . . . : web.intra
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . . : No
WINS Proxy Enabled. . . . . . . : No
DNS Suffix Search List: web.intra
Adaptador ethernet Ligação de área local:
Connection-specific DNS Suffix :
Description . . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Con
nection
Physical Address. . . . . . . . . : 00-22-64-A5-11-7A
DHCP Enabled. . . . . . . . . . : Yes
IP Address. . . . . . . . . . . : 192.168.1.164
Subnet Mask . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . : 192.168.1.254
DHCP Servers . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . : 192.168.1.1
192.168.1.2
194.79.69.129
194.79.69.131
195.23.129.126
Primary WINS Server . . . . . : 192.168.1.1
Secondary WINS Server . . . . .: 192.168.1.2
May 20th, 2011 6:11am
Hi,
I noticed that you said “What i meant by "goes down" is that it (a DC which named SERVER1) becomes inaccessible through network, and only to certain computers”,
how did you access the DC? Via remote desktop? Do you have share folder on DC which cannot be accessed? Have you got any errors when accessing the share folders? Can you access the shares by IP directly? Please provide us more information on how the user found
the DC “becomes inaccessible”. Can you find any errors in Event Log on the problematic clients and on SERVER1? If so, please paste the event here for research. Does the issue persists if you restart the DC SERVER1? If so, please check whether Clean
Boot helps.
Boot in to Clean Boot mode on client
==============================
1. Click "Start", go to "Run", and type "msconfig" in the open box to start the System Configuration Utility.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click Disable All (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
4. Restart your computer. If the "System Configuration Utility" window appears, please check the box and click "OK".
5. Access DC, check whether the issue persists in this mode.
Thanks.
NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 6:12am
Hello,
remove all not domain DNS servers from the NIC on each domain machine:
194.79.69.129
194.79.69.131
195.23.129.126
After this run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on DCs and reboot clients.
To have internet access configure the FORWARDERS on the DNS server properties in the DNS management console with the ISPs DNS server or use the root hints.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
May 23rd, 2011 6:31am
Thanx for the feedback so far.
The affected machine (SERVER1) is a DC, but only for failover pouposes, because the main DC is SERVER2. This is mainly an SQL Server machine.
When, the problem happens, everything becomes inacessible, remote desktop, sql, shared folders, even ping commands (by dns and by ip).
there are no erros on event log, only the following warning "The time service has not synchronized the system time for 86400 seconds because none of the time service
providers provided a usable time stamp. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. Monitor the system events displayed in the Event Viewer to make sure that a
more serious problem does not exist"
I'll try to do a clean boot and see what happens.
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 6:47am
Thanx, I'll try this and give my feedback
May 23rd, 2011 6:48am