Moving Wingate Server to a New Machine

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

Moderator: Qbik Staff

Moving Wingate Server to a New Machine

Postby neujron » Sep 17 04 3:37 pm

Hello once again!

I have posted before, we will be moving our wingate server to a new server machine with Windows 2000 Server OS. This is in response to your suggestion that it's recommended that we use 2 NIC for external and internal IPs. Currently, we have 1 NIC and both external and internal IPs are configured on same card.

My concern is, how do we move the installation of the Wingate server to the new machine? Here are some big issues (sorry no time to search for KB's regarding this):

1. We'll be using same IP's external/internal like the IPs in the old machine. How am I going to install wingate? Do I need to shutdown the old machine 1st? But in that case how can I connect to internet and do some updates? Or can we install with different IPs 1st then change it later to the IPs we currently use in the old machine?

2. Do I need to install the old version (4) 1st then update later or can I just install the newer version (6) and put the old version license key to it? This is regarding license issue, we have old version license key only.

3. How about our current setup, can I copy 1st the wingate folder to the new machine and install Wingate over that folder? Will it restore or copy the current configuration or will it overwrite?

4. Newbie question (never done before), do I need to physically connect also the 2nd NIC with UTP cable or no need for that?

5. I have read sticky note of Adrien, regarding adapter issue. Are we going to modify the 2 adapter config to what it will be used for like 1 NIC for external and the other 1 as external?

For now, these are the issues that currently we have. Can you guide us on what to do best? We greatly appreciate any help you can give us. Thanks.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby Pascal » Sep 17 04 3:53 pm

1. Install with different IPs, then renumber once you replace the old machine.

2. You can install 6.0 right off the bat, but you'll need to do that with a trial key. Before you disconnect your old machine, de-activate the 6.0 key there so you can activate it on your new machine.

3. Folder should not be necessary, but you can do the same for the registry. You need to be confident in editing / importing the registry though. All warnings about editing the registry applies to this.

(a) Export HKEY_LOCAL_MACHINE \ Software \ Qbik Software \ WinGate.
(b) This will create a registry import for you
(c) You should be able to import this on a different computer

Note though, if you're changing locations (E.g. old machine was C:\WinGate and new machine is D:\Program Files\Wingate) then this approach will cause problems.

4 + 5. Yes, definately. One NIC will become your external interface. This connects to the device you use to connect to the Internet. Your other NIC becomes the internal interface. They should be marked appropriately in WinGate.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby neujron » Sep 17 04 4:34 pm

Thanks Pascal for that quick reply.

So you mean to say in #2, I will install ver6 with trial key then if I'm going to make it live, I will deactivate the 6.0 key in the old and what key should I activate on the new? Do I have to copy the keys in the old and activate it on the new? How would it know that I have an old license key? Or does the "export registry" to new machine will take care of it? Is this the registry created on the GateKeeper's Advanced Options-->Save Registry Settings (WinGateConfig.reg)?

For safety reasons, I'll install the Wingate to the drive letter where it was currently intalled, same as it is.

#4 Noted, I will connect 2 UTP cables to the 2 NIC cards, 1 each.

#5 Noted, I have to mark the NIC cards external or internal respectively.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby Pascal » Sep 17 04 4:40 pm

When you install the new system:

1. Activate a trial
2. Set it up
3. Test it

Once you're done with all the testing, etc. and you are ready to move the IPs do the following:

1. Deactivate your version 6 license on the old system.
2. Disconnect it from the network (Or change it's IPs)
3. Add the IPs to your new system and connect it to the network / internet
4. Activate the old (Version 4.x) license key you have.
5. Deactivate the trial license

You should still have the license details with which you purchased it. You can simply enter those into the activation client software and it will submit that information for you. This HAS to be the purchased key you have (I.e. your version 4 license key).

If you do not have that key, you can get in touch with Matt, our support lead and general key guru through the support channels (http://support.qbik.com) . He'll ask you all the right questions to validate identity, etc. before giving you the information.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby neujron » Sep 17 04 4:53 pm

Okay that sounds easier and very helpful, I'll keep in touch whatever maybe the outcome or if there are any issues I'll get bumped on the way.

We still have our license details with us.

Thanks for your help. :)
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby dizonj9 » Sep 18 04 9:41 pm

I have reinstalled new WinGate 5.0.0 to a new machine with newly configured Windows 98 which is set up as the server in my Internet Cafe. After I have successfully installed the WinGate, at first only few users were able to connect to the internet but later on when I used proxy server in workstation LAN settings, all computers are now able to connect to the internet, but there is one big problem --

1. When users are in Yahoo Messenger, they cannot be connected when the connection is set to No Proxies, but once I change the connection of the Y Messenger to Firewall with no proxies, connection will be estavlished.
Previously sellecting No Proxies was ok.

2. When users are online in Y Messenger, they cannot view their webcams as well as the webcams of other chatters, with the following error message:

"Sorry, you appear to be behind a firewall and are currently unable to use Yahoo!Webcam service"

Last time we did not encounter this problem before. How can I check if the firewall is blocking the Yahoo webcam service?

Appreciate your appreciate response on this. Thanks a lot.
simple lad
dizonj9
 
Posts: 4
Joined: Sep 18 04 9:23 pm
Location: Philippines

Postby neujron » Sep 19 04 8:04 am

Hi Pascal,

As promised, I'll get back to you whenever there's a problem on our installation.

I have installed already Wingate to our new machine for testing. After the installation, I noticed the red exclamation point in the DNS Service with default port 53. In the System Messages tab there's a message "Service startup complete or partial failure - Check your bindings"

When I checked on the Bindings of DNS Service, the status was "error" for the loopback and for the adapater instead of "started". What could be the reason for this?

And as discussed on this post, we installed with different IP but we cannot connect to the internet so I used our IP in the old server and disconnect it also in the network. I think maybe because the test IP was not configured in our ISP provider site. We are connected in the internet but the DNS Service problem is still there, the status is the same "error". Is it because the O.S. (Win 2000 Server) is different from the old server (Win NT4)? What should be the setup for DNS?

Please advice, thank you.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby neujron » Sep 20 04 3:14 pm

Hello Support,

We beg for your help please.... :(

What maybe the cause why the DNS service cannot bind to our 2 NIC adapters? The status is "ERROR" instead of "STARTED". This is a new install on a new machine on a Windows 2000 Server with 2 NICs.

Thanks.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby kgoodknecht » Sep 20 04 4:03 pm

neujron wrote:Hi Pascal,

As promised, I'll get back to you whenever there's a problem on our installation.

I have installed already Wingate to our new machine for testing. After the installation, I noticed the red exclamation point in the DNS Service with default port 53. In the System Messages tab there's a message "Service startup complete or partial failure - Check your bindings"

When I checked on the Bindings of DNS Service, the status was "error" for the loopback and for the adapater instead of "started". What could be the reason for this?

And as discussed on this post, we installed with different IP but we cannot connect to the internet so I used our IP in the old server and disconnect it also in the network. I think maybe because the test IP was not configured in our ISP provider site. We are connected in the internet but the DNS Service problem is still there, the status is the same "error". Is it because the O.S. (Win 2000 Server) is different from the old server (Win NT4)? What should be the setup for DNS?

Please advice, thank you.


If the new Windows 2000 server is an Active Directory domain, disable the Wingate DNS service. You are required to use the Windows 2000 DNS (or compatable BIND DNS) on all Active Directory Domain members and DCs only in TCP/IP properties.
Best regards,

Kevin Goodknecht [Microsoft MVP]
See me in the Microsoft Public DNS newsgroups
kgoodknecht
Senior Member
 
Posts: 161
Joined: Nov 24 03 1:31 pm
Location: Wichita Falls, TX

Postby neujron » Sep 20 04 5:01 pm

Thanks Kevin for your reply.

So, I have to disable DNS on Wingate but I just want to know if there'll be no effect or any problem I'll get into when we deploy it already for production?
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby neujron » Sep 20 04 5:32 pm

Ohh I forgot, in my installation, I haven't configured anything for Active Directory because we're not going to use this. I think this is not the default while installing Windows 2000 Server right or it was installed silently? If ever, how do I disable AD?
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby HenriLemmers » Sep 20 04 9:08 pm

Hi,

Even without AD, windows 2000 server kan have DHCP and DNS installed. I think in the whitepapers they do describe how to setup DNS and DHCP with Active Directory. I would propose disabling the Windows DNS and DHCP in your situation where you are not using AD. Use the wingate DHCP and DNS, and it should be working as you are used to.
BTW, I am using AD now and it seems to work allright.

Good luck,
Henri
Henri Lemmers
HenriLemmers
 
Posts: 26
Joined: Jun 08 04 9:32 pm
Location: Netherlands

Postby neujron » Sep 20 04 9:32 pm

Thanks for your help guys, I do appreciate it.

But we're not using DHCP, the DNS settings are on our NICs on Internet Protocol (TCP/IP) for our internet connection setup. We will be using these IP's also for our e-mail server DNS settings.

Right now, I can connect on the Internet using the newly installed Wingate and I have tested also some TCP mappings and it's okay. I just want to confirm or verify if there'll be any impact/effect while on production if the DNS Service has an error on the bindings. For now, as I've said, the internet connection is fine and I think other Mapping also and I don't have any idea if DNS service will cause us a problem in the future.

Thanks a lot.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm

Postby kgoodknecht » Sep 21 04 2:04 am

neujron wrote:Ohh I forgot, in my installation, I haven't configured anything for Active Directory because we're not going to use this. I think this is not the default while installing Windows 2000 Server right or it was installed silently? If ever, how do I disable AD?


If you haven't ran DCPROMO then you have not installed AD. But if your getting a red X on the DNS service in Wingate then you have probably installed DNS. If your not going to use AD you can disable Win2k DNS, but if you install AD then you must use the Win2k DNS.
The advantage of using Win2k DNS is that it is a Full content DNS service that supports resolving its own zones. The Wingate DNS is a proxy DNS that must rely on other DNS servers for content.
Best regards,

Kevin Goodknecht [Microsoft MVP]
See me in the Microsoft Public DNS newsgroups
kgoodknecht
Senior Member
 
Posts: 161
Joined: Nov 24 03 1:31 pm
Location: Wichita Falls, TX

Postby neujron » Sep 21 04 7:50 pm

Thank you for that information. I'll keep that in my notes for future reference. For now, I'll just disable Wingate DNS and we'll just wait and see for the result when we're going to install already our e-mail server.

Hope Qbik will further enlighten us on this one, whatever best practices they have.

Best regards.
neujron
 
Posts: 76
Joined: Jul 27 04 4:19 pm


Return to WinGate

Who is online

Users browsing this forum: No registered users and 4 guests

cron