 Features
FAQ
Pricing
Download Free Trial Version
Order Form
Support
Connection
Back To Main Software Page
|
WinGate Technical Support FAQ
Before doing any trouble shooting, be
sure to upgrade to the latest version of WinGate from the
WinGate download page at ZiD !
- How do I restrict access to certain
web sites?
- How do I tell which version of
WinGate I am currently running?
- My Winsock 32 DLL file keeps
performing illegal operations on the Win95
machine running WinGate. Why?
- Occasionally, my WinGate seems to
randomly dial out and connect to the Internet.
Why might that be?
- After sitting idle for a period of
time, the WinGateEngine in my NT machine will no
longer respond to requests from the workstation,
requiring that I shut down, and restart the
service, or Win95 will get a RNAAPP.EXE crash.
- The WinGateEngine will not start in
Control panel, Services when I try to start it
manually.
- When I shut down my NT machine
running WinGate, the WinGateEngine will not shut
down. I just get some sort of call back message.
- Can I run an internal SMTP mail
server such as Microsoft Exchange on my LAN
behind WinGate, and connect it through WinGate
for Internet mail?
- I get a 2186 Error when I try to
start the Qbik WinGateEngine service in Control
panel, Services, Why?
- Can I configure MS Front Page to
connect through WinGate?
- I have forgotten my Administrator
password for Gatekeeper, or Gatekeeper no longer
accepts my Administrator password, how can I get
logged back in?
- I just installed WinGate, and
can’t log in to Gatekeeper. How do I log in?
- WinGate won’t accept my license
number and registration key.
- Why can’t I transfer files in
IRC via DCC?
- Can I connect a MAC through WinGate
on my network?
- I am running WinGate 2.0 Pro, how do
I add users in Gatekeeper?
- Why do I see a strange IP address in
Gatekeeper when I am logged on from the WinGate
machine?
Q: How do I restrict access
to certain web sites?
A: To
create rules and policies to restrict access to
specific sites on the Internet, simply follow
these instructions. You need to remember that
since WinGate 2.0 will perform
HTTP-to-SOCKS-handovers you will need to
duplicate any HTTP policies you create with SOCKS
policies, other wise, when the request can't go
through HTTP, it will just switch over and go
through SOCKS.
For example purposes, we will create a policy
that will not allow any users to attach to web
sites containing the character string XXX.
1. Log into Gatekeeper.
2. Edit the WWW proxy service by double clicking
it
3. Click on the Policies tab
4. Deselect the "Use default rights"
option at the bottom of the window
5. Click the "Add" button
6. Select the "Request" tab.
7. Choose the "Specify which requests"
option
8. Click the "Add Filter" button
9. Click on the filter that you created to
highlight it
10. Click the "Add Criterion" button
11. Select the "This criterion is NOT met
if" option
12. In the first box, scroll down to HTTP URL and
select it
13. In the middle box, scroll down to and select
"Contains"
14. In the last box, type in the particular URL,
or words that may be contained in a
URL that you don't want your users accessing, in
this example, I will use "XXX"
15. Click OK, then add more criterions or filters
if you want, otherwise, click OK again,
and again until you are back at the Gatekeeper
screen
16. Edit the SOCKS proxy service by double
clicking it
17. Follow steps 3 through 15, only in step 12,
scroll down to "Server name" instead
of HTTP URL
That is all there is to setting up policies to
restrict access to certain URL's and web sites.
Q: How do I tell which
version of WinGate I am currently running?
A: To find out which version of
WinGate you are running, open up a DOS prompt and
switch to the directory that WinGate is installed
in. By default, this is \Program Files\wingate.
Once there, enter the command wingateengine -v
(NT) or wg2eng95 -v (W95). This command will
report the version back to you.
Q: My Winsock 32 DLL file
keeps performing illegal operations on the Win95
machine running WinGate. Why?
A: These Illegal operations that are
occurring in your Winsock 32 can be caused by a
couple of different things. One, your Winsock DLL
file may be corrupt, or bad. The solution here is
to take a copy of the DLL file from another
machine on your network and overwrite the file on
your WinGate machine with it. The other cause is
not quite so simple, but is just as easily fixed.
It has to do with problems at your ISP. We have
seen many cases where simple problems at an ISP
have caused WinGate to crash.
These problems can range from modems that don't
answer to bad DNS servers. In this case, the
latter is likely the cause here. Try changing the
DNS servers in your WinGate machine's DNS server
search order to the following:
Primary DNS: 198.109.118.94
Secondary DNS: 198.109.118.67
These are known good DNS servers, and have fixed
this crashing problem in several instances.
Q: Occasionally, my WinGate
seems to randomly dial out and connect to the
Internet. Why might that be?
The problem of WinGate randomly
dialing out to your service provider is most
likely caused by DNS lookups coming from your
workstations. These don't have to be Internet DNS
lookups, but can be requests for workstation
names on your local network. Some TCP/IP stacks
also have a built in name resolver that
periodically refreshes their cache, NT 4, and MS
office 97 seem to do this. The way to fix this is
to edit the DNS service in WinGate, and uncheck
the "allow service to start dialer"
option. WinGate's autodialer will still work for
http and email requests, but not for SOCKS, or
other native DNS lookups.
Q: After sitting idle for a
period of time, the WinGateEngine in my NT
machine will no longer respond to requests from
the workstation, requiring that I shut down, and
restart the service, or Win95 will get a
RNAAPP.EXE crash.
A: This is the result of a timing
problem between WinGate and RAS. It has to do
specifically with the rate that WinGate's dialer
polls the RAS connection for connection status.
To fix this, log in to Gatekeeper, and open the
Dialing box. Then, > select the
"settings" tab. In the Advanced section
of this window will be a setting called
"Online status check update interval".
This comes set to 2 by default, which is normally
fine. On certain installations however, it is too
fast. Try changing this setting to 10, and see
what happens. This normally fixes this problem
completely. Just remember to press the "save
to disk" icon in the upper left-hand window
of Gatekeeper before logging out (it is the one
that looks like a little disk.) Other wise, the
next time you shut the WinGateEngine down, this
setting will revert back to 2, and the problems
will start over again. There is also a setting in
the Windows registry that may be effecting this,
Edit your registry and go into
Hkey_Local_Machine\Software\Qbik software\
wingate 2. Highlight Dialer, and highlight
RASdialTimeout, the setting should be at 90000.
Edit this entry, and modify it by selecting
decimal and change the value to 120000. Exit the
registry editor, and reboot your computer for the
changes to take effect.
Q: The WinGateEngine will
not start in Control panel, Services when I try
to start it manually.
A: There are two possible fixes for
this problem, they are,
1. If you are running MS IIS on the WinGate
machine, there will be a port conflict that may
stop the WinGateEngine from starting. The fix for
this is to shut down the IIS, and start the
WinGateEngine, then log in to Gatekeeper, and
change the ports that WinGate listens to for WWW,
and FTP proxies. Then restart the IIS service.
2. If the above does not work, or you are not
running IIS, uninstall WinGate 2.0, and remove
all references of it from the Windows registry,
including references to WinGate 1.3 (remember to
stop the WinGateEngine service before running the
uninstaller, otherwise you may not be able to
completely remove the Engine.) Reboot the system.
Then reinstall from scratch.
One of these two fixes normally takes care of
this particular problem.
There are a couple of things to check here also.
The first thing WinGate tries to do is change
directories into the directory that the EXE file
is in, so that any subdirectories are in the
right place. This was done, because the Service
Control Manager runs everything out of the
system32 directory.
If WinGate cannot change directories, it
terminates. Reasons for not being able to change
directories:
1. On an NTFS partition, the System account does
not have sufficient rights to the WinGate
directory.
2. On an NTFS partition, the System account does
not have "Bypass Traverse Checking"
rights.
We are changing this behavior in the version C
release, so that if WinGate cannot change
directories, it will still run, even if it does
put directories all over the place.
Q: When I shut down my NT
machine running WinGate, the WinGateEngine will
not shut down. I just get some sort of call back
message.
A: When the WinGateEngine will not
shut down automatically while shutting down the
computer, you have probably configured the Qbik
WinGateEngine service to interact with the
desktop. Deselect this setting, under control
panel, services, highlight Qbik WinGateEngine,
shut the service down, and restart it. That
should take care of the problem.
Q: Can I run an internal
SMTP mail server such as Microsoft Exchange on my
LAN behind WinGate, and connect it through
WinGate for Internet mail?
A: To configure WinGate to allow you
to Send/Receive from internal SMTP server, you
will have to configure special mappings in the
SMTP mapping service in Gatekeeper. All you need
to do to accomplish this is:
Log on to gatekeeper, double click services, SMTP
server
General tab
Check, accept connections on port 25. Check
enable default mapping to:
Server: enter the address of the network card for
the internal SMTP,
on port 25.
Mappings Tab
Press, add
Check enable mapping to: Server: ISP's SMTP
Server Name, on port 25.
Locations Tab:
Check specific locations from where this mapping
applies.
Included locations: enter the address of the
network card for the
internal SMTP (the same as the address that you
have for your default
mapping under the General tab.)
Press, add
This will cause WinGate to route all traffic
coming to port 25 to the machine running your
internal SMTP server, unless it is originated by
that machine, in which case, it is piped directly
to your ISP's SMTP server.
Q: I get a 2186 Error when
I try to start the Qbik WinGateEngine service in
Control panel, Services, Why?
A: This situation is caused when the
installer fails for some reason and the user runs
WinGateEngine -i from the command line to fix it.
The typical reason is that the user is not logged
in as administrator when installing WinGate. What
happens in the installer is, it creates a key in
the registry to tell WinGate to install itself as
a service when run by the installer (because our
poked install package cannot handle command line
parameters). WinGate removes this key itself when
it installs itself, so that the next time it is
run without command line parameters (by the
service control manager hopefully), it will run
normally.
However, if the user is not logged in as
Administrator to NT, WinGate will not be able to
install itself as a service, and the registry key
will not be removed. Then when the user types
WinGateEngine -i, it uses a different section of
the code, and the key is not removed either. Then
when the service control manager start WinGate,
it checks for the key, and it is still there, so
it tries to install itself as a service.
Unfortunately at this stage, it hangs, because
the service control database is locked when
starting services. So the key still isn't
removed, and the service control manager times
out after a while with the message "Error
2186: the program did not respond in a timely
fashion"
In the key HKEY_LOCAL_MACHINE\Software\Qbik
Software\WinGate2\Settings\
delete the value "InstallService" This
should take care of this problem for you.
Q: Can I configure MS Front
Page to connect through WinGate?
A: Setup Front Page as follows;
Start up FrontPage, go to tools, options, proxies
tab, in HTTP proxy field put WinGate or (the name
or IP address of the WinGate machine).
Select site to edit.
Q: I have forgotten my
Administrator password for Gatekeeper, or
Gatekeeper no longer accepts my Administrator
password, how can I get logged back in?
A: Under the Start button click
"run" and type in "regedit".
Then open the directory
HKEY_LOCAL_machine/software/Qbik
Software/WinGate2/userdatabase/administrator.
Select administrator and press the delete key.
This will remove any and all information
pertaining to the administrator. Exit regedit and
reboot computer. You should be able to log on
gatekeeper as a new Administrator without a
password. Then assign a new password under
"file", "change password".
Q: I just installed
WinGate, and can’t log in to Gatekeeper. How
do I log in?
A: The first time that you log in to
Gatekeeper you need to log in as Administrator
(with an uppercase A,) no password, on server
name localhost and port number 808. If you are
running WinNT, you also need to go into Control
panel, services, and make sure that the Qbik
WinGateEngine service is installed, and started.
You will have to switch this to Automatic, and
start it manually the first time, but after that,
it will start automatically on boot up. If there
is no WinGateEngine service, go to a dos prompt
in your WinGate directory, and type WinGateEngine
-i and hit enter, that will install the service.
Then make the above changes to it, and that
should get you on line.
Q: WinGate won’t
accept my license number and registration key.
A: When entering your registration
information into WinGate, you need to be very
careful to enter the proper information into the
proper fields, and to enter it correctly. Make
sure that you are entering the license name (Your
software is registered in the name of:) in the
"Licensee" field, and your registration
key into the key field. If at all
possible, you should copy and paste this
information from the original email that you
received it in, as it is sensitive to case,
punctuation, and spaces. If you can not copy and
paste it in, make sure that you type it in
EXACTLY as it appears in the original email,
other wise it will not work.
If it still does not work, please send an e-mail
to trialkey@fttc.com and we will issue you a new
key.
Q: Why can’t I
transfer files in IRC via DCC?
A: Due to the fact that DCC send and
receive require a dynamically assigned TCP port,
it is not possible to implement either through
WinGate. The developers of MIRC and Aventail
AutoSOCKS are currently working on a solution for
this, but as of now, there is no way to make it
work.
Q: Can I connect a MAC
through WinGate on my network?
A: WinGate will support connections
from almost any TCP/IP stack, though it was
developed on, and for Microsoft's TCP/IP stack
built in to Win95 and NT. It is possible to
connect through WinGate on a network using UNIX,
Linux, and MAC's.
For information on connecting MAC's through
WinGate, go to http://mag-nify.educ.monash.edu.au/Wingate/mac.html and read
through the article.
Q: I am running WinGate 2.0
Pro, how do I add users in Gatekeeper?
A: Adding a User:
On the Configuration pane there are seven
branches. The top branch is Users. Click the +
sign to view registered users. Initially there
will be two users, Administrator and Guest. For
organizations that wish to use the accounting
features, a user record must be set up for each
individual account.
To add a user
1. Open the user tree by clicking on the + sign
2. Right click on any user and select ‘New
User’
3. You will be presented with a Tab control .
4. Type in the users name (eg mary-bob) into the
Username field
5. Enter the users Real name (optional)
6. Get the user to enter and confirm their
password, or leave it blank and select ‘User
must change password at next logon’
7. Enter a description (optional)
8. Select the options you wish for that person.
9. Click OK.
The options on the User info tab are self
explanatory, though they are discussed in the
security section on the help desk.
http://www.wingate.net/help.htm
10. Select Polices, default polices, add, select
everyone or specific user or group, highlight the
user and select an option at bottom of screen.
11. Each user that has to authenicate, will log
on to gatekeeper from their workstation.
Client Machines:
Don’t run the full install on client
machines. Simply copy these files to a shared
directory, or to each machine.
GateKeeper.exe
wingate2.hlp
wingate2.cnt
wg2util.exe
wg2auto.ini
Q: Why do I see a strange
IP address in Gatekeeper when I am logged on from
the WinGate machine?
A: The IP address that you are seeing in
Gatekeeper running on the WinGate
machine is due to the fact that 127.0.0.1 is the
default loop-back address that is
standard with TCP/IP networking, and TCP/IP
stacks. All this means is that you are
logged into the WinGateEngine service from the
local host machine, or the local
machine. This does not effect the IP address that
the rest of your network sees. There
is no need to change this value.
|