Simple thing, but... (RAS)

[Surfer]

Hi there!

I am confused about one simple thing. I did it without troubles some years ago on Windows NT 4 server and Wingate 4.0, but now it's not
working on Windows 2000 server SP4 and Wingate 6.1.1. :(
Facts:
- server have a modem for incoming calls, lan card for local net and ADSL line for web access
- all working fine from server side
- all working fine from clients in local net
- created incoming connection for modem, configured and selected
static pool from 128.1.0.189 to 128.1.0.190, added in assume list and
services, no firewall enabled
- client call by modem, connected and got an address from pool
- in a browser he select "connect thru proxy" and type ip and port of WWW service
- but he haven't web connection! WHY?
Wingate doesn't show anything in log. No "guest" connections or something. Just like client from modem disappeared. However he can ping proxy! What it may be?

[Pascal]

Do you have a binding policy for the web proxy that will include that device?

[Surfer]

Oh, my...! :) Of course not.
But... i can't see this device in binding list. Nothing to add.
Is it appear only when he is in active state? (connected)
Add "all adapters" is a bad idea as i think.

[Pascal]

You are setting up a binding policy (If you are using 6.x of WinGate). So, set the policy to be "bind to all internal/external adapters" as appropriate.

[Surfer]

Yes, I did it.
But still not working.
I can ping a proxy from modem, can connect to gatekeeper or connect to server by terminal service, but can't connect to www. Nothing appeared in the log of gatekeeper.
Looks like some type of firewall are between modem and proxy. However no firewalls installed.
:(

[Pascal]

What type of adapter is it detected as? (Internal/External)

[Surfer]

What type of adapter is it detected as? (Internal/External)

Incoming connections (WAN (PPP/SLIP) interface)

[Pascal]

Sorry, I'm interested in what the "Useage" column for that device indicates (Internal / External). This tells us what set of firewall rules are being applied to it. I suspect it might be detected as "External", in which case it's being firewalled.

[Surfer]

Oh, i'm sorry.
Yes, it shows as "external".
I switch it to "internal", but nothing happens anyway.
Gatekeeper firewall still in disable state.

[Pascal]

- created incoming connection for modem, configured and selected static pool from 128.1.0.189 to 128.1.0.190, added in assume list and services, no firewall enabled

You are using public IPs for that static pool.

[Surfer]

Changed to private (192.168 series). No effect.

[Pascal]

Ok, from the command line run:

"netstat -an"

What you are looking for is an entry that indicates it will be listening on the appropriate port there. So, for example:

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 192.168.0.67:80 0.0.0.0:0 LISTENING

either of the two BOLD lines would indicate something listening on port 80 on my machine. Verify that you have something listening on your machine on the IP address that you expect dial-in users to connect to.

[Surfer]

Yes. I see an IP with port 8010 in listening state. 8010 - is my WWW proxy port (log server moved to another).
But I must note that IP's of my WWW proxy and dial-up static pool are not in one subset. May be it is a clue?
Originally they was in one. So, when i moved to 192.168 band they come different.

[Pascal]

Ok, well - you need to make it so that you have WinGate listening on the IP you expect the dial-in users to connect to. Then you need to ensure that there are no firewalls / other traffic-blocking devices inbetween the two.

[Surfer]

I found it!
I connect to server by modem, trying...nothing, start terminal service,
stopped wingate service, started wingate service, try again... working!
I did this action only once. Now all working! What it can be?

[Pascal]

Only difference should be in the detection of adapters when you stop/start the engine. However, WinGate has several methods of detecting those on the fly. One quick question then:

Could you see it listening on the correct port once the modem was connected?

[Surfer]

Yes, i see a correct port. netstat show it.
And note, when i haven't ability to use www service, i can't use ftp, socks or other services as well.
After start/stop in connected state, name of the adapter or his useage not changed but all working. Interesting.
Modem is an internal genius winmodem.