WinGate Forums

by **kalvos** » Aug 09 04 6:50 pm

Hi,

I upgraded to WinGate 6. Licenses went fine, and everything looks normal. I have used WGIC and continue to do so.

Here are the symptoms.

1. I can ping any machine from any other.
2. I can use the server successfully (I am writing this message from it).
3. I can resolve DNS from client machines.
4. The client computer name and running application name appears in the activity panel.

However, nothing else works. There is no browsing, no email function, no time server function, no NNTP, etc.

The client applications make the connection, but it then stop. For example, when using Eudora, it will make the connection and present the "Logging on..." notice. There it sits. The app shows in the activity panel, but none of the connections I'm used to seeing are below it.

Browsing with Opera will get to the site, but then say it wants to download an octet-stream document of 0 bytes. IE just gives the old "page cannot be displayed" message. Likewise, the app only shows up in the activity panel.

Trying to reach a time server or quote server with Netlab gets to the server, but stops there. However, running DNS from Netlab on a client does resolve, and it shows up in WinGate's activity panel.

I have tried WinGate's WWW proxy on and off (I had kept it off before). I have tried the WGOptions for Realtek, just in case (I have one on the client, not the server. ENS is enabled, but the firewall is not blocking the clients. I have reset the WGICs. I have rebooted, released/renewed, and just about everything else I can think of.

The only unusual item is that WinGate's network status indicates the internal NIC status as "unknown", even though it is otherwise detected and reported correctly and the addresses are correct.

The client-to-server setup seems just great. In fact, I am running the server's browser right now in a window on a VNC client, so TCP/IP is just fine from client to server.

What's left to check?

Thanks,
Dennis

by **adrien** » Aug 09 04 10:04 pm

Hi

first thing to check is that the interfaces in WinGate have the correct usage.

If for instance your internal adapter has a default gateway, it will be deemed external, and will firewall your LAN from WinGate.

Second thing to check are the bindings in the services. In some cases we weren't able to migrate settings, so we post a warning in the installer if you are upgrading.

Adrien

by **kalvos** » Aug 10 04 1:03 am

adrien wrote:first thing to check is that the interfaces in WinGate have the correct usage.

If for instance your internal adapter has a default gateway, it will be deemed external, and will firewall your LAN from WinGate.

Second thing to check are the bindings in the services. In some cases we weren't able to migrate settings, so we post a warning in the installer if you are upgrading.

I'm just guessing with what goes with what. I have had the proxy servers (FTP, POP3, Telnet, WWW) turned off, and still do. I don't know what the others do, so left them alone. What bindings should I actually use and what should they be? I'm not a network person, and set this up several versions ago and have long since forgotten how it works, just how it "looks". Now that you've changed the "look" of the bindings, they are meaningless to me again!

What does "internal adapter has a default gateway" mean? Where do I look for this? The firewall is showing nothing, except occasional hits from the outside world.

The only thing I've found since I posted my first message is that the Network Panel shows only the server, and not the other computers.

As I said, the computers are talking, because I'm typing this in a window on a client computer using the browser on the server using VNC.

Dennis

by **adrien** » Aug 10 04 1:08 am

OK.

Basically the place to look first is in the Network tab in GateKeeper, at the bottom under Network Connections. In there you should see all your network adapters. The key piece of information here is the "usage" column. That shows whether WinGate thinks your adapters are internal or external. If this is wrong, double-click on an adapter, and choose the setting you want.

then for bindings, the normal policy is to bind services to internal adapters. If you changed your adapter usage above, you should find the bindings pop up.

Otherwise, in order for a service to be available to your network, it must be bound to the adapter that is connected to your network (or any adapter - special case).

Adrien

by **kalvos** » Aug 10 04 1:35 am

adrien wrote:Basically the place to look first is in the Network tab in GateKeeper, at the bottom under Network Connections. In there you should see all your network adapters. The key piece of information here is the "usage" column. That shows whether WinGate thinks your adapters are internal or external. If this is wrong

These are correct -- the internal and external adapters are shown that way under auto-detect. The only anomaly is that for the internal adapter, the status line is "unknown".

then for bindings, the normal policy is to bind services to internal adapters.

That is the case -- to "any internal adapter". And except for DHCP, they're all also bound to loopback/127.0.0.1

Dennis

by **kalvos** » Aug 10 04 2:29 am

More information that might help.

I have just made the WGIC monitor visible on the client.

When running from the client, usual applications (Eudora, Opera, IE, Netscape, etc.) show bytes sent, but none received.

Netlab shows bytes sent and received when doing time server connection, quote server connection, Whois, etc., but gets "connection refused" from those servers (those services worked under WinGate 5). DNS lookup with Netlab is successful. (Ping and trace report no information, as expected, except to machines on the local network.)

I mentioned that I'm using VNC. This connects from client to server and bytes galore are being transferred as I type and refresh the client screen.

(On the server, the local network is visible and accessible -- but WinGate shows only the server in the network panel, not any of the clients.)

Dennis

by **kalvos** » Aug 10 04 2:52 am

Yet more information. Here is the WRP log for a mail check:

08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Created:
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Debug: Request 303 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1347 to 209.197.105.52:110
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Debug: Request 303 Creating new socket 2152
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Debug: Request 303 starting async connect
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Debug: Request 303 connect completion 209.197.105.52:110
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Debug: Request 303 Connect completion stage 2 - LSP has connected to us
08/09/04 09:45:59 192.168.244.135 Guest 0000000016 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:46:01 192.168.244.135 Guest 0000000016 Debug: Request 304 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:46:02 192.168.244.135 Guest 0000000016 Traffic 80 97 0 0 3s
08/09/04 09:46:02 192.168.244.135 Guest 0000000016 Terminated exit code 0

Here is the log for checking 3 websites on browser launch:
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 305 WRP_COMMAND_BIND UDP 192.168.244.135:0 to 0.0.0.0:0
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 305 Created Socket 2152
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Setting new client socket port to 1158
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 305 bound to 0.0.0.0:1158
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 305 UDP Relay 192.168.244.129:1159 created socket #2156
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 305 sending response packet
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 306 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1352 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 306 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 306 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1354 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 Creating new socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Receiving 40 bytes on UDP Relay socket #2156 from 192.168.244.135:1158
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Sending 30 bytes to 216.204.165.70:53 using socket #2152
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Receiving 103 bytes on UDP socket 2152 from 216.204.165.70:53 - sending to 192.168.244.135:1158 using UDP socket 2156
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 306 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 308 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 309 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1355 to 209.68.33.147:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 309 Creating new socket 2152
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 309 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 306 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 310 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1356 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 312 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 313 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1357 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 313 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 313 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 313 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 314 WRP_COMMAND_CLOSESOCKET Socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 315 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1358 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 315 Creating new socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 315 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 316 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 317 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1359 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 317 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 317 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 315 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 318 WRP_COMMAND_CLOSESOCKET Socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 319 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1360 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 319 Creating new socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 319 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 317 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 320 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 321 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1361 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 321 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 321 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 319 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 322 WRP_COMMAND_CLOSESOCKET Socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 323 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1362 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 323 Creating new socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 323 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 321 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 324 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 323 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 307 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 325 WRP_COMMAND_CLOSESOCKET Socket 2168
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 326 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1363 to 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 326 Creating new socket 2160
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 326 starting async connect
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 326 connect completion 209.197.105.52:80
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 311 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:55 192.168.244.135 Guest 0000000017 Debug: Request 327 WRP_COMMAND_CLOSESOCKET Socket 2160
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 connect completion 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 328 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 329 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1364 to 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 329 Creating new socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 329 starting async connect
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 329 connect completion 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 330 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 331 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1365 to 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 331 Creating new socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 331 starting async connect
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 331 connect completion 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 332 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 333 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1366 to 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 333 Creating new socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 333 starting async connect
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 333 connect completion 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 334 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 335 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.244.135:1367 to 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 335 Creating new socket 2152
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 335 starting async connect
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 335 connect completion 209.68.33.147:80
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 309 Connect completion stage 2 - LSP has connected to us
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Error: Caught unknown exception in CWRPSession::OnAccept() - ignoring
08/09/04 09:50:58 192.168.244.135 Guest 0000000017 Debug: Request 336 WRP_COMMAND_CLOSESOCKET Socket 2152
08/09/04 09:51:05 192.168.244.135 Guest 0000000017 Traffic 793 677 0 0 10s
08/09/04 09:51:05 192.168.244.135 Guest 0000000017 Terminated exit code 0

by **adrien** » Aug 10 04 4:24 am

Hi

Thanks for that.

Tracked down a bug in the code. I take it you aren't using a trial activation, and also you are running on NT4?

Does this problem go away if you activate a trial? I found some code in there that sets up a necessary variable for WGIC to connect, but only if centralised WRP configuration is available, and that is only available on Enterprise licenses.

We are putting out a maintenance release soon which will fix this, but in the mean time, the Trial activation gives you an Enterprise license.

Adrien

by **kalvos** » Aug 10 04 4:40 am

adrien wrote:Tracked down a bug in the code. I take it you aren't using a trial activation, and also you are running on NT4?

Win98SE. 5-user Pro license upgradable, activated last night.

Does this problem go away if you activate a trial?

By golly you've got it! I'm now typing this on my client browser running via Wingate.

Now pretty please, the patch before the trial expires! :)

Dennis

by **adrien** » Aug 10 04 5:04 am

heh, well We were going to put it out later today, but I wouldn't want you to miss out on the opportunity of getting used to those other Enterprise features :)

by **kalvos** » Aug 11 04 5:50 pm

adrien wrote:heh, well We were going to put it out later today, but I wouldn't want you to miss out on the opportunity of getting used to those other Enterprise features :)

Never enough time for that! :)

Did the new build 993 fix the activation issue? Can I revert to my 'real' key now?

Dennis

by **Pascal** » Aug 11 04 6:38 pm

It wasn't an issue with activation - activating a trial gave you an Enterprise key - which was required for a certain code path to execute. We've since moved that code outside of the block for "Enterprise" only.

So your real license key should function 100% now with 993.

WinGate Forums

WinGate 6 Mostly Not Connecting

WinGate 6 Mostly Not Connecting

Who is online