Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

http requests for client problem

Dec 11 05 10:51 pm

Hi

I have this problem with Wingate 5.0:

I have a client machine (FreeBSD 5.4) connected to winXPPro as it's gateway, which in it's turn is connected to the internet (aDSL). Wingate is on XP. Now, I cannot get on the Internet fron UNIX box. HTTP requests are sent but nothing happens afterwards. It just sits there displaying plank page. Default gateway on BSD is set to 192.168.0.1 (XP internal IP), no firewalls enabled. Does this setting supposed to work or I need to modify some configuration settings for BSD? I can ping any Internet addresses from UNIX, resolv.conf file points nameserver to what my ISP have provided and all looks fine except for no HTTP is coming back to the client. On Wingate firewall has no entries and would assume it is not active. I also, just in case modified Wingate's firewall to allow practically anything in and out.
On BSD box --- when setting proxy connection, what port I have to put after IP address of a proxy server: HTTP_PROXY="http://192.168.0.1:xxxx???? do not know the port #.
Help me please.

Alex16

Dec 12 05 12:22 am

By default Wingate binds HTTP proxy to port 80 - whern your BSD machine connects, do you see an HTTP session in Gatekeeper?

Dec 12 05 1:58 am

Yes, there is 'DNS: lookup www.ibiblio.org' line,
then 'NAT: TCP Connection to 152.2.210.80:80'

Lynx just says: 'HTTP request sent; waiting for response'

I am using Lynx as my (for now) web browser from the command line as BSD just been installed and nothing else besides Lynx is there. I cannot download anything using 'make' from my ports collection, for example to install Mozilla, 'coz 'fetch file from http://.....' fails as well. 'Fetch' might connect to the requested server but will not start the actual download.

Here is Wingate's output for a simple 'ping' command:

'DNS: lookup www.google.com'
'NAT: ICMP 192.168.0.2<->66.249.93.104'
and 'ping' is success.

Thinking that may be something is missing in my BSD installation. Will try to re-install it.

I will keep trying

Thank you

Dec 12 05 10:17 am

Hmmmm.... Looks like it goes through fine - can you try FTP just to make sure NAT works properly?

Dec 12 05 8:50 pm

I'm reinstalling BSD right now and will try again tonight when back home from work. Thinking that may be TCP stack didn't install properly the first time. Will let you know how did it go.


Thank you


Alex16


p.s. I don't think it's Wingate related problem because I had the same simpthoms when using windows ICS. The above worked fine with MS Windows based clients before. I surely will post a soluting here once I got this figured.

Dec 12 05 9:03 pm

So, as I understand all I need to do in order to connect to the Internet is to define a default gateway (the computer with Wingate server) on the client side and that should be enough, right?


Alex16

Dec 12 05 9:08 pm

Yes, that's correct. I'd also suggest, that you set your DNS server to be the Wingate machine.
Post a reply