Authentication failed - user Guest on 192.168.x.x requested

[Elijah-777]

Hi - my first post.

On a second Server (Win2k) on the same INTERNAL subnet running Wingate 6.6.3, FROM the main server (IP above 192.168.x.x Win 2003) running Wingate 6.5.2, we get this error message below coming in ONCE EVERY 2-3 minutes <?????>

Object: Authentication
Time: 27-Mar-2012 16:53:09
Message ID: 0301
Description: Authentication failed - user Guest on 192.168.x.x requested

HOW CAN THIS MESSAGE BE STOPPED PERMANENTLY????

Win2k machine just had software reinstalled plus Wingate (never had this issue before).

There shouldn't even BE a Guest Account trying to access the Win2k Server on the subnet
from the main Server.

Both machines have two NICs. The internal NICs link the two servers and the external NICs takes both machines into
the Internet Router on a separate subnet. These are the only two machines on the subnets.

The WIN2k machine is only a storage server with occasional web access needed and for faxes and a scanner.
IIS is NOT even installed.

HOPE SOMEONE can advise how to STOP this error message - TRIED EVERYTHING i can think of SO FAR...

Thanks and God Bless you In JESUS - Amen

Elijah

For EVERYONE with Hope : http://www.Constellation7.org/TheSimple ... fFaith.htm

† Matthew 3 : 16 - 17 †
"And Jesus, when he was baptized,
went up straightway out of the water:
and, lo, the heavens were opened unto him,
and he saw the Spirit of God descending
like a dove, and lighting upon him:
And lo a voice from heaven, saying,
This is my beloved Son, in whom I am well pleased."

[Elijah-777]

Hey Matt - Thanks very much. Your words below really helped.

Realised that the meltdown machine IP was registered in the DNS settings for the main server;
but when re-installing for the old machine i changed the machine name.

Removed all the old machine name Zones for the WIN 2K Server from the Master DNS
Records in the WIN 2003 machine and the Authentication errors STOPPED - Amen

As a suggestion for the future, it would be cool if the Authentication Warnings
had more verbose detail, LIKE the system or user Origin service or application.

All i could see was the Warning / Error Messages -
NO way to know where they came from.

Will post this in the Forum - may help someone else one day.

God Bless you In JESUS Alive - Amen

Elijah

http://www.Constellation7.org/TheSimple ... fFaith.htm

2 Timothy 4 : 5
"But watch thou in all things,
endure afflictions,
do the work of an evangelist,
make full proof of thy ministry."

Hi Elijah,

The guest account is the name that WinGate gives to any connection that is not authenticated. WinGate can only know the username that initiated a session if there is an authentication policy in place and the user authenticates, otherwise all connections are attributed to the Guest user. So if you're getting a connection coming in and there is no authentication policy, or the connection hasn't yet authenticated, you will see it as the Guest user, whether or not the Windows Guest user is enabled.

What is the connection trying to reach? Do you see a URL or an IP address?

Thanks,

Matt Parker
Qbik New Zealand