Which is best MS OS for new WinGate install?

[craigside]

Hi

I have been using WinGate 5.2.3 for about 5 years with no problems on Win2K, with Norton AV running alongside and I now need to update my hardware. In my experience I have found it better to have a dedicated PC to run WinGate seperate from other servers etc., on the LAN side, i.e. if 1 mission critical machine goes down it is easier to fix.

I have tried installing Ver 5.2.3 onto my new machine - and I realise it won't install on XP Pro SP2 or SP3, however 5.2.3 WILL install on Win2K3. I also find that the newer version of WinGate (6.6.4) WILL install on XP Pro.

So, my situation is;

1. I need to be running on XP Pro, or Win2K3 to make take full advantage of my new machine's quad core processing.

2. I want AV software at the 'front end' and Nav2010 won't run on Win2K3 (I am told that AV is more costly for MS server platforms).

So, I think I should be running on WinGate 6.6.4 with the Kaperski AV plug-in.

My question is, keeping in mind that my PC is dedicated as a firewall/proxy server (i.e. just stands in the corner untouched and runs 24/7) which OS should I go with; XP Pro SP3 or Win 2003 Server?

I am inclined towards Win2K3 as it might have better resource management, but I don't know for sure.

Any advice is much appreciated!

Thanks

[logan]

The only difference between XP and 2K3 that effects WinGate in a noticeable way is the concurrent half-open outbound TCP connection limit enforced in XP (as of SP2). After 10 half-open connections, further connection attempts are put into a queue and forced to wait. In network intensive applications such as WinGate this can slow things down, and the more users you have on your network, the slower it will get.

However, this can be resolved by simply patching your TCPIP.sys to allow a much higher number of half-open outbound connections.
I also recommend disabling the Windows Firewall (it blocks network traffic and is outside WinGate's control), and the Application Layer Gateway service (prevents WinGate's gateway selection from working) when you use XP.

So XP is just as good as 2K3 if you address the issues mentioned above.

[Alen]

There is one more discovered difference: when using XP you have to login to OS for Wingate proxy server to start working (NAT is working also without necessity to log into the OS).

[logan]

There is one more discovered difference: when using XP you have to login to OS for Wingate proxy server to start working (NAT is working also without necessity to log into the OS).

WinGate runs as a service in the background, so you shouldn't need to be logged in. What's happening that makes you think it's not started? Maybe there's a different cause for the problem.

[Alen]

WinGate runs as a service in the background, so you shouldn't need to be logged in. What's happening that makes you think it's not started? Maybe there's a different cause for the problem.

I mentioned this behaviour in another thread and was told by another user that this is normal if you use non-server version of OS (XP in our case). As I was not alone I took this as a fact.

P.S. Once again, NAT connections are working fine, only proxy ones need OS administrator to make login. As soon as admin loged in, proxy connections started to work.

[Alen]

Just checked again, now everything is working without the necessity to login!? Don't know what to say...

P.S. I update Wingate OS once every 3 month, may be after an update the behaviour changed...

[logan]

That is particularly odd. I've never had to log in to the OS for WinGate to work, and the fact that NAT was working means that WinGate was running in the background. Maybe there was a firewall on the machine that blocked network traffic until a user logged into the machine as a security precaution. That's the only way I could explain it.

[Alen]

Maybe there was a firewall on the machine that blocked network traffic until a user logged into the machine as a security precaution.

No, only Wingate and only on Wingate server (and the issue with proxy was for all users, not only one).
I remember another user confirms and told us here, that the issue is because of non-server OS. Here is the topic:
viewtopic.php?f=12&t=40273&start=0&st=0&sk=t&sd=a

BTW, the main question of that topic is still unanswered.
Anyway, I decided to migrate to W2k3 SP2 Standard soon, I'll let you now if my old problems still remain in place.