Networking Forums

Networking Forums > Computer Networking > Windows Networking > no domain controller is available...

Reply
Thread Tools Display Modes

no domain controller is available...

 
 
Peter Poulimenakos
Guest
Posts: n/a

 
      01-22-2004, 01:35 PM
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


 
Reply With Quote
 
 
 
 
Robert L [MS-MVP]
Guest
Posts: n/a

 
      01-22-2004, 05:30 PM
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

>



 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      01-22-2004, 09:54 PM
If the machine has the AD client installed, it should be using DNS/LDAP
to find the domain controller, just like W2k/XP does. So it won't be using
LMHOSTS or WINS for this. Slow logins usually mean incorrect DNS settings.

Does it have your local AD DNS server as its only DNS reference?

"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

>



 
Reply With Quote
 
Peter Poulimenakos
Guest
Posts: n/a

 
      01-26-2004, 11:32 PM
No, there are two DC (both Win 2003) with IPs of
192.168.2.11 and .12. The 98 clients are configured with
both these servers for their DNS settings.

Did I mention that 98 clients on the same network can
authenticate... With the same network settings... It's
just the ones on networks other than the one that the
domain controllers are on that are having difficulty
finding the DC. See msg bellow for details.

Regards,

Peter S Poulimenakos


>-----Original Message-----
> If the machine has the AD client installed, it should

be using DNS/LDAP
>to find the domain controller, just like W2k/XP does. So

it won't be using
>LMHOSTS or WINS for this. Slow logins usually mean

incorrect DNS settings.
>
> Does it have your local AD DNS server as its only

DNS reference?
>
>"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

>>

>
>
>.
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Ace Fekay [MVP-DS, MCT] Windows Networking 1 01-10-2010 11:08 PM
Clients can't join domain-new Primary Domain Controller installed blinton25 Windows Networking 7 06-23-2008 09:58 PM
Domain Controller Omar Abid Windows Networking 4 07-15-2007 02:08 PM
Server 2003 Standard - Cannot browse domain with domain controller! davidw@dwynn.demon.co.uk Windows Networking 2 04-12-2006 04:28 PM
Moving a domain 2003 domain controller to a different subnet John zhang Windows Networking 1 07-27-2004 01:41 PM



1 2 3 4 5 6 7 8 9 10 11