Error ID 5719. Source Netlogon

For some reason I am getting the following on all my workstations:

Error ID 5719. Source Netlogon
No Domain Controller is available for domain <my domain name here> due to
the following:
There are currently no logon servers available to service the logon request.
..
Make sure that the computer is connected to the network and try again. If
the problem persists, please contact your domain administrator.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I have looked at everything I can think of.

I can login to the domain
I can ping the DC
The computer is in the DC
The DC is the DNS and is pointing to itself
I can see and use file/print shares, etc.

Basically, if I didn't look in the event log I probably would not see
anything wrong with the network except for one thing. I have one machine
that uses a share on another as a source of family pictures for a screen
saver. This is mapped as the T: drive. This will work fine for about a
day, and then when you look at the screensaver it will indicate it can no
longer see T:. I have to reboot to regain connectivity. I can still see
the other machine, but it won't reconnect on the fly. This is what started
it. Other than that everybody can login, print to network printers, see
each others shares, whatever. I have looked at numerous MS KB articles but
can't find an appropriate solution.

--
--Jim
©¿©¬



If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

quoted from http://www.ChicagoTech.net
Event ID 5719 - The system cannot log you on now because the domain "name"
is not available."
Symptoms: when attempting to logon a domain, you keep getting an error that
"The system cannot log you on now because the domain "name" is not
available." Also, Event viewer shows Event ID: 5719. No Windows NT or
Windows 2000 Domain Controller is available for domain <domain name>. The
following error occurred: There are currently no logon servers available to
service the logon request.

Resolutions: One possible cause of this error is that you have run out of
buffer space in the NetBT datagram buffer. To resolve this problem, increase
the MaxDgramBuffering value from 128 KB to 256 KB. Run Regedt32.exe, go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT\Parameters. On
the Edit menu, click Add Value, and then add the following information:

Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000


--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"jtpr" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> For some reason I am getting the following on all my workstations:
>
> Error ID 5719. Source Netlogon
> No Domain Controller is available for domain <my domain name here> due to
> the following:
> There are currently no logon servers available to service the logon
> request.
> .
> Make sure that the computer is connected to the network and try again. If
> the problem persists, please contact your domain administrator.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> I have looked at everything I can think of.
>
> I can login to the domain
> I can ping the DC
> The computer is in the DC
> The DC is the DNS and is pointing to itself
> I can see and use file/print shares, etc.
>
> Basically, if I didn't look in the event log I probably would not see
> anything wrong with the network except for one thing. I have one machine
> that uses a share on another as a source of family pictures for a screen
> saver. This is mapped as the T: drive. This will work fine for about a
> day, and then when you look at the screensaver it will indicate it can no
> longer see T:. I have to reboot to regain connectivity. I can still see
> the other machine, but it won't reconnect on the fly. This is what
> started
> it. Other than that everybody can login, print to network printers, see
> each others shares, whatever. I have looked at numerous MS KB articles
> but
> can't find an appropriate solution.
>
> --
> --Jim
> ©¿©¬
>
>
>
> If you want to reply by email its --> ryan at jimryan dot com
> Please use BCC and lets all avoid spam
>
>
>

Thanks, I found this before, but now I'm thinking they are referring to the
DC, not the client (its not clear). I'll try upping this parameter on the
DC tonight. It had no effect on the client.

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam
"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> quoted from http://www.ChicagoTech.net
> Event ID 5719 - The system cannot log you on now because the domain "name"
> is not available."
> Symptoms: when attempting to logon a domain, you keep getting an error
that
> "The system cannot log you on now because the domain "name" is not
> available." Also, Event viewer shows Event ID: 5719. No Windows NT or
> Windows 2000 Domain Controller is available for domain <domain name>. The
> following error occurred: There are currently no logon servers available
to
> service the logon request.
>
> Resolutions: One possible cause of this error is that you have run out of
> buffer space in the NetBT datagram buffer. To resolve this problem,
increase
> the MaxDgramBuffering value from 128 KB to 256 KB. Run Regedt32.exe, go to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT\Parameters. On
> the Edit menu, click Add Value, and then add the following information:
>
> Value Name: MaxDgramBuffering
> Data Type: REG_DWORD
> Value: 0x40000
>
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
help.
>
> Robert Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "jtpr" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > For some reason I am getting the following on all my workstations:
> >
> > Error ID 5719. Source Netlogon
> > No Domain Controller is available for domain <my domain name here> due
to
> > the following:
> > There are currently no logon servers available to service the logon
> > request.
> > .
> > Make sure that the computer is connected to the network and try again.
If
> > the problem persists, please contact your domain administrator.
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > I have looked at everything I can think of.
> >
> > I can login to the domain
> > I can ping the DC
> > The computer is in the DC
> > The DC is the DNS and is pointing to itself
> > I can see and use file/print shares, etc.
> >
> > Basically, if I didn't look in the event log I probably would not see
> > anything wrong with the network except for one thing. I have one
machine
> > that uses a share on another as a source of family pictures for a screen
> > saver. This is mapped as the T: drive. This will work fine for about a
> > day, and then when you look at the screensaver it will indicate it can
no
> > longer see T:. I have to reboot to regain connectivity. I can still
see
> > the other machine, but it won't reconnect on the fly. This is what
> > started
> > it. Other than that everybody can login, print to network printers, see
> > each others shares, whatever. I have looked at numerous MS KB articles
> > but
> > can't find an appropriate solution.
> >
> > --
> > --Jim
> > ©¿©¬
> >
> >
> >
> > If you want to reply by email its --> ryan at jimryan dot com
> > Please use BCC and lets all avoid spam
> >
> >
> >
>
>