Greetings,
My employer has an off the shelf (yeah, right) software package that
requires access to an SQL-server database that is located outside our
internal network at a remote vendor. We are accessing this vendor's
database through the Internet by (successfully) opening a firewall port for
the database traffic, but the application also requires port 135 (the DCOM
service locator port) in order to work.
Apparently, Eagle Raptor version 5.0 (we're migrating to a Firewall-1
implementation soon) blocks port 135 in such a way that I have been
unsuccessful at allowing access to the vendors port 135. I've attempted to
simply define a GSP service for it and created a rule that allows port 135
service between inside and outside servers, but that does not work.
If port 135 traffic can be allowed from internal to external networks in
any way I would be incredibly appreciative for an explanation of how I
might do that.
Thanks.
Rob Scott
May God help me to be the person that my dogs think I am.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Scott, mailto:[EMAIL PROTECTED]
Langley, Washington on Whidbey Island (a suburb with a moat)
Network Security Specialist for Alaska Airlines
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
