• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 520
  • Last Modified:

opening tcp port on a windows 2003 server

I have a windows 2003 server that is not responding on port 88. I have verified that the firewall is off and that the antivirus is disabled. after generating a report using netstat -ano I find that UDP port 88 is open and listening but TCP port 88 is not listed as an active connection. Is there a way to get the server to listen on TCP port 88 as well?

Thanks

Jim
0
jfholloway
Asked:
jfholloway
  • 4
  • 2
1 Solution
 
Paul MacDonaldDirector, Information SystemsCommented:
The Server itself won't be listening on any port.  There has to be a service that listens.  What service are you running that listens on port 88 and are you sure it's running?
0
 
jfhollowaySr. Systems AdministratorAuthor Commented:
I need port 88 for Kerberos traffic between domain controllers. I see it is active on one DC but, not on the other which is causing replication issues. I see on the one DC that port 88's PID is 416 and that PID is associated with lsass.exe. I am not sure why one DC has a servcie that is actively listening but, the other doesn't has a service that is listening on that TCP port.

That does explain why I can telnet to the server that is listening on port 88 but, not to the one that doesn't.

Is there a way that I can fix this on the DC that isn't working?
0
 
Paul MacDonaldDirector, Information SystemsCommented:
When troubleshooting DC/AD issues, the best thing to do is run a DCDIAG.  That will usually steer you in the right direction.

Also, any error log information can give you an idea where to look.
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!

 
jfhollowaySr. Systems AdministratorAuthor Commented:
I have 2 DC's in the domain and the one has tombstoned based on the dcdiag reports I collected last week. After I reset the secure channel password I was able to get DNS back online. Right now I can't replicate, dcpromo the server because it can't communicate with the other DC and I can't transfer(or seize) the FSMO roles from the bad DC to the good one because of communication errors which led me to isolate which ports were and weren't responding.
According to TCPview and netstat the bad server (service) is not listening on the required ports for A.D. and the KCC to communicate properly. I believe if I can get communication working on TCP ports 88, 123, 137, 138, 139 and 3268 I can possibly remove the lingering objects and continue replication.

Any suggestions on where I can look to see why the server service isn't listening on the needed ports?
0
 
Paul MacDonaldDirector, Information SystemsCommented:
If there's no firewall or other impediment to communication, it seems likely the service isn't running.  Check that.  Check the error logs for any information that might offer insight.

If you can't get the problem DC to communicate, you can seize the roles it holds (the whole point of seizing is to recover from a failed DC).
0
 
Paul MacDonaldDirector, Information SystemsCommented:
Thank you for the points, but I'm curious about the "C" grade.  Was the answer not satisfactory?
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

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now