Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

NO Internetconnection on WINNT4.0 Server

Sep 04 05 11:16 am

Hi,
i have a problem with Wingate 6 (current version) that drives me crazy ...
Wingate server is NT4.0 SP6, just one client (W2K SP4). Internetaccess is via dialup (AVM ISDN). Had Wingate 4 running on this server for a few years now (via proxy access) with no further problems. Just upgraded to Wingate 6 (wanting to use NAT), removed all proxy settings for the browser on server and client but internet access stopped working. Nameresolution is working fine, i can ping hosts by name on the internet without any problems. IE comes up, says "website found, connecting ..." and times out (page not found). Same with OE: can resolve the hostname but no access via pop.
This is what i tried so far:
- Upgrade of Wingate 4 to Wingate 6
- Complete uninstall and fresh install of Wingate 6
- Tried to use the proxies
- Tried to use WIC
- Left the firewall at it-s default values, put it on "medium", switched it off.
- Played with the advanced options (Recalculate TCP ... etc)

No success. The nat connection is shown in the activity pane, the firewall log only shows some blocked access from the outside on netbios borts (138, 445). There-s an option to keep Wingate-firewall running when wingate engine is shut down. If this option is UNchecked and i shut down wingate and fire up the connection manually IE works again on the server. If this option is checked and wingate is shut down IE shows the same problems: "website found ..." and times out. So it looks as if the firewall SHOULD have something to do with it ... Or maybe a low-level driver it loads.
Any ideas on this are really appreciated

Dirk

Re: NO Internetconnection on WINNT4.0 Server

Sep 04 05 3:57 pm

Hi Dirk

Try the area in point 2 mentioned by James on this page: http://forums.qbik.com/viewtopic.php?t=3934

2. Check that your network adapters were detected correctly by WinGate. The network card pointing towards the LAN should be marked as "Internal" and the network card / modem that is pointing towards the internet should be marked as "External". GateKeeper --> View menu --> Network.

Image

Report back how it goes!

Sep 05 05 1:22 am

Hi Nev,

i-m pretty sure i checked this one but i will double check today to be sure.

Thanks
Dirk

Sep 05 05 11:54 pm

Hi,

all interfaces are correctly identified as internal /external. Anything else i could look at?

Dirk

Sep 06 05 1:20 pm

You mentioned that gatekeeper reported NAT connections properly - was dialup connection active when you were trying to establish this connection?

Sep 06 05 5:47 pm

1. Are you running any security suites / firewalls? ZoneLarm, McAfee, Nortons, Windows etc?
2. What kind of network card do you have on the WinGate server? Realtek 8029?
3. Do you have a gateway set on your internal network card? (You shouldn't usually)

Sep 07 05 12:38 am

Hi,

thanks for stepping in guys.
@genie:
yes. at least i think so because NAT shows the ip-adresses of the servers i was trying to connect. like i said, dns is working properly .... But i-ll check that again of course!

@jamesc
1.
No, nothing else regarding firewalling is installed
2.
It-s an Realtek ISA 8109. Tried the "Realtek-Switch" under advanced options already, made no difference
3.
I-ll check that

Thanks again
Dirk

Sep 07 05 11:34 am

Hi,

okay, just got back from the client. There is no gateway defined on the network card and wingate is connected while trying to get the page in ie loaded.
Wingate connects properly, nslookup is working i can ping hosts on the i-net, even telnet to them on port 80 .... IE shows "Wesite found, waiting for reply " and times out.. Activity pane shows the connection to the ip-adress on the i-net ... That drives me (and the client ;-) ) crazy!
Anything else i can try?

Thanks

Dirk
Post a reply