HELP: Inter-Domain administring problems..
Tim
Two domains in the main office (headquarters) en 16 in remote places
(Shops).
The two domains at the main office are called Unique and Multi_Services.
Problem:
At first I was able to administer the entire network throught both Unique
and Multi_Services. Then suddenly some shops started to give errors when I
administered a remote domain through Multi_Services, I got the message: "No
servers available to service te logon request", when I wanted to add a user
in a usergroup from the Multi_Services domain.
As a work arround I logged on on Unique, here everything worked fine. I
tried to find to what the problem was, but with no luck so far.
Now the same problems start to happen form the Unique domain.
I deperate, looked everywhere I know
Please Help!
Protocol : TCP/IP
All the PDC's have WINS and DHCP installed.
All the Domain are configured for a complete trust.
All WINS servers are configured to replicate their databases with a central
WINS server which is located in the Multi_Services Domain.
Thanx in advance for reading this message.
Regards,
Tim van Dijk
Unique International N.V.
the Netherlands
Di...@Connect-Systems.Com
Robert_Proffitt
the Service Pack was not the same on our servers.
My lesson was to keep the servers all at the same SP and bits.
Bob
Tim <T...@Unique.nl> wrote in message news:7r5lvk$fl3$1...@news.worldonline.nl...
Tim Monkman
bit or 40 bit. I worked with MS Support for a couple of weeks with no luck.
The fix I stumbled on was to put a lmhosts file in the
c:\winnt\system32\drivers\etc directory with entries for all
servers/machines in both domains, then all went well from. Never a problem
again. There is a lmhosts.sam (sample file) in this directory for reference.
Remember the lmhosts file has no file extension. Basically it is a plain
file you create with notepad as follows:
IP Address Machine name(uppercase) #PRE #DOM:domain
name(uppercase)
207.254.136.15 SERVER1 #PRE #DOM:UNIQUE
207.254.136.16 SERVER2 #PRE #DOM:UNIQUE
You should either reboot or flush the local cached name table by using the
nbtstat -R command at the command line. This will flush this new file into
cache. Then do a resync of each domain at each PDC. Your problem should go
away. Good Luck.
--
Tim Monkman
t...@bubblehead.net
630-416-8049
Robert_Proffitt <NONSPAMRobe...@email.msn.com> wrote in message
news:eAPPk5f##GA.257@cppssbbsa04...
Jamie
Have you got the Resource Kit? If so, install Domain Monitor. This will show
all of your trusts and the connections between them.
In DM just highlight the trust(s) marked "nologonsrv) then disconnect them.
NT should renegotiate the secure channel.
There's also NETDOM, a command line thingy, but its fiddly. Might also be a
Res Kit utility.
Regards,
Jamie.
Jamie
Have you got the Resource Kit? If so, install Domain Monitor. This will show
all of your trusts and the connections between them.
In DM just highlight the trust(s) marked "nologonsrv) then disconnect them.
NT should renegotiate the secure channel.
There's also NETDOM, a command line thingy, but its fiddly. Might also be a
Res Kit utility.
Regards,
Jamie.
Tim wrote in message <7r5lvk$fl3$1...@news.worldonline.nl>...
>The following discribes our situation.
>
>Two domains in the main office (headquarters) en 16 in remote places
>(Shops).
>The two domains at the main office are called Unique and Multi_Services.
>
>Problem:
>
>At first I was able to administer the entire network throught both Unique
>and Multi_Services. Then suddenly some shops started to give errors when I
>administered a remote domain through Multi_Services, I got the message: "No
>servers available to service te logon request", when I wanted to add a user