• Previous message: Atkins, Richard J (Richard): "proxy-name problems"
• Maybe in reply to: Atkins, Richard J (Richard): "proxy-name problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello again,

I've got a little further on this problem, but name resolution still
isn't working correctly for me:

1) It just flat out refuses to work for me with any app under XP
SP1.

2) It appears to work a little better under 2K SP4:

a. telnet works correctly: 'telnet test.noresolv.com' correctly
forwards through the socks server.

b. When told to go to 'https://test.noresolv.com', IE and firefox
both try to connect to IP addresses like '0.0.0.1', and these connection
attempts wind up at the socks server, but these servers don't exist so I
get each browser's error page.

It looks to me like the browsers are somehow mangling the magic IP
address that Hummingbird gives them in response to the
gethostbyname/WSAAsyncGetHostByName call, and so Hummingbird then
doesn't correctly intercept the socket call. Is this correct? Is there
anything I can do to get this to work?

I'm also trying to use the Hummingbird shim with a Juniper Networks
SA5000 box, with either of its two tunnelling apps Network Connect or
Secure Application Manager. The SA5000 is directly reachable. I've
discovered that having Hummingbird and SAM installed at the same time
crashes the client OS. Do you know if there's any workaround for this?
Do you know if there are any conflicts with Network Connect?

Thanks,

            Richard

-----Original Message-----
From: Atkins, Richard J (Richard)
Sent: Tuesday, 19 April 2005 3:12 PM
To: ' '
Subject: proxy-name problems

Hi all,

I'm trying to configure Hummingbird Socks 8.00 to do authentication and
hostname resolution for simple HTTP and maybe some other TCP based
traffic (the SOCKS server doesn't support UDP associate, nor bind
commands). I can't just use a straight through SOCKD5 server, since the
socks server is also a firewall. My socks.cfg looks like the following:

PROXY-NAME @=192.168.1.1:9001

The problem is that IE doesn't seem to perform any lookups through the
socks shim - it just goes straight to showing "The page cannot be
displayed" with the status message "Cannot find server or DNS Error".

Is there something else I'm supposed to do to get this to work?

Thanks for your help,

            Richard

• Previous message: Atkins, Richard J (Richard): "proxy-name problems"
• Maybe in reply to: Atkins, Richard J (Richard): "proxy-name problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 30 2005 - 23:54:02 EDT