upgrading from 5.2.2 to 5.2.3 stops all proxy activity

[webmistress32]

I have an installation of 5.2.2 that's been fine for about 6+ months. My network configuration is a little complex but it's been in existence for about six years with the same architecture; I understand it and it works. so please no suggestions about changing the config!! :-)

I am simply trying to understand why my architecture works perfectly with 5.2.2 but not at all with 5.2.3

Wingate proxy/firewall server = Windows 2000 with all up-to-date patches, SPs

internal LAN NIC = static IP on 172.16.xxx.xx subnet, connected to
internal hub 10/100 3Com OfficeConnect. All other internal LAN machines on 172.16.xxx.xx subnet DCHP assigned.

external LAN NIC = static IP on 64.81.xxx.xx subnet, ISP assigned connected to SDSL line through SpeedStream SDSL device

Wingate server, other services = WWW, port 80; SMTP, port 25; POP3, port 110; FTP, port 21;

Wingate proxy services for internal LAN = WWW, port 8080; FTP, port 8021; others, ports as neccessary

ENS settings, port security =
* connections from Internal LAN to Internet = default is allow
* connections from Internal LAN to Wingate server = default is allow
* connections from Internet to Wingate server = default is deny
But allow port 80, 25, 110, 21


using 5.2.2 this works flawlessly. from the internal LAN I can connect to the Wingate server using terminal services and do any maintenance needed. we can use our browsers set to the proxy server address to surf and do anything needed.

however as soon as I upgrade to 5.2.3 (have tried twice now, once as an upgrade, once as a fresh install) all internal LAN to Wingate server connections stop working. I cannot use terminal services, cannot use brownser. when I watch the server activity in the Wingate GUI I see that the Wingate server is blocking the internal connections as blocked firewall ports. I have even trying specifically setting those ports to allow and they are still blocked.

I am unable to upgrade due to this issue. thanks in advance.

Laura

[MattP]

Hi Laura,

Can you please check your network interfaces, under the options>advanced menu and check that your internal interface is set to private and trusted.

Can you ping the server by name and IP address from the clients when you're on the client?

You can try to recreate the Extended Networking driver by editing the registry, if you find the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Components\WinGate Network Driver
and delete it (this will reset any settings you have in the Extended Networking menu) and it will be recreated when you restart the engine.

Please let us know how you get on,

Matt

[webmistress32]

do I verify/change these items now before I upgrade to 5.2.3 or upgrade and then verify/change them?

the problem is that once I upgrade and it doesn't work, I have to uninstall and then reinstall from scratch and it's time consuming to recreate all of my configurations.

maybe I could back up the registry key and restore it after I downgrade?

Laura

[MattP]

You should try those things after you upgrade to make sure all your settings are correct.

To save your settings you just export your registry file, all the usual warnings apply before editing your registry:
open your registry editor
fnd the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software
go to the registry menu and select export registry file
save it somewhere handy
if you need to import your registry just double click on the file and it will overwrite your registry settings.

Matt

[webmistress32]

okey doke. will try over the weekend. I have a demanding family - translates to the worst users on the planet! no downtime is acceptable, esp when the Cubs are playing :-)

will advise how it goes.

Laura