Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


411 posts

Ultimate Geek


Topic # 60011 16-Apr-2010 10:04
Send private message

Hi There,

My SBS 2003 Server, all of a sudden has stopped accepting anything.

When i double click on network drives it says that it cant find the server (From a client PC)

I cant ping the server from any other pc
I cant go to the web address of the server.
Exchange wont connect to the server.

On the server itself, everything appears to be going fine, I can access OWA locally on the server, and can access and ping other computers and devices on the network.

No idea what has happened to it...

Would anyone know how to fix this? :)

Create new topic
BDFL - Memuneh
61205 posts

Uber Geek
+1 received by user: 11982

Administrator
Trusted
Geekzone
Lifetime subscriber

  Reply # 319254 16-Apr-2010 10:33
Send private message

Perhaps some changes in the IP configuration on the ethernet adapter you are not aware? Or the Firewall rules were modified to block everything? Any third party software installed lately?




264 posts

Ultimate Geek
+1 received by user: 95


  Reply # 319285 16-Apr-2010 11:13
Send private message

When you try to access the server from a client, does it work if you use the IP address instead of the server name (that would indicate a DNS issue)?

Amanzi
879 posts

Ultimate Geek
+1 received by user: 90

Trusted
Subscriber

  Reply # 319345 16-Apr-2010 13:18
Send private message

The first question: has anything changed recently?
Second question: have you looked in the event logs?

8 posts

Wannabe Geek


  Reply # 319359 16-Apr-2010 13:47
Send private message

Try adding the registry key as described in

http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-prop...

and restart the server

Amanzi
879 posts

Ultimate Geek
+1 received by user: 90

Trusted
Subscriber

  Reply # 319362 16-Apr-2010 13:50
Send private message

tawilson: Try adding the registry key as described in

http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-prop...

and restart the server


Obviously you should check the event logs first to see if this really is the cause of the problems. :-) 

1085 posts

Uber Geek
+1 received by user: 65


  Reply # 319451 16-Apr-2010 16:46
Send private message

Had a very similar situation awhile back and it turned out to be a port issue.

What had happened was the DNS Server service had started before the ipsec service had and assigned itself the port that ipsec needed.

Quick fix was to stop the DNS server service and then start the ipsec service, then restart the DNS Server service.

The long term fix is to exclude the port for ipsec from the range DNS can use (I can't remember the port numbers but there is a MS KB article for it)

1085 posts

Uber Geek
+1 received by user: 65


  Reply # 319452 16-Apr-2010 16:48
Send private message

here is the link to the KB Article for the issue:

http://support.microsoft.com/kb/956189

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.