Problems using proxy

[norcis]

Hello,


Great job!

I'm trying to migrate from SC to PCHW.
There is problem with proxy. In my company, we use proxy to connect to internet (it looks like, we use ISA server and Microsoft Firewall Client for ISA server 2004). We use http://srvproxy:80 for connection.
PCHW detects it, but can't connect through it.

I got such information:


------------------------------
relay_method:HTTP (3)
relay_host: SRVPROXY
relay_port =80
relay_user=username_in_domain
local_type=socket
local_port=1111
dest_host=reapeater_ip
dest_port=443
not matched, addr to be SOCKSified: reapeater_ip
resolved host by name: SRVPROXY
resolved: SRVPROXY (local_proxy_IP)
connecting to local_proxy_IP:80
begin_http_relay()
Unsupported authentication type: negotiate
Unsupported authentication type: kerberos
Unsupported authentication type: ntlm
Can't find Proxy-Autjemticate: in response header.
Using reapeater
.......
--------------------------


Also, I have created UI for SC with custom functionality and want to use it with PCHW. I need to execute PCHW by passing connection parameters to it. After this, PCHW should automatically connect to repeater.

Can this be done?


Best regards,
Andrius

[norcis]

Oh, I downloaded source code and found UI code.
Like I understood, I can create my own UI.


Also I have question about autoreconnect option. It reconnects after server disconnects from viewer. How viewer should close connection, than server quits? Does autoreconnect works after computer reboots?


Thank you.

[redge]

Does autoreconnect works after computer reboots?

No, except if you modify UI for push pchelpware_server to Startup folder or RunOnce

not work direct dynalias
-connect 123.123.123.123 -autoreconnect -direct should added to helpdesk.txt

[norcis]

No news about using proxy? I can't make it work

[alex74]

Hi, I have the same problem with authentication and ISA Server.
The debug windows outputs:
Unsupported authentication type: negotiate
Unsupported authentication type: kerberos
Unsupported authentication type: ntlm
Any idea with this?

Thanks.
Alex

[alex74]

Hi, I figured out the way to work it out in ISA Firewall. The problem is that by default ISA Server is configured to disallow Basic authentication. So you can enable it going to Configuration, Networks and select your network properties you want to change. This setting is in the WebProxy tab, in the Authentication button.

It would be very nice to allow NTLM or Kerberos authentication since it's the most secure way.
Any news to find a way to input the user name from SCIII?

Thanks.
Alex

[Xavi]

Any other solution if unable to access the ISA Server to allow basic authentification?

[X-Byte]

The only way to use Basic Authentication in that case is, to use a local proxy that is able to authenticate to the ISA Server using NTLM.

The only reliable and free program I found is NTLMAPS. It is a python program, so you need to install the Python runtimes to run it.

All informations and downloads here: http://ntlmaps.sourceforge.net/

A small drawback of this solution is, that you have to specify your Username and (optionally) password in server.cfg. Unfortunately NTLMAPS doesn't automatically use the currently logged in user's account&password.

Anyways, I learned to live with it and my applications that don't support NTLM work with NTLMAPS without a problem