Blocking a windows service vs. a desktop Application (NPF 2005)

In testing compatibility with Norton Personal Firewall 2005 for an in-house app (that I wrote) I find that I can set a rule to permit it communicating with a non-pc IP device on a given port (1325) when testing it running as a desktop app, but that rule doesn't seem apply when running the same application as a service.

In other words: The port is open when running on the desktop but blocked when running as a service.

The application runs either way simply by adding a command line switch and starting it from the command prompt rather than having the Service Control Manager run it. So, I'm pretty confident that I comparing apples to apples.

Can anyone offer some insite on how I can configure a rule to apply to the service?

TIA

Reply to
TXBueller
Loading thread data ...

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.