Trouble after upgrading to Wingate 5.2.2

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Trouble after upgrading to Wingate 5.2.2

Postby henryg » Feb 14 04 7:44 pm

Hi!

I've just upgraded from Wingate 4.3 to Wingate 5.2.2, and I have run into some unexpected difficulties.

First of all, I used to be able to see the network drives on the server from all client computers. This is not possible anymore.

So my first question (on the assumption that there is no silly question): I used to have Wingate 4.3 running on the server only, with nothing installed on the client computers. Has this changed? Do I have to have a wingate client installed on the client computers?

Next (the plot thickens), I have (the misfortune of having) a leased line, and so I have to manually set my IP addresses, and they are all on the same subnet. I used to be able to ping the server from the clients, but since I upgraded, I cannot do so anymore.

There are a few other things that are not-quite-normal, but I'd be grateful for any hint/clue/help/pearl-of-wisdom that could get me back up and runnning!

Thanks in advance,
Henry
henryg
 
Posts: 2
Joined: Feb 14 04 6:51 pm

Postby erwin » Feb 16 04 8:54 am

Hi Henry

Are you using NAT (Network address Translation) for your client access
You should not have to install the WGIC on any of your client machines if already using NAT or Proxy as WinGate 5.22 will handle all 3.

Second question, The leased line you talk about, does that provide an external interface for your internet connection?.

If this is so then it should not affect the clients ability to reach the server by ping (as you say all the client machines are on the same subnet, using the same internal IP address range.)

If the clients cannot ping the WinGate server and cannot use mapped drives then I would suggest you start by rechecking TCP/IP config on the server for the LAN before checking Internet access. How do the clients receive their IP details? via DHCP from the WinGate Server? or are they statically set. It sounds as though the TCP/IP config needs to be rechecked.

Check this and let us know how you get on

Regards
Erwin
erwin
Qbik Staff
 
Posts: 408
Joined: Sep 03 03 2:54 pm

Postby henryg » Feb 16 04 10:35 am

Thanks for your help, Erwin.

The reason I mentioned the leased line is that it forces all our IP addresses to be static. It took me the better part of the weekend to understand the finer points of Wingate and get my system configured and operational again, but it seems to be all good now! The main thing I did that helped was to open some ports in the firewall for my local machines to see each other...

Thanks again for your help!

Regards,
Henry
henryg
 
Posts: 2
Joined: Feb 14 04 6:51 pm


Return to WinGate

Who is online

Users browsing this forum: No registered users and 1 guest