Ext. networking / User services question

[George in Seattle]

I've successfully entered "TCP Mapping Services" for three server applications for external users and they work great. However If I delete these services and try to enter them directly into "Extended Networking/Port Security" they wont work no matter what --no way, no how :) I've tried many variations of all the options with absolutely no luck. All I get are messages such as "server not started" (which is not true) on the external client. I need to be able to enter some port ranges to complete my setup. I'm beginning to think something else besides Wingate is misconfigured.

All the machines on my LAN have hard coded fixed IPs if that makes any difference. At this point I am out of ideas. So my question is: what would cause "User Service entries" to work while Extended Networking entries fail? Anyone have any ideas what might be wrong? Thanks!

[genie]

You do not use services when ENS is in use - ENS will simply redirect your traffic through a NAT session.

[George in Seattle]

Turns out all my incoming Extended Networking entries were working fine all along. This according to my off-site users.

I cannot test my Wingate config by pointing my local client programs to my own internet address. Even if they are on the Wingate machine. I need to call a remote person to test, and it works for them.

Why would this be? It would be nice to be able to test a client and have it behave as an external user would see it. Thanks!

[jamesc]

I cannot test my Wingate config by pointing my local client programs to my own internet address. Even if they are on the Wingate machine. I need to call a remote person to test, and it works for them.

Why would this be? It would be nice to be able to test a client and have it behave as an external user would see it. Thanks!

Scenario:

Internet
|
|
<Public IP Address - Resolved to www.george.com>
Hardware router
<Private IP Address>
|
|
<Private IP Address e.g. 192.168.1.2>
WinGate Server
<Private IP Address e.g. 10.1.1.1>
|
|
LAN Client.


Speculation:

You are sitting on the WinGate Server, you point Internet Explorer's Proxy Settings to your 10.1.1.1 and then type in the address www.george.com?


Solution:

Wherever the WinGate Server gets it DNS Requests resolved, you most probably need to modify the HOSTS file - you may just need to do it on the WinGate Server.

e.g.
C:\WINDOWS\system32\drivers\etc\hosts

At the bottom of that file, enter:
10.1.1.1 www.george.com

Then save - make sure no file extension is put on that file.

Then open up a dos prompt and ping that address; does the 10.1.1.1 address return? Next try the web browser.

***If that does not work, then check which ip address this web server is listening on; the host file may need to resolve to the External side; i.e. 192.168.1.2.

[George in Seattle]

Thanks for the reply! Your senario is close but the actual senario is even simpler:

My public IP: 24.18.154.190 (NIC is on wingate machine)
Wingate machine: 10.0.0.1
Telnet server resides on private: 10.0.0.3 (behind Wingate)

A remote and external user points his telnet client to 24.18.154.190:23
And it works (he gets a logon prompt).

I am sitting at wingate machine and point a telnet client to: 24.18.154.190:23
I get no success:
Microsoft Telnet> open 24.18.154.190:23
Connecting To 24.18.154.190:23...Could not open connection to the host, on port 23: Connect failed

Still at Wingate machine, I point the telnet client to 10.0.0.3:23 and I get a logon prompt.

I expected that using 24.18.154.190:23 on the Wingate machine would totally bypass Wingate and allow me to "see" things as the outside world does (so I can run tests).

[jamesc]

Try a TCP Mapping while I investigate why:

1. Remove your redirection in ENS.
2. Navigate to the Services tab and then right click an existing proxy service and then click "New TCP Mapping".
3. Enter the Default Mapping address of 10.0.0.3 and the port.
4. Make sure the TCP Mapping is bound to an interface pointing towards the internet.
5. Test.