Server Disconnect Beyond my scope!

gglover · 09-11-2006, 09:58 AM

Hi there~

I'm a self-employed custom developer, mainly database/office applications. I'm doing a project for a client who has a small (15 workstation) WIN Svr 2003 network. It was set up by a previous non-tech employee who wore a lot of hats - including application development and network maintenance.

I have worked with servers and can do minor work with Active Directory, etc., but I am no network administrator and there have been some things happening that I have not been able to figure out. May be simple to folks who deal with this stuff all the time...I hope so, at least.

Symptoms:

Periodically, all users are abruptly disconnected. We've learned that rebooting the server will allow reconnection, but it also seems that sometimes a reboot is not necessary, although the mapping has to be removed and reestablished at the workstations.

Their cabling is an absolute mess, and I'm wondering if the server's connection to the network may be glitching.

They have a 15 user license, although not all workstations are connected concurrently. It is possible that a 16th could try to connect, but I do not know the server's response to this - surely it would just disallow the connection rather than throwing everyone off....surely.....???

There are only two errors I have noted from the Event logs, but the timing is not always in sync with the problems.

a) Product: Windows Operating System Event ID: 4007 Source: DNS Version: 5.2 Symbolic Name: DNS_EVENT_DS_REGISTRY_DP_INVALID Message: The DNS server was unable to open zone %1 in the Active Directory from the application directory partition %2. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone.

b) The computer OFFICE11 tried to connect to the server \\SOMSERVER using the trust relationship established by the COASTSOM domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.

I have purchased two huge books for svr 2003 but can't find these things in there. It's probably that I don't know enough in general to be looking in the right place, and there are a gazillion "places", so I'm hoping for some guidance.

I am also trying to convince the owners to let me try to find a "network guru" who can take a look at things and make a list of any physical and configuration issues. So far they've just been willing to live with these occasional problems, but obviously the set up is somewhat less than optimum.... (!)

Any suggestions as to diagnostic procedures and/or what areas I might research are gratefully accepted.

- Gary

whardman · 09-11-2006, 02:53 PM

Looks to me as if the domain name was changed without the other computers being configured for the new domain. I would probably remove the computers from the domain and demote the server. Then promote the server back to a domain controller, and reconnect the computers. This should clear up some of the issues if not all of them.

gglover · 09-25-2006, 09:29 AM

Whardman, I apologize for my lateness in responding, but I DO very much appreciate the suggestions.
I have a couple of questions, mainly about what can be done from the server and what has to be done from each workstation, but I'm sure it'll be fairly clear once I read up on the topics of promotion/demotion.
One of the error events I had noticed had to do with other workstations announcing they were domain servers as well. It was only an occasional thing, but whatever it is, it must indicate a less-than-optimum (to say the least) configuration.
Thanks again for your help.

-GGG

09-11-2006, 09:58 AM	#1 (permalink)
gglover Registered User Join Date: Sep 2006 Posts: 2 OS: WIN XP	Server Disconnect Beyond my scope! Hi there~ I'm a self-employed custom developer, mainly database/office applications. I'm doing a project for a client who has a small (15 workstation) WIN Svr 2003 network. It was set up by a previous non-tech employee who wore a lot of hats - including application development and network maintenance. I have worked with servers and can do minor work with Active Directory, etc., but I am no network administrator and there have been some things happening that I have not been able to figure out. May be simple to folks who deal with this stuff all the time...I hope so, at least. Symptoms: Periodically, all users are abruptly disconnected. We've learned that rebooting the server will allow reconnection, but it also seems that sometimes a reboot is not necessary, although the mapping has to be removed and reestablished at the workstations. Their cabling is an absolute mess, and I'm wondering if the server's connection to the network may be glitching. They have a 15 user license, although not all workstations are connected concurrently. It is possible that a 16th could try to connect, but I do not know the server's response to this - surely it would just disallow the connection rather than throwing everyone off....surely.....??? There are only two errors I have noted from the Event logs, but the timing is not always in sync with the problems. a) Product: Windows Operating System Event ID: 4007 Source: DNS Version: 5.2 Symbolic Name: DNS_EVENT_DS_REGISTRY_DP_INVALID Message: The DNS server was unable to open zone %1 in the Active Directory from the application directory partition %2. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. b) The computer OFFICE11 tried to connect to the server \\SOMSERVER using the trust relationship established by the COASTSOM domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship. I have purchased two huge books for svr 2003 but can't find these things in there. It's probably that I don't know enough in general to be looking in the right place, and there are a gazillion "places", so I'm hoping for some guidance. I am also trying to convince the owners to let me try to find a "network guru" who can take a look at things and make a list of any physical and configuration issues. So far they've just been willing to live with these occasional problems, but obviously the set up is somewhat less than optimum.... (!) Any suggestions as to diagnostic procedures and/or what areas I might research are gratefully accepted. - Gary

09-11-2006, 02:53 PM	#2 (permalink)
whardman Registered User Join Date: Jun 2006 Location: Cincinnati, Ohio Posts: 617 OS: Windows XP My System	Looks to me as if the domain name was changed without the other computers being configured for the new domain. I would probably remove the computers from the domain and demote the server. Then promote the server back to a domain controller, and reconnect the computers. This should clear up some of the issues if not all of them.

09-25-2006, 09:29 AM	#3 (permalink)
gglover Registered User Join Date: Sep 2006 Posts: 2 OS: WIN XP	Whardman, I apologize for my lateness in responding, but I DO very much appreciate the suggestions. I have a couple of questions, mainly about what can be done from the server and what has to be done from each workstation, but I'm sure it'll be fairly clear once I read up on the topics of promotion/demotion. One of the error events I had noticed had to do with other workstations announcing they were domain servers as well. It was only an occasional thing, but whatever it is, it must indicate a less-than-optimum (to say the least) configuration. Thanks again for your help. -GGG