Can't access internet from either client/server

[bench]

I would like to know if I am setting up wingate server/client properly. I can't connect to the internet from either the server or client laptop.

Here's what I did:

* Installed wingate 6 trial on a PC running w2k server
* Configured my two network cards with the following address
* 65.183.219.244, 255.255.255.248, 65.183.219.241 for the wan
and the dns 65.183.217.253
* 192.168.2.2, 255.255.255.0, 192.168.2.2 for the lan

* I open gatekeeper and I see that it detects the lan IP.
* I installed wingate client on a laptop for testing purposes
and it automatically detects the wingate server. I have the
ethernet card on the lptop to get an IP automatically.
* In gatekeeper under system services I go to dns/winresolver
and enter the dns servers.
* I am able to access the internet from both the server and client
but about two minutes then it stops. I can't get access from either
one.

I would appreciate some suggestions on how to make sure the
server is not trying to use the lan to connect to the internet.
One other thing, the cable that connects to the lan comes from a switch
which is connected to a router who is connected to a firewall.

Can the server be behind a firewall?

I would appreciate any tips or pointers.

thanks.

[Pascal]

192.168.2.2, 255.255.255.0, 192.168.2.2 for the lan

Is the second 192.168.2.2 a default gateway for the LAN card? If so - take that off.

[bench]

Thanks for the advice, indeed changing the gateway for the lan to the gateway of the wan worked just fine.

Now I am focusing on the user policies and finding out how to restrict access to certain websites.

The thing is that sometimes the internet connection is still lost from the PC that has wingate server. I can't connect to the internet so obviously neither can the client PC's.

I don't understand why it loses connection. It was working fine for over 5 hours then it just stopped.

I have not changed anything except the policies and that's only for users. Any idea why it's dropping the connection?

I checked the switch box and the line is hot and read just like the other lines connected to other PC's not connected to wingate. I tried adding the DNS server to wingate so it would look there first but still the same.

[bench]

I rebooted the PC and it connects fine now but it was freezing up right before I rebooted. Don't know if that affects the internet connection since I couldn't even ping the dsn servers.

Also, I have the client pc to enter their username and password but when I open IE in the client, it doesn't ask me for it right away until I close it and re-open it again. I also see that in gatekeeper it lists the client as guest the first time then as the actual user after I enter the username and pass.

Why doesn't gatekeeper see the client as the user instead of guest the first time it tries to connect?

[Pascal]

Thanks for the advice, indeed changing the gateway for the lan to the gateway of the wan worked just fine.

You don't need the gateway there. In most cases, that will actually break things. You normally only need a gateway for your external adapter.

[Pascal]

Policies are sometimes a bit tricky. You've gone through the post that details how to set it up...

What method did you choose to use to authenticate the client? Remember, WinGate will count it as a connection from a machine. As long as one session remains active, the machine will remain authenticated.

All connections will be treated as "guest" (Unknown) until they have either authenticated or been assumed.

[bench]

I removed the gateway from the lan as you suggested and it was connecting, however, I stepped out of the office for about two hours, came back and it was not connecting anymore.

Do you think it's a setting in wingate that disconnects the server from the internet or is it a hardware problem?

I am understanding the policy procedures better and it seems to work well so far, the main problem is getting the server to stay connected.

I will be looking into the e-mail server later on.

You had mentioned that there's a manul in the making waiting for approval, any chance you can let me have a copy?

I also found a manual for wingate 4 on the net from a canadian distributer, does much of the info there apply to the new one?

Thanks

[Pascal]

It's difficult to determine what is preventing you from connecting. WinGate does nothing that 'prevents' you from connecting at any stage - but it could be a set of circumstances. Normally, it is observed behavior - rather than actually being disconnected.

When you get into that stage, what cures it for you? (Stop/start of WinGate; Reboot, etc.)

What activity is still possible? I believe you cannot ping - but I assume you are pinging by name? Can you still access sites directly by IP - for example, try pinging 210.55.214.101; which is www.qbik.com.

Then, what activity is shown in GateKeeper at that time?

Then, which machines are getting their IPs via DHCP and from where?

How do you connect out to the internet? (What type of hardware / device / etc.)

[bench]

Here's the scenario.

I have a cable coming out of the switch box to the server(wingate) WAN, then I have a cable coming out of the 2nd card(LAN) to the uplink in a router. I have the test client PC connected to one of the ports in the router. Someone mentioned to me to use a crossover cable from the switch box to the server but I have not done so yet.

The switch box is hooked up to a 16 port router who in turn is connected to a watch guard firewall. We are testing wingate before implementing it.

Usually rebooting the server pc solves the problem for awhile. Sometimes the connection will stay on for hours sometimes for a couple of minutes. I know the client won't connect because the server has lost the connection so the problem lies in the server with wingate on it. Something it's causing it to drop the connection. I can't ping to the dns servers or other websites.

the client machine is getting the IP from the server. The server's wan and lan have fixed ip's. I typed the addresses for each in a previous post. I believe the problem is not in the client as it works fine when the server connects.

What is your comment as far as the manual for wingate 4, could that be useful? I think a manual is essential to the implementation of wingate.

[Pascal]

Version 4 manual might not be 'that' useful. Our documentation has had a fairly decent overhaul recently; there should be a WinGate.chm file in your installation folder.

Otherwise, you can get the latest version from:
http://www334.pair.com/qbiknz/downloads/WinGateHelp.chm