Network computers can't connect via Wingate 5222

[fr.anthony]

We set up a new server and moved Win2KadvServ containing Wingate 5222 to it via a ghost image. We are using 2 NICs, one for the network and a second for the broadband connection.

We connect to the internet from the new server, and all machines on the network connect to the server. But no internet applications on newtork machines can connect to the internet.

Looking at the Gatekeeper at start-up, it gives a system message that it has bound to the IP on the broadband NIC. But it does not also say that it has bound to the LAN NIC, as I believe it always did before changing servers.

Maybe something got corrupted in the change-over? Is there someplace in Wingate where I can copy the configuration from the previous machine's files. BTW - moving the network cables back to the old server makes everything work again. So I'm guessing it has to be a configuration issue.

Thanks for any suggestions.

[labull]

Are the IP addresses on the NICs the same on both computers?

I'm guessing possibly the internal is not.

If that is the case you merely have to bind the internal address to the WinGate services you use.

Larry

[fr.anthony]

>[quote="labull"]>Are the IP addresses on the NICs the same on both computers?

No. The new computer has the same as the previous server, and the previous server is disconnected from the network.

>I'm guessing possibly the internal is not.

>If that is the case you merely have to bind the internal address to the WinGate services you use.

How to do it?

Also, I neglected to mention in my original post that the network machines cannot see the wingate server at all...if the Client is opened, it cannot find the server. I tried reinstalling the WGIC, but the installer could not see the server on the network either, and offered to set itself up as a server instead of a client.

Thanks for the input, though.

[Pascal]

Maybe something got corrupted in the change-over? Is there someplace in Wingate where I can copy the configuration from the previous machine's files. BTW - moving the network cables back to the old server makes everything work again. So I'm guessing it has to be a configuration issue.

First suggestion is to open the appropriate proxies and to check which Interfaces they are bound to. You should see a binding to your internal LAN nic (Normally).

For a quick copy of WinGate settings, you can export:

HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate

That contains the basic setup information for WinGate. (There are some additional keys for the driver, etc.)

How are your clients connecting to the WinGate Server ? Using WGIC ?

[fr.anthony]

[quote="Pascal[/quote]

First suggestion is to open the appropriate proxies and to check which Interfaces they are bound to. You should see a binding to your internal LAN nic (Normally).

For a quick copy of WinGate settings, you can export:

HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate

That contains the basic setup information for WinGate. (There are some additional keys for the driver, etc.)

How are your clients connecting to the WinGate Server ? Using WGIC ?[/quote]

The binding appears to be only to the external interface (the nic on the cable modem). That's the only one that shows up.

We've tried using NAT to connect (which we used before changing server machines), WGIC, and a combination of both. None work.

We've been using a hardware switch/router for the network for a little over a year...but never tried to use the built-in firewall and connect it directly to the broadband connection, since Wingate worked well and I don't believe in fixing what isn't broken! But this problem got me to go ahead and configure the switch/router and try connecting through it.

It works so well, I have no desire to go back to Wingate. But I'd still like to solve the problem because I don't like loose ends. And I might have a need to use Wingate again sometime.

[labje69]

We also have ghosted our machine. And unfortunately we have the same problem. The HTTP requests results in: socket error 10049.
Please can anyone help!!! We cannot change our machines till we have fixed this problem.

[labje69]

QBIK staff: please respond!!!

[Pascal]

We also have ghosted our machine. And unfortunately we have the same problem. The HTTP requests results in: socket error 10049.
Please can anyone help!!! We cannot change our machines till we have fixed this problem.

Socket error 10049 means "The requested address is not valid in its context. ".

Have you (a) checked that your Internet Connections are set up properly, with the correct IP addresses, etc. and (b) that your bindings and interfaces in WinGate are correct ?

How are you connecting the clients, via NAT, WGIC or proxies directly ?

[labje69]

Hello Pascal,

a. Yes, via direct contact, it works fine. We have only problems when we connect via the proxy. Or is there a configuration sheet where the IP adresses of my ISP have to be filled in?
b. No errors are reported in the wingate screen. So I think the bindings are oke, how can I check this?

We are connecting via proxies directly.

[Pascal]

a. Yes, via direct contact, it works fine. We have only problems when we connect via the proxy. Or is there a configuration sheet where the IP adresses of my ISP have to be filled in?
b. No errors are reported in the wingate screen. So I think the bindings are oke, how can I check this?

Open GateKeeper and navigate to the appropriate Service (WWW Proxy Service, in this case). Switch to the "Bindings" tab. That should be set to your internal network's adapter. Normally, WinGate will default to that config though, so it might be off base, but worth a check.

[labje69]

That setting is OK.
Do you have any other suggestions?

Kind regards,
Sandra

[erwin]

Hi there

By the sounds of things the second Network Card that connects to the rest of the LAN is not being bound in WinGate. This can be because:

There is no private IP address in the network properties of this card and so thats why WinGate doesnt bind it. This card should be configured with a Private address that is in the same range as what the rest of the network is using (such as 192.168.1.*)

It is also THIS address that clients should use as their Gateway and DNS entries in their network properties to access the WinGate server via NAT,WGIC. This address is also used/entered in the clients Internet application settings when it asks what is used for the proxy server address.

It is also usually the only IP address (apart from 127.0.0.1) that should be in the "bound window" on the bindings tab of the services (www,socks etc), in GateKeeper. Usually it is not wise to have the broadband IP (external) in the "bound window" on the BINDINGS tab on any of the Services as this will pose a security risk.

Regards
Erwin

[labje69]

We found the problem!!!
I checked the bindings earlier, and I didn't see any problems.
I had set the proxy open for outside as inside as well, I know, security risks, but I was desperate!
Later, after browsing using the bindingstab in the "connections will be accepted on" field, it worked suddenly.
Later you can choose the option you want. It has to be greyed. If not, it does not work. Tip: browse and then choose the option you want. Start and stop the service and it works. Amazingly!!!

Thanks everyone for the help!