Wingae 6.0.1 clients not connecting

[Booboo]

I have a problem that seems similar, but different, than some of the others in the forum.

Upgraded from 5.x to 6.0.1 and now none of the clients can browse the web. Except, I have an email server on a client machine that can connect out via POP3 and retreive mail. It can, however, not send mail via SMTP. When it connects out via POP3 I see the machines name in the Activity pane of Gatekeeper, otherwise there are no activity messages.

I've checked the network settings in GateKeeper and my two NICs on the Wingate machine are tagged correctly as internal and external; but both say "Status: Unknown". And, in Windows, both NICs have the same name, but in GateKeeper they have different names.

Only the external NIC has a default gateway set; to the local side IP of our DSL router. The clients have the gateway set to the Wingate machine's IP.

I am not using the WG client software on the clients.

There are no messages in the firewall pane.

I've looked through the logs and find no indication that the clients are attempting to connect.

The clients can ping each other and the Wingate machine. The clients can browse the only local webpage available (our copy machine). The Wingate machine can browse the internet.

Any ideas? Thanks.

[MattP]

Hi,

Would you be able to email me your route table and your WinGate config file? To export the route table open a DOS window and type route print >route.txt, this will create a file called route.txt in the directory you are currently in. To export your WinGate configuration file go to options>advanced and select save report. You can email them to me at mattp at qbik dot com.

What types of network cards are they? What kind of internet connection do you have? Do you have Extended Networking enabled in WinGate and do you have an advanced tab on the network adapter properties when you double click on them in GateKeeper?

Thanks,

Matt

[Booboo]

Thanks Matt, I sent the files.

The network cards are "NETGEAR FA311/FA312 PCI
Adapter". I have a DSL internet connection that does NAT. I do
have extended networking enabled and I get an Advanced
tab for the internal NIC, but not the external one.

The Wingate machine is running on Windows 98. The
others are a nice mix of Windows 98(1), ME(2) and XP
Home(3).

Also, I've discovered that if I setup IE with proxy settings pointing to the Wingate machine it works. Still can't get my email out though, and the proxy thing isn't really what I need.

Thanks for your help,
Cheers,
Brad

[MattP]

Hi Brad,

Your routing tables look fine so that combined with the fact that a proxy connection works makes me think it could be a DNS configuration problem.

Do your clients point at the internal NIC of the WinGate server for their DNS? When they make a NAT connection they need to look at the WinGate server, or a DNS server on your network.

Matt

[Booboo]

No joy. I had the DNS in the clients set to the IPs provided by our internet provider. Changing them to the IP of the Wingate machine had no effect.

Everything works great when I switch back to the previous Wingate (5.2.3), but then stops (except for the POP3 proxy) when I go to 6.0.1.

I have DHCP in Wingate turned off, and all the machines have assigned IPs.

[adrien]

Have you checked the adapter usage in WinGate?

Check on the Network pane in GateKeeper. If the adapter usage is not correct for your adapters (i.e. internal vs external etc), then double click the adapter and select the usage that best fits.

Adrien

[PMRCmedia]

I too am having a similar problem. I do the 6.01 install on my server/gateway machine, iinstall the client on other machines, and they will NOT connect. I go back to version 5 and everything works fine. I have done this several times and no luck. (6 user, Pro. license)
******************************************************
* !!!!!!!!! Found Problem !!!!!!! - DNS / WINS Resolver
*
* Install 6.0.1, In Gatekeeper, System tab click DNS/WINS
* Resolver, in Name Servers add your ISP's DNS server IP
* Then all clients started connecting to the internet!
* (NOTE: For some reason, the 6.0.1 install didn't pick up the
* IP iof my ISP .. maybe something about my config.?!
* anyway, hope this helps others having same trouble)
******************************************************
/ Don Lackey Don@PMRCmedia.com

[Booboo]

Adrian,
Thanks, but that is the first thing I checked based on discussion in other topics. The two NICs are automatically tagged corectly 192.168.0.1 as internal and the one connected to the DSL router as external. I've also tried tagging them manually to the same settings, but that made no difference.

Don,
Thanks, you're right, the IPs for DNS were not listed in the DNS pane. However, adding these did not fix the problem.

After putting these valuse in GateKeeper; if I have the DNS IP on the clients set to the IP of the Wingate machine then I can do a DNS lookup from the client (ping returns an external IP, but get's no response from the resolved IP address).

However, if I have the DNS IPs on the clients set to the external values provided by our ISP then DNS lookups fail. This is the configuration we has with the previous Wingate that worked fine.

But with both these configurations the basic problem remain, I can't browse the web or send out SMTP mail from the clients.

Thanks,
Brad

[Booboo]

Thanks Adrien, Matt and Don for your help. But, I'm wondering if you have any more thoughts. I still have the problems - when I upgrade Wingate my client machines have no access (except for POP3). I'm sailing along nicely with the older Wingate, but would like to stay up to date.

Thanks again,
Brad

[PMRCmedia]

Once again, I upgraded my old creaking old dial-up gateway machine from NT4 to W2Kpro ... all went well with the OS upgrade, then I reinstalled Wingate 6.0.1 and ... same problem as my previous post .. nothing would connect. After 2 hours of "tweaking" and rebooting ... finally I adjusted Wingate's DNS Service, Bindings and added "Any Adapter - Any IP Address" and wow - everything came up on the clients just like normal!
Seems like the new version does something different with the DNS part and bindings ... its NOT all automatic, at least with my set-up. -- Hope this helps.
/Don Lackey