no domain controler is available to authenticate you...

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

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
>

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