Upgrade from W2K to Windows XP SP3
Apr 13 14 3:09 am
Operating System: Windows 2000
Wingate version: 6.6.4
KAV version: 3.04
Users: 12 users
Users connect from a PC through this program to the Internet.
Users don't log-in and all users are in the users tab, groups and assumed users and everything appears to work correctly.
Can connect to the Internet bypassing the Wingate server without any problems.
I am wanting to upgrade this PC which Wingate is running on, to a XP Pro SP3 PC. My questions are:
1) Will it work?
2) What do I have to do that is the easiest way to move across to the new PC. Can someone let me know the steps they would take that would be trouble free?
3) What do I have to do regarding licence transfers?
4) I've heard that XP has a connection limit?? Since we only have about 5 PC's max that will be connecting to the internet, is this going to be a problem?
5) Any other useful tips?
Many thanks
Wingate version: 6.6.4
KAV version: 3.04
Users: 12 users
Users connect from a PC through this program to the Internet.
Users don't log-in and all users are in the users tab, groups and assumed users and everything appears to work correctly.
Can connect to the Internet bypassing the Wingate server without any problems.
I am wanting to upgrade this PC which Wingate is running on, to a XP Pro SP3 PC. My questions are:
1) Will it work?
2) What do I have to do that is the easiest way to move across to the new PC. Can someone let me know the steps they would take that would be trouble free?
3) What do I have to do regarding licence transfers?
4) I've heard that XP has a connection limit?? Since we only have about 5 PC's max that will be connecting to the internet, is this going to be a problem?
5) Any other useful tips?
Many thanks
Re: Upgrade from W2K to Windows XP SP3
Apr 20 14 8:02 pm
Hi
yes, WinGate runs on XP no problem.
You can export and import the registry if you're keeping the same version of WinGate.
HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate
You should install WinGate on the target computer first, then copy over the registry.
Yes, XP has a connection limit of 10 in-progress connections. This can be a problem even for a single user. Windows Vista and later didn't have this limit, as MS decided it was a bad idea, but didn't back it back out of XP with a later patch unfortunately. You would probably be better off running on Windows 7.
To transfer licenses, what you will need to do is before you decommission the source WinGate, you will need to deactivate the license. YOu can do this inside WinGate. That will free up the license to be used on the target. In the meantime - to make sure everything is working first - just activate a trial on the new WinGate.
Regards
Adrien
yes, WinGate runs on XP no problem.
You can export and import the registry if you're keeping the same version of WinGate.
HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate
You should install WinGate on the target computer first, then copy over the registry.
Yes, XP has a connection limit of 10 in-progress connections. This can be a problem even for a single user. Windows Vista and later didn't have this limit, as MS decided it was a bad idea, but didn't back it back out of XP with a later patch unfortunately. You would probably be better off running on Windows 7.
To transfer licenses, what you will need to do is before you decommission the source WinGate, you will need to deactivate the license. YOu can do this inside WinGate. That will free up the license to be used on the target. In the meantime - to make sure everything is working first - just activate a trial on the new WinGate.
Regards
Adrien
Re: Upgrade from W2K to Windows XP SP3
Apr 21 14 4:35 am
Many thanks for the reply. Regarding "Yes, XP has a connection limit of 10 in-progress connections" can you just confirm what in progress connections means? I've attached an image (taken from the help manual) showing a typical GateKeeper activity icons.
In the example attached does the user called WITCH mean 1 connection or does that mean WITCH has 8 connections.
Does this mean then user 192.168.6.33 under it is the second connection and is using 4 connections?
Just want to make sure before the switch is made, say there is a computer called WITCH, 9 other pc's can connect and use the internet but its what's under the user isn't the session connection made, it's just showing what is been downloaded from the website to the PC?
Hope this makes sense?
In the example attached does the user called WITCH mean 1 connection or does that mean WITCH has 8 connections.
Does this mean then user 192.168.6.33 under it is the second connection and is using 4 connections?
Just want to make sure before the switch is made, say there is a computer called WITCH, 9 other pc's can connect and use the internet but its what's under the user isn't the session connection made, it's just showing what is been downloaded from the website to the PC?
Hope this makes sense?
- Attachments
-
- Attachment showing sessions.
- wg.jpg (66.53 KiB) Viewed 3169 times
Re: Upgrade from W2K to Windows XP SP3
Apr 22 14 12:33 pm
Hi
in-progress means in the process of being set up. TCP connections go through a 3-way "handshake". After the connection is set up, it doesn't count to the 10 connection limit.
Also WinGate NAT connections are not subject to this limitation, since the connection doesn't go through the windows protocol stack.
You can see if the limit is being hit in the windows event viewer (system log), TCPIP logs a warning about connection limit being exceeded. At this stage, it prevents new connections from being made.
In terms of your picture, yes 192.168.6.33 is using 4 connections, but since these are NAT connections, they don't count towards the limit
In terms of that computer WITCH, the connection limit isn't related to number of client computers, it's related to number of TCP connections, so even 1 client can max out the limit.
Regards
Adrien
in-progress means in the process of being set up. TCP connections go through a 3-way "handshake". After the connection is set up, it doesn't count to the 10 connection limit.
Also WinGate NAT connections are not subject to this limitation, since the connection doesn't go through the windows protocol stack.
You can see if the limit is being hit in the windows event viewer (system log), TCPIP logs a warning about connection limit being exceeded. At this stage, it prevents new connections from being made.
In terms of your picture, yes 192.168.6.33 is using 4 connections, but since these are NAT connections, they don't count towards the limit
In terms of that computer WITCH, the connection limit isn't related to number of client computers, it's related to number of TCP connections, so even 1 client can max out the limit.
Regards
Adrien