no domain controller is available to authenticate you...

I figured out a work around to the problem that works...
All I had to do is configure the 2003 DC to use WINS, and
enabled NetBIOS over TCP/IP. Once they registered
themselves in the WINs database the 98 clients could
authenticate across different networks.

My question to you, is there a different DS client for
Win 2003? I mean the DS client we have installed on all
the 98 machines is off the Win 2000 server disk... Is
there an updated version for Win 2003?

If not, why was I unable to connect... The 98
workstations are all setup with the DNS addresses of our
two Win 2003 DC... Yet they could not find them from any
network other that the network the DC are on... We are
using multiple DNS zones, might that have something to do
with it?

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
>>
>
>
>.
>
..