Assumed User by Machine Name Stopped Working

[z80jim]

On my network I use authenticate based on machine name. This has been working fine.

Last week a user could no longer authenticate. No changes were made to my Wingate configuration. All the authentication is set up right. It was only this one user. To bypass I had to change to authenticating based on his ip.

Now today, my authentication stopped working also. Same situation. I have not made any changes to Wingate.

Some advice on where or what to look for would be appreciated.

Wingate 6.03.

Regards,
Jim Weil

[jamesc]

Assuming by computer name requires WinGate to be the DHCP server; is that the case?

Can you check that your Windows Firewall is disabled in the services, and any other security suite for the sake of testing?

*Edit Also, the latest verison of WinGate is 6.1.1

[z80jim]

Thanks for the reply.

Wingate is our DHCP server. No Windows firewall services running.

Again, all 40 of my users are assumed by machine name and it has been working fine for over a year. Now, in two weeks, it has stopped working for two users. The others are still fine.

Thanks,
Jim

[MattP]

Hi Jim,

If you do an IPCONFIG /ALL on these two machines do they list the WinGate server as their DHCP server? Are the machine names listed correctly?

[z80jim]

Matt,

In the last two months I had switched these machines to a fixed IP instead of DHCP because I need to do some port forwarding from the internet to these machines. Can that be causing it? I have another user that is on a fixed IP and they are working fine thought.

Thanks,
Jim

[jamesc]

Hi Jim,

Hard to say, we probably need to have a review of your policies to make sure there is nothing blocking it in there. Can you zip and send the following details to sales@wingate.com and reference this forum post?

1. An ipconfig/all from a LAN Client and the WinGate server.
2. What connection methods your LAN client use; NAT / WinGate Internet Client (WGIC) / Proxy
3.WinGate Registry:
GateKeeper --> Options menu --> Advanced --> Save Registry Settings
4. WinGate Config Report
GateKeeper --> Options menu --> Advanced --> Save Report
5. Usernames / computer names / ip addresses of the computers with issues.

[ChrisH]

I think WG gets 'confused' when a static IP is set as it no longer knows or can correlate the static IP to a machine name. What if you set up a reservation using WG's DHCP service as shown below? This way WG will always give the same IP to the machines' as you require.

[z80jim]

Chris,

Outstanding. Didn't even know you could do that in WG DHCP, but that did the trick.

Thanks a million.

Jim

[greboriorobert]

May be password had time validity. See local policies in Administration tools

[adrien]

Matt,

In the last two months I had switched these machines to a fixed IP instead of DHCP because I need to do some port forwarding from the internet to these machines. Can that be causing it? I have another user that is on a fixed IP and they are working fine thought.

Thanks,
Jim

Hi Jim

Moving from DHCP to fixed IP will do it. Because WinGate relies on the DHCP settings to know the machine name normally for the purposes of assumptions by machine name. It will take a while however, since WinGate will consider the DHCP lease to be valid for quite some time (default is 60 days with WinGate).

Regards

Adrien