Re: ISEE Proxy configuration security question (518 Views)
Reply
Occasional Contributor
Glenn Sorge
Posts: 5
Registered: ‎07-06-2007
Message 1 of 5 (518 Views)

ISEE Proxy configuration security question

I have a customer who uses proxy accounts to access the internet. To create a proxy account he needs to know what program ( exe or dll ) is used plus the port it accesses to send data to HP. This is ISEE 3.95 running on a Windows 2003 server
Trusted Contributor
ITRC Test-CH
Posts: 146
Registered: ‎07-20-2003
Message 2 of 5 (518 Views)

Re: ISEE Proxy configuration security question

This is a summary of the demands for all ISEE clients.

ISEE Supported transportations:
- All proxy servers conforming to the HTTP/1.0 specifications
- Tcp port 80 outbound with established back (ISEE Client)
- Connection directly to the Internet to access the HP backend

ISEE Not Supported transportations:
- NTLM authentication
- Kerberos authentication
- Proxy auto-configuration scripts

IMPORTANT
The ISEE Client software installation may fail if a customerâ s firewall or security software does content filtering.

Regards,
Werner
Occasional Contributor
Glenn Sorge
Posts: 5
Registered: ‎07-06-2007
Message 3 of 5 (518 Views)

Re: ISEE Proxy configuration security question

Thanks for that information, However my customer needs to know what program or dll opens port 80
Honored Contributor
Liem Nguyen
Posts: 306
Registered: ‎02-11-2003
Message 4 of 5 (518 Views)

Re: ISEE Proxy configuration security question


Glenn,

The process named mad.exe is the one that sends data to HP Backend over port 80.

Most people don't care about this process, what they do is allow the IP address of their Servers to get to HP Backend.

If they need to create a Proxy User, this user will be authenticated by their Proxy Server, the Proxy then allows or reject the connection,

Hope this helps,

Occasional Contributor
Glenn Sorge
Posts: 5
Registered: ‎07-06-2007
Message 5 of 5 (518 Views)

Re: ISEE Proxy configuration security question

Liem:

Thanks for the reply, I did a "netstat -b" and sent test messages and mad seemed to be the only process using HTTP at that time
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.