Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 328
  • Last Modified:

SBS 2003 Exchange stopped working remotely

As of this morning, users outside the LAN cannot access Exchange. Internal users are still getting emails.

In the event log at the time Exchange remote connectivity was lost there are the following event logs.

LDAP Bind was unsuccessful on directory FZ1.xxx.local for distinguished name ''. Directory returned error:[0x34] Unavailable.    

Process MAD.EXE (PID=3280). All Domain Controller Servers in use are not responding:
FZ1.xxx.local
 
Any suggestions?
0
OZSJ
Asked:
OZSJ
  • 7
  • 5
1 Solution
 
joelsplaceCommented:
Have you checked all the Exchange services to make sure they are running?  That's almost always the problem when this happens to me.
0
 
OZSJAuthor Commented:
Ye, Exchange appears to be all good. After some more digging it appear that IIS default website is not running. (all remote users use RPC/hhtp). When I try to enable the default website i says another process is using this port. However looking at netstat shows nothing using port 80... so still a bit lost.

As a temporary solution I have changed iis port 80 to 8080, and created a virtual port forward on the router for port 80 external to port 8080 internal. Works for the moment, but would like to figure out what is using port 80.

Strange.
0
 
joelsplaceCommented:
Did you install anything that might be attempting to use that port?
Have you rebooted?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
OZSJAuthor Commented:
No, installed nothing. Rebooted a couple of times. We did have an old vmware server running on this OS. Vmware server was running Win 2008 and we no longer need it so I shut it down this morning, shortly before email problems started. But I have shutdown this virtual server many times before and believe the timing must be a coincidence.

I have installed TCP View to check what is using port 80. Again nothing is listed for port 80 although I can see that http port listed as a system process. No process ID.

The timing of this is very unusual. The server has worked for many years with barely a hiccup.

My temporary solution of changing port to 8080 appears to work for all except iphone and ipad. Not sure why.








I have
0
 
joelsplaceCommented:
I would try to figure out what that process is and why it's there.
0
 
OZSJAuthor Commented:
Any ideas on how? There is no information on this process. I can kill it, but as it is a system process not sure what will happen.
0
 
joelsplaceCommented:
Have you tried Process Explorer to see what it says about it?
0
 
OZSJAuthor Commented:
Thank Joel. In the end I found the process that was using port 80 by deleting most startup processes. I had forgotten about process explorer. Great tip.
0
 
joelsplaceCommented:
Glad it's fixed.  What startup process was it?
0
 
OZSJAuthor Commented:
It was an online backup program. Fantastic app sp I will not name it here.
0
 
joelsplaceCommented:
Ok.  Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now