Windows Server unable to see rest of network

August 25, 2010 at 04:56:12
Specs: Windows Server 2003 Standard Edition
I hope someone can help me. I'm a little out of my depth when it comes to Servers, but I recently messed around with one of our servers, and now it can't see any of the shares on the other machines.

There are two servers running Windows Server 2003 Standard. One has the print and file share and the other runs a webserver. The webserver appears to be isolated from the rest of the network, in that it cannot navigate to such addresses as \\\Home which is our home share on the second server. Similarly, I cannot access it's www folder share.

I'm not sure what I've done, other than what I was trying to do, which was set up Active Directory. I'm going to hazard a guess and say that it's due to the Domain Controller that gets installed that's messed things up. I've subsequently removed AD and DC from it and tried to revert back to the way it was, but I'm failing on this minor point.

I could really appreciate any guidance on getting the machines all talking again.

Many thanks in advance.

See More: Windows Server unable to see rest of network

Report •

August 25, 2010 at 10:16:07
How did you remove AD? DCpromo down?
Did you rejoin the workgroup?

Report •

August 25, 2010 at 13:30:33
To remove AD and DC I ran the "Manage Server" and removed the Directory Services service.

How would I make the server rejoin the workgroup?

Thanks for your help.

Report •

August 26, 2010 at 08:14:52
That is not how you remove AD

Near the end of this link tells you how to join a workgroup. It's just like you do with a workstation.

Might want to get a 2003 server book or do some research on the internet before you attempt any further changes. Otherwise you may find yourself in a hole to deep to get out of.

Report •

Related Solutions

August 26, 2010 at 08:35:39

Thanks for the response - the first link reads very close to how I did remove AD. The only difference is that I selected the option to remove the domain from the forest, as it was the last DC.

The second link doesn't appear to be much use as this seems to be something that's done during an install of the server os. I found this link that seems to have offered the method instead:

However, neither really helped. I've "re-joined" the workgroup, but the server still appears to be isolated from the rest of the network.

I have a book on server 2003 - however I can only read so fast and the book has over 600 pages. I put my trust (maybe unwisely) in the Microsoft interface and followed it as it suggested. I appreciate your concern for the hole I could get myself into, but I've come to learn there's always a fix - even if I have to rebuild the server (although I'm trying to avoid it if I can).

Thanks for your help so far, do you have any other thoughts?

Report •

August 26, 2010 at 11:16:32
post the results of an ipconfig /all from this server and from a workstation for review. This may give us a clue where to look

Report •

Ask Question