Re: sbs2003 to (new)server2003 user issue



Hello BrianMultiLanguage,

see inline

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

Here's so far.
Play by play.
1. sbs2003 network. Laptop not/never part of the domain.
2. user name/password on sbs domain match user/password on laptop.

will not work like i wrote you, because of the SID.

3. laptop in ou under SBS.
4. sbs server dead sunday night.
5. 2 new dc created, server03 std, monday. same domain name.

Even if you use the same domain name, you have built a NEW domain with a NEW Domain SID, that the client doesn't know and is not part of.

6. laptop can not see the network shares on the dc's nor can it attach
to
exchange via outlook.

Because of the new domain SID.

7. laptop user has domain admin rights because he is. (this is always,
never
changed)
8. can not map drives with user or admin account/password.
9. can not add laptop to domain. ERROR access denied using rights from
#8.
10. laptop user can see other servers in the domain AND if prompted
for
logon, domain\user and password works showing server, shares, etc.
11. laptop has never been on any domain just workgroup.
12. renamed the laptop. no change from above.
I am mentally fried from this work of disaster.
Thanks for any support.

You have built the domain totally new from scratch after the SBS was crashed. That means all user accounts, workstation names etc. are gone from the domain and the access rights are deleted. Even if you choose the same names ( domain, server, workstation and users), it will NOT work, because the credentials on the workstation did not match the domain security.

The easiest way to get access to domain shares, exchange and all other will be, to add the workstation to the domain and work with user accounts created in Active Directory, via Active directory Users and computers.
"Meinolf Weber" wrote:

Hello BrianMultiLanguage,

If you work over RDP to the SBS it will work on that way. What do you
mean with AD does not see it? If you add the workstation to the
domain it will appear in AD in the user container, otherwise it is
not added to the domain. How did you add it?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
Correct. Not part of the domain.
In the sbs versions, all I needed was to make sure my name and
password
account was on the domain.
No adding the pc in AD did not change, AD does not see it. Still can
not attacthto shares.
"Meinolf Weber" wrote:

Hello BrianMultiLanguage,

Your first post stated:

A users laptop is not part of the domain ???

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
add the computer and the account should work.
OK. Looks like it already is but I'll delete it and readd it.
Thanks.
I'll post back.
"Meinolf Weber" wrote:
Hello BrianMultiLanguage,

Even if the account in the domain and the local account on the
computer are written the same, BUT there is no relationship
between them. The have a different SID and will authenticate
either on the domain via RDP which works, because of logging in
to the domain server, not local on the computer or on the local
computer and this account has no rights to the server shares. So
add the computer to the domain and work with the domain user
account.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
A users laptop is not part of the domain but their login name
and
password on
their laptop match their account name in AD.
Since switching from sbs to server this weekend the user can not
resolve the
email server to their name, can not add network shares from
servers,
BUT can
remote desktop to the same servers with thier domain\name
password
logon.
I reset the password just in case but that did not fix it. I am
stuck.


.



Relevant Pages

  • Re: sbs2003 to (new)server2003 user issue
    ... You have not just add the "name" to ADUC, rightclick My Computer icon on the desktop, choose properties, go to network identification tab, here click properties and choose under Member of "Domain", fill in the domain name and a window will open asking you for an account from the domain with the password. ... This posting is provided "AS IS" with no warranties, and confers no rights. ... Laptop not/never part of the domain. ... sbs server dead sunday night. ...
    (microsoft.public.windows.server.active_directory)
  • Re: assign permissions from the domain
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... "Meinolf Weber" wrote: ... Both server have static IPs however the standard server has the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Please help refresh my memory on AD DC
    ... "Meinolf Weber" wrote: ... They however cannot logon directly to the physical DC machine. ... NOT an admin account to be able to Login so I can control it from ... A Server has websites already hosted on it in a Workgroup and now ...
    (microsoft.public.windows.server.active_directory)
  • Re: sbs2003 to (new)server2003 user issue
    ... If you work over RDP to the SBS it will work on that way. ... "Meinolf Weber" wrote: ... Even if the account in the domain and the local account on the ... account has no rights to the server shares. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Change IP Address of Windows 2000 Domain Controller
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... only reply to Newsgroups ... "Meinolf Weber" wrote: ... DNS server? ...
    (microsoft.public.windows.server.active_directory)