HELP with "NO DOMAIN CONTROLLER WAS AVAILABLE..." error.

[jea...@nospam.lansol.com]

HELP...

We have a small NT network (1 PDC) with 3 Win95, 2 NT workstation. It
worked fine for the last 8 month. It worked fine this morning. If
anyone logged out and when they try to log back in, they get "NO
DOMAIN CONTROLLER WAS AVAILABLE TO VALIDATE YOUR PASSWORD". If the
workstation stayed logged in, they had no problem accessing the
server, but once they logged out, they "cannot find the domain
controller..." again.

The only thing we did today is plugged in our old Novell Netware 3.12
server on the network to get some files, but once we were done, we
shut the Novell server off and left it off.

PLEASE HELP.... I looked in the Event Log and there was no errors.

Where should I start to trouble shoot this?

** Please remove "NOSPAM" for e-mail replies.

[Gerhard Stockinger 4SYSTEMS]

If you use NWLINK IPX/SPX you should set the FrameType to Ethernet 802.2,
Perhaps Autodetection won't work with Novell Servers. If the workstations
find another FrameType because of the Novell Server no Domain Controller
will be found.......

GS

jea...@NOSPAM.lansol.com schrieb:

[jea...@nospam.lansol.com]

Thanks for the reply. The Novell server is not turned on... is not
even connected to the network any more.

[li...@nospam.lansol.com]

Hi,

We have a NT network w/one PDC, NT4.0 workstations and Win95/98
workstations. One printer attached to the PDC and one printer
attached to a NT4.0 Workstation.

Can someone tell me why our Win95/98 Workstations cannot "see" or
attach to the printer connected to the NT Workstation 4.0? But It
prints to the PDC printer just fine.

With our NT workstations, there is no problems printing or "seeing"
both printers!

What's the difference between NT and Win95/98 workstations? What am I
missing?

Thanks for your help in advance.

[Tony Northrup]

This is a NetBIOS name resolution problem. Troubleshooting it will depend
on how you resolve NetBIOS names. I'm assuming you're on a LAN and aren't
relying on WINS or LMHOSTS to resolve names.

For some reason, your primary domain controller is not responding on the
network when clients send a broadcast message looking for the PDC. Try
rebooting the PDC and seeing if that helps. If that doesn't help, you'll
need to do more in-depth troubleshooting of the problem. For that, I'd
refer you to chapters 8 and 10 of my book 'NT Network Plumbing', which
shows you how to troubleshoot NetBIOS name resolution problems. Good luck.

| Tony Northrup, MCSE, Compaq ASE
| Author, NT Network Plumbing, available at:
| http://www.amazon.com/exec/obidos/ASIN/076453209X/002-1782677-8866026

jea...@NOSPAM.lansol.com wrote:
>
> HELP...
>
> We have a small NT network (1 PDC) with 3 Win95, 2 NT workstation. It
> worked fine for the last 8 month. It worked fine this morning. If
> anyone logged out and when they try to log back in, they get "NO
> DOMAIN CONTROLLER WAS AVAILABLE TO VALIDATE YOUR PASSWORD". If the
> workstation stayed logged in, they had no problem accessing the
> server, but once they logged out, they "cannot find the domain
> controller..." again.
>
> The only thing we did today is plugged in our old Novell Netware 3.12
> server on the network to get some files, but once we were done, we
> shut the Novell server off and left it off.
>
> PLEASE HELP.... I looked in the Event Log and there was no errors.
>
> Where should I start to trouble shoot this?
>

> ** Please remove "NOSPAM" for e-mail replies.

[Jim Anderson]

On our mixture of win95 and nt4.0 workstations we found that there is
a limit to the length of the printer name that win 95 can see that
doesn't bother the nt workstations. I don't remember the max length
exactly but try changing to eight to start if you are using long
printer names. The max is longer than that I think but not much. We
found that xxxxx_lj4si_1 was too long fot the win 95's.

Jim

[Randy Owens]

Any spaces in the printer names?

[Carl Cox]

Use max 11 characters, no spaces for shares to be visible to "downlevel"
clients (DOS, WfW, Win 9x).

--
Carl Cox
Systems Support Engineer
Applied Retail Solutions, Inc.
The opinions expressed are my own, not those of my employer.

Randy Owens wrote in message <365b3a12....@news.itron.com>...

[li...@nospam.lansol.com]

Thats IT! It was the printer name. I had "EPSON STYLUS" as the name
and when I change it to "EPSON", it worked!

Thanks!!!

On Tue, 24 Nov 1998 22:58:56 GMT, ran...@uts.itron.com (Randy Owens)
wrote:

[chr...@my-dejanews.com]

Check your services to make sure they are all running like they should be.
Sounds like your server lost a service.

In article <365a5c5...@news.flashcom.com>,

jea...@NOSPAM.lansol.com wrote:
> HELP...
>
> We have a small NT network (1 PDC) with 3 Win95, 2 NT workstation. It
> worked fine for the last 8 month. It worked fine this morning. If
> anyone logged out and when they try to log back in, they get "NO
> DOMAIN CONTROLLER WAS AVAILABLE TO VALIDATE YOUR PASSWORD". If the
> workstation stayed logged in, they had no problem accessing the
> server, but once they logged out, they "cannot find the domain
> controller..." again.
>
> The only thing we did today is plugged in our old Novell Netware 3.12
> server on the network to get some files, but once we were done, we
> shut the Novell server off and left it off.
>
> PLEASE HELP.... I looked in the Event Log and there was no errors.
>
> Where should I start to trouble shoot this?
>

> ** Please remove "NOSPAM" for e-mail replies.
>

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[Surfer]

Start by restarting the PDC.

--
Surfer!
http://www.nevis-vieww.demon.co.uk
http://www.nevis-vieww.demon.co.uk/flash
Hopeful anti-spam: alter double 'w' to single 'w' to view site & send Email.