Jump to content

Window 2003 Server Firewall blocks communication with clients


Recommended Posts

It is evident that UDP/TCP ports 497 are not the only ports Retrospect 6.5 uses to communicate with Clients. When utilizing piton multicast to locate clients on the subnet, Retrospect clients communicate back to the server listening through random UDP ports such as 1591. This is easily seen by running netstat before and after trying to add new clients. Each time an add is attempted using the multicast the ports that the server is listening on change: for example; from 1591 to 1595. Because the firewall settings on Windows 2003 server are static it is not possible to select ports to leave open for the server to listen for client responses.


Is there a way to set a fixed port for server to listen on? Or maybe some other workaround?

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...