We help IT Professionals succeed at work.

Preferred Server on NT

drodrigu
drodrigu asked
on
Medium Priority
259 Views
Last Modified: 2013-12-23
I know that the nearest Primary Domain Controller or Backup Domain
Controller is who validate you, but in some time it isn't true.
The question: Is there a form that I can force that a Win95
workstation be validate for a especific Server like in Novell that exist
a Preferred Server variable in the Net.cfg
Comment
Watch Question

Author

Commented:
Edited text of question

Commented:
If you are using Microsoft Networks you can enter the master browser via the Advanced settings.

However, if you are referring to logons it shouldn't matter which DC validates you.
Also, its not necessarily the nearest DC that validates logons.

Author

Commented:

Commented:
No specific way to choose your domain controller on login, I believe, the authentication model doesn't work that way -- but there's hope;  you can take a single server (if it's important enough to you to do so) and put it into it's own domain -- a "resource domain" with trusts operating between it and the other domains to ensure access to the existing network shares yo need.  This single server  will of course be the PDC of that resource domain, and if your W95 workstation specifies the "resource domain" (and you've added him to the domain via user manager, of course) your login could be quite swift, depending on the configuration & whatever else you're running on that machine.   This also adds an additional level of security refinement as to what you can share, and to whom, but it can also be made pretty transparent if you wish.  Look up "Multiple Resource Domain Model" in the NTS planning docs.

Author

Commented:
Look, We have like 12 Servers distributed among WAN'S links
and is important to have a BDC in each state (You Know, for
logon validation be more quickly and distributed) and to have
backups of the DataBase. Maybe my question was not be very
especific.

I'm going to tell you what is my plan:
The login script of server B for the userX has connection to that
server B.

If server B is having problems the userX could validate for other
Server C and that login script for the userX has connection to
that server C.
This Server B and C are syncronize their data.

I want that the server who validate me have a script that make
connection to hisself.. but if I do that and a Server that is not
the primary for the user validat me what happens?....

How I am now:
The script for userX is the same in all Servers (That's the way
a resolve the problem no matter what server validate you). But
if the script make connection to a Server that is down What's
happens........ I need to modify or have a backup of different
scripts....
Commented:
There is no obvious way to solve this.

What i would do as a workaround is something like this:

[login script for Xserver users]
rem Xserver is the preferred server
net use h: \\xserver\apps /y
if errorlevel 0 goto done
rem Yserver is first failover server
net use h: \\yserver\apps /y
if errorlevel 0 goto done
rem Zserver is second......
net use h: \\zserver\apps /y
if errorlevel 0 goto done
........
:done

I use the net use/errorlevel myself for a slow link, where the first two or three net use might time out:

:oncemore
net use x: \\farawayserver\importantshare
if errorlevel 1 goto oncemore


Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.