any errors on event viewer? 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.
"Peter Poulimenakos" <(E-Mail Removed)> wrote in message
news:1f2d01c3e0f5$05349f90$(E-Mail Removed)...
> The problem still persists... I edited the LMHOSTS file
> as with the IP address of our domain controller with the
> #DOM setting and rebooted, but it didn't help.
>
> The W98 clients have the AD client installed and are
> setup with the correct IP address for both DNS servers
> and the WINs server. The only network protocol we are
> using is TCP/IP.
>
> Perhaps the problem has something to do with the switch
> we are using? (Allied Telesyn Rapier 24) Does the switch
> need to be configured in any particular way for W98
> clients to be able to login to a Windows 2003 domain?
>
>
>
> >-----Original Message-----
> > Do the W98 clients have the AD client installed? If
> yes, do they have the
> >correct DNS address configured (ie the IP address of
> your local DNS server).
> >
> > If they do not, are you running WINS? If not, you
> may need an LMHOSTS
> >file on the clients with a #DOM entry for the domain
> controller which is on
> >the "other" segment.
> >
> >"Peter Poulimenakos"
> <(E-Mail Removed)> wrote in message
> >news:00ce01c3dbed$2ae10d30$(E-Mail Removed)...
> >> Hello,
> >>
> >> I am experiencing the following problem when I try to
> >> login to the Windows 2003 Domain using a Windows 98se
> >> workstation.
> >>
> >> 'no domain controler is available to authenticate
> you...
> >> etc.. ect..'
> >>
> >> The network is setup with two networks, 192.168.2.x and
> >> 192.168.120.x with a subnet mask of 255.255.255.0. The
> >> 192.168.120.x computers are all going through a layer 3
> >> switch wich is connecting them to the 192.168.2.x
> >> network. The domain controlers are all located on the
> >> 192.168.2.x network and I have no problem loging into
> the
> >> domain from that network.
> >>
> >> But when I try to login from the 192.168.120.x network
> it
> >> comes back with the 'no domain controller is available'
> >> message. I can ping to and from both networks no
> problem,
> >> and I still have access to network resources, it just
> >> takes the workstation forever to boot to the desktop
> and.
> >>
> >> Any ideas on how to resolve this problem?
> >>
> >> Regards,
> >>
> >> Peter Poulimenakos
>