Port 17070?

[Ruckus]

Newbie Alert - I’ve been lurking for a while, but this is my 1st time posting on this forum.

I took over admin duties for Deadline 6.0 a year ago, and upgraded that to 7.0 about a month ago. When I upgraded to 7.1.0.21 a few days ago, we lost the ability to send remote commands to the Slaves (restart slave, restart machine). Other info: We are using all Windows 7 SP1 clients, the repository/DB server is Windows Server 2008 R2. We are not using Pulse (yet).

I noticed that these remote commands are all trying to use port 17070. That port is not mentioned anywhere in the documentation.
In Deadline 6 & 7.0 these were all the Firewall Rules I needed:

I can easily create a firewall rule to allow that port, but before I do I want to know 2 things:

1. Why do I need need to do this in 7.1, but did not need to do it in 7.0 or 6.0?
2. Is there a better way - maybe allowing a program access rather than a port?

Any help will be appreciated,
Dave

[rrussell]

Hey Dave,

This is the default port that the Deadline Launcher listens on for remote commands. The default is auto-generated based on the major version number, so that’s really odd that you didn’t have this problem previously with 7.0 because the default port number wouldn’t have changed.

You could just open up the Deadline Launcher application, instead of explicitly enabling port 17070.

Cheers,
Ryan

[Ruckus]

A firewall rule for deadlinelauncher.exe did not help - but a rule for deadlinelauncherservice.exe did!

Thanks, Ryan!

I suppose I can get rid of those rules for 17060 & 17061 then.
(Obviously firewalls are not my specialty)