Joe, can you confirm the app that's listening on that port?  

Do you have other applications on the client that might be using that port
to connect? 

What kind of traffic do you see destined for that port on the wire?

There's no set reason that port would be used out of the box that I'm aware
of other than just luck.

One other thing to check: Windows XP SP2/Ol2003 have a way to get around the
update port used without specifying the server to listen on a particular
port. This allows UDP notifications even with the firewall enabled.  What
they do is pre-seed the registration of the client for new mail notification
via GPO settings.  I haven't looked on the wire to see if the client will
poll the server on that same port in the case of not getting a new mail
notification after a certain amount of time, but I suppose that's possible.
It's supposed to result in the client listening on a predetermined UDP port
vs. talking to the server on a predetermined TCP port.





-ajm 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pelle, Joe
Sent: Monday, February 14, 2005 10:52 AM
To: [email protected]
Subject: RE: [ActiveDir] OT:Exchange 2003 TCP 18053

Tony,

 

Thanks for the quick response!  It doesn't appear that we have a static port
assigned though.

 

Joe Pelle

Senior Infrastructure Architect

Information Technology

Valassis / IT

19975 Victor Parkway Livonia, MI 48152

Tel 734.591.7324  Fax 734.632.6151

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

http://www.valassis.com/ <http://www.valassis.com/> 

 

This message may have included proprietary or protected information.  This
message and the information contained herein are not to be further
communicated without my express written consent.

 

________________________________

From: Tony Murray [mailto:[EMAIL PROTECTED]
Sent: Monday, February 14, 2005 10:36 AM
To: [email protected]
Subject: RE: [ActiveDir] OT:Exchange 2003 TCP 18053

 

Could be that you have a statically mapped port assignment for a particular
service (NSPI Proxy, IS, SRS, etc.).  Check out the following article.  You
can the look for the corresponding registry entries.

 

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

 

Tony

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pelle, Joe
Sent: 14 February 2005 16:28
To: [email protected]
Subject: [ActiveDir] OT:Exchange 2003 TCP 18053

 

Hello! 

 

When I do a netstat -an on my Exchange 2003 server I see a lot of
connections on TCP 18053.  All of our email clients connect to this Exchange
server and just about all of them appear to have a connection via this port.
No one seems to have any idea what that traffic could be... 

 

Does anyone have any ideas?  

Any help or insight is greatly appreciated! 

 

Joe Pelle

Senior Infrastructure Architect

Information Technology

Valassis / IT

19975 Victor Parkway Livonia, MI 48152

Tel 734.591.7324  Fax 734.632.6151

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

http://www.valassis.com/ <http://www.valassis.com/> 

 

This message may have included proprietary or protected information.  This
message and the information contained herein are not to be further
communicated without my express written consent.

 

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to