Re: Event ID 5807 / Netlogon



Hi

check:
http://www.jsifaq.com/SUBR/tip8800/rh8877.htm


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"ThOF" <mpareja@xxxxxxxxx> wrote in message
news:OF1ZZO3mGHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Hi all the group;

I'm constantly seeing on some of my DCs the Event ID 5807 (source
Netlogon) which argues about client IP addresses not mapped to any site

The IPs that appearsin the netlogon.log file are IPs from remote VPN
clients and also IPs from another different Windows domains in which we
trust (we've configured trust relationships among them, but I don't think
it should be neccesary define new sites for those remote domains!)

I've searched all over the Internet and Google Groups to see if some
decent explanation and/or workaround can be done for this, but wasn't
unable to find it

Remote clients (RAS/VPN) are in fact appearing in the netlogon.log with
their public IP addresses (i.e. 80.0.0.0/24) not with the "conversed"
internal ones.

On the other hand, DCs from remote domains in which we trust appear with
their "correct" internal IP addresses (i.e. 172.16.0.0/16)

Anyway, for this kind of cases, what would be the best
solution/workaround? Define a new subnet (i.e. 80.0.0.0/24) and then
associate it with the existing site where the DC that is arguing belongs?

Obviously, I don't want to define a new site for the remote users because
that site will not have any DCs!!! (the DCs for those clients are added in
the remote domain, of course). Moreover, if I try to define a new site in
my domain I have to add the replication link between this new site and the
other existing ones, and I don't want this, neither!!)

What I have done by now is to simply create subnets for the "unclassified"
IPs and then simply assign those subnets to our local site (where the main
DC is located) although I recognise those clients shouldn't belong to
it... but is the best solution I've thought of

Regards and many thanks in advance.



.



Relevant Pages

  • Re: Event ID 5807 / Netlogon
    ... The IPs that appearsin the netlogon.log file are IPs from remote VPN ... clients and also IPs from another different Windows domains in which we ... What I have done by now is to simply create subnets for the "unclassified" ...
    (microsoft.public.windows.server.active_directory)
  • Event ID 5807 / Netlogon
    ... The IPs that appearsin the netlogon.log file are IPs from remote VPN clients ... What I have done by now is to simply create subnets for the "unclassified" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Virtual LAN Problem
    ... > connectivity with the remote LAN and from the remote LAN. ... It collapsed after trying to allow it to have a remote DNS address ... Confirm a decent tunnel by pinging the remote site internal clients. ... > But I had full access to the files shares on the SBS box! ...
    (microsoft.public.windows.server.sbs)
  • Re: Connect to Small Business Server VPN
    ... The remote clients are assigned IP address and gateways that are identical. ... I ask because most home users are going to all be on these same subnets when connecting remotely and this causes all kinds of browsing/connecting issues. ... then unable to access or ping computers on the internal network. ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual LAN Problem
    ... Gateway device and MANUAL DNS settings to get it to work. ... connectivity with the remote LAN and from the remote LAN. ... Confirm a decent tunnel by pinging the remote site internal clients. ...
    (microsoft.public.windows.server.sbs)