Installing Wingate on Small Business Server 2000......

[paul_edi]

We have finally dumped our NT4 server.

I have installed Wingate on a new server running SBS2000.

When the machine boots the Wingate icon reports "Wingate engine starting" but it never starts and is always "Yellow".

Is there anything specific I should choose when performing the install of Wingate??

The server is not running DHCP, it is running DNS and Exchange 2000, no ISA server either.

Thanks,

Paul.

[Pascal]

Hi Paul,

From the sound of it about the only thing that you could do during the install would be to check that you've not requested WinGate mail - as you're already using Exchange 2000 and wouldn't want the service conflicts.

Have you tried Larry's famous History database check? Sometimes if the WinGate Engine is not properly stopped before the system reboots the history database will become corrupted. You can test if this is the case by moving the History.dbf and History.cdx files from the WinGate folder to another, temporary folder.

Regards,

[jamesc]

Please let us know if you are still having this issue.

[paul_edi]

I have solved my initial problem with WinGate not starting....I re-installed the OS!!....there were some other strange things happening...no Control Panel..etc.

I re-installed WinGate, added the users, but I then noticed that they could access the Internet but no webpages were displayed....like a DNS problem.

The DNS service is working fine on the server.

The following are disabled in WinGate, DNS, DHCP and the email option.

I then followed the "Considerations for Active Directory Domains" given in the "System Requirements for WinGate"

I added the IP address into WinGate Advanced Options as in Step 3

I added the IP address to the servers DNS Forwarders section (I couldn't understand why this would be necessary as WinGate resides ON the same machine as the DNS service).......now when I try to log on to GateKeeper i get an error....

"Connection with Wingate server terminated" (iirc)


Please help!!!!!!


Thanks.

[MattP]

Hi Paul,

When WinGate is installed on the domain controller you don't need to set the forward zone and you don't need to enter the IP address in the WinGate advanced options, but you DO need to stop the WinGate DNS and DHCP services.

"Connection with the WinGate server terminated" indicates that there is a policy denying you access to the server. There are a few ways to do this, if you remove the Everyone group from System policies and haven't made sure that the administrator is allowed access then you'll lock yourself out. Not having permission in the Remote Control service will also do it. You can have a look through your registry file if you know what you're looking for, or you can email us your registry file and we'll have a look for you.

Alternatively, you can download this registry file which grants the administrator rights to the Remote Control Service and ignores the default (system) rights. It will over-write a similar policy in the Remote Control service, but it should allow you to get back into GateKeeper and find the problem. Please note that this registry file was created in an XP system, so if you're running an earlier OS you'll need to copy the contents of the file to a registry file generated from your OS.

[paul_edi]

Hi,

Thanks for the reply. I have no problem editing the registry, could you advise what I need to check for/change??

I haven't yet investigated but I assume I should be looking in ....

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\Wingate\Default Rights

I can be emailed, if preferred, paul.brown@edihouse.ie


Thanks again for all your help,

Paul.

[Pascal]

Under Default Rights you want to have a look at "Access" and find the recipient for "Everyone" under that. Each of the "SpecifyXYZ" entries indicate a specific component (Ban, Time, Location, etc.) and if any of those are set they could be the ones denying access. Double check specifically that "SpecifyUser" is not set to 1. If the "UserName" value is "Everyone" and "SpecifyUser" is set to 1 that will always fail with the problem you are describing. (For any policy)

However, from the sound of it it seems as if your problem might be related to synchronisation between the UDB and the active directory. (You don't have any users, thus authentication on policy is failing, etc.)

But try the registry first, then we can dig into that section of it.

[paul_edi]

Thanks Pascal,

I was able to change Recipient4 to "Everyone" and the SpecifyUser to "0".

I can now log on to Gatekeeper!! I added the "Administrators" back into the System Policies....I can't remember removing it originally....rather stupid on my part, well it was 2:45 am on Sunday!!!!

I have changed the registry settings back to their originals, removed the IP address from the "Advanced Options" and ensured the IP address is not in the Forwarders list on the servers DNS properties.

Hey Presto ....WinGate is working absolutely fine!


Thanks James, Matt and Pascal....excellent support!!

Regards,

Paul.