mcit wrote:I have set it up so that the server is running to accept assumed users only, I have set the assuming computer names and created usernames for the assumed computers. The problem is that I am finding that it seems to block access to all of the Windows 98 machines, the XP machines work ok though.
Is there any difference in configuration between the machines? Only DHCP clients can use name-based assumptions; so be sure that the 98 clients have requested their config from WinGate.
One alternative to using user assumptions is authentication. You can make that fairly transparent for the users if you follow a few simple guidelines. For examples, NTLM authentication over an HTTP link will automatically log the currently logged in user in. So, your login to your OS becomes your login into WinGate. Ditto, using mail authentication methods - your security level can be raised and you will be associated with the appropriate user name. Etc. Of course, this only covers the cases where the underlying protocol has some form of authentication - so it's more suited to groups that are running HTTP, SMTP+POP3, etc. type of scenarios rather than a swathe of custom software with internal protocols.
Edit: That should be qualified. It is only available for the POP3 Server and SMTP Server, not the proxies. The ideal scenario is still to get the assumptions to work perfectly.
mcit wrote:If I can get the server to connect to both connections, then
http://forums.qbik.com/viewtopic.php?p= ... ght=#12719
Gives you some idea how to do it 5.2.3. 6.0.3 is significantly better for this type of scenario, though, and you can use it with a version 3, 4 or 5 license key.