Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Wingate DHCP & Assumed Users

Oct 15 04 4:41 am

Hi,

I disabled WG DHCP and used Win2003 DHCP instead (thesame machine). After doing this, assumed users (By Computername) are not able to browse the internet and IE would display "Forbiden......".

I also noticed that Gatekeeper is no longer displaying computer names but only IP addresses. This could be the reason why assumed users (By Computername) are having problems.

Tested using Assumed by IP Address and everything works fine. I don't want to use Assumed by IP since we are using DHCP.

-WG6.0.3 build 1005 on Win2003 Server.

Oct 15 04 8:31 am

Hi there

As per the WinGate helpfile, to run assumed users by computername clients must be using WinGate DHCP.

Unfortunately Assumed users by computername will not work when they receive IP details from another DHCP server.

Regards
Erwin

Oct 15 04 11:11 pm

erwin wrote:Hi there

As per the WinGate helpfile, to run assumed users by computername clients must be using WinGate DHCP.

Unfortunately Assumed users by computername will not work when they receive IP details from another DHCP server.

Regards
Erwin


And when will this problem be solved ??

Oct 16 04 1:12 am

I don't think it's seen as a problem, just the way it works.

Sounds difficult to implement.

SkyMan

Oct 16 04 6:44 pm

But why is it that I can see computer names in the Network tab. Can Qbik do anything about this. I am personally more comfortable using DHCP Server of Win2003.

Oct 16 04 8:51 pm

When a machine connects to WinGate, WinGate looks up in its database of DHCP clients that it knows about (only if it allocated them) to find the machine name.

I'll see if we can do anything about this - the Network panel was added a long time after the DHCP server. We do have IP->machine name tables from this, although it is not always very reliable.

Adrien

Oct 17 04 2:55 am

Thanks. Hope it will come soon as I have temporarily disabled WG Authentication because of this issue.

Nov 02 04 9:20 pm

Maybe I'm asking too soon, but what the status on this problem ??
I'm having the same problem and clients have noticed it, some of them already managed to gain access to the Internet just by filling in the proxy server and I can't block them!
Some help or a fix would be highly appreciated :).

Nov 03 04 2:18 am

I hope QBik can address this issue ASAP.

Wingate DHCP

Nov 05 04 12:06 pm

I don't know all the details of your situation, but why are you so down on the wingate DHCP service? I've been using it for over a year with no problems at all. However, I only have around 50 clients, so this is no enterprise class environment.

Wingate's logging of the DHCP transactions is also very nice (you have to turn on DHCP debugging to get all the details).

So given that you can use machine name based assumptions and full transaction logging as well as have full control over the IP scheme, I'm just not sure why you wouldn't want to use the wingate DHCP.

Maybe there are some cool features I'm missing with the Win2k3 DHCP server?

G

Nov 06 04 8:01 pm

The main reason I shifted to Win2K DHCP is due to IP Conflicts. We have a mix of DOS/Win95/98/XP/2000 Worstations. Sometimes IP Conflicts occur and renewing the clients IP with Wingate's DHCP does not solve the conflict and I had to manually assign a static IP on the other machine to correct the problem. But when I started using Win2K DHCP, resolving IP Conflicts is done by just restarting the machine or renewing the IP.


jian

Nov 09 04 3:05 am

My reason is that I don't want to use wingate DHCP because Win2k3 handles it just fine and that I don't want 15 different programs on my server which Win2k3 could do also. The less programs I need on my server, the better. The more programs you install, the more conflicts/problems you'll get.

assumed users

Nov 10 04 2:24 am

i have similar issues. wg 5 dhcp and dns disabled; win2k server pdc issuing ip addresses and dns configured; same computer. my clients get outlook express "access denied" error and on the server "authentication failed - user guest on 192.168.0.(number within my dhcp scope) requested pop3/smtp". this is due to the lack of entries in the "assumed users - by ip address", as noted previously. my work-around is specifying a wildcard, i.e. 192.168.0.* - is assumed to be - administrator. unfortunately when the clients need to authenticate/logon for web browsing, their java window pops up with "administrator" as the user - on any/all machines; they make the appropriate name change, enter their password and log on as usual. are there any negative issues for my configuration? failing this the clients have to logon via their java window to check their email, which means launching their browser, navigating to a website (to pop up the java window), logging in (making the appropriate user name change) then proceeding to their email client. i can hear the complaints coming in already.

Nov 26 04 11:32 pm

Dear Qbik,

How are we doing on this problem ??
Will there be a fix in the future (a.s.a.p.) ?
Otherwise I am forced to drop your license and look for other software that does support this.
I'm using Wingate since version 3.x and never had this problem before, just since version 6.x.

We have a big problem now, because anyone can use Internet to download just about everything, just by filling in the correct proxy ip-adres.
Post a reply