Anybody have any idea what's going on?
check FSMO roles are ok from the DC: netdom query fsmo
On the workstation, check that:
-Date & Time are the same as the domain (closer than 5 mn)
-It has the DC as primary dns server
-you try to join the domain with the FQDN name (mydomain.com)
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr
"DaDuck" <DaD...@discussions.microsoft.com> wrote in message
news:36373453-5B9B-4668...@microsoft.com...
You may experience network-related problems after you install Windows Server
2003 SP2 or the Scalable Networking Pack
http://support.microsoft.com/kb/936594
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr
"DaDuck" <DaD...@discussions.microsoft.com> wrote in message
news:36373453-5B9B-4668...@microsoft.com...
>
Post the ipconfig /all from your client and your dns server.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"DaDuck" <DaD...@discussions.microsoft.com> wrote in message
news:36373453-5B9B-4668...@microsoft.com...
>
I read this thread and tried everything. The DC names are correct; All
possible updates are installed and tried. I tried different nwtwork
cards (desperate).
The x64 box gets to the username/password dialog and then pauses about
1 minute after entry. The I either get the same message as above or an
access denied message.
Oddly, ONE time when I changed computer names on the XP x84 client, did
NOT reboot and attempted a domain login. I got a "Welcome to the domain
message" followed by a message which told me that the name has reverted
to the old name of the computer (or something like that).
What accompanies this error is the server disabling the computer
account after this error occurs.
I have tried changing client names, different boxes, different NICs,
and am considering a small hammer if I can't get this to work. HELP
please!
Thanks in advance.
--
Photomanliny
------------------------------------------------------------------------
Photomanliny's Profile: http://forums.techarena.in/members/photomanliny.htm
View this thread: http://forums.techarena.in/active-directory/837472.htm
1. Delete Comp. Acct. in AD User's & Computers on controller.
2. Wait 5 minutes.
3. manually set DNS to AD server on workstation.
4. Renamed local Administrator to Administrator
5. Re-added, using my domain ID (as domain admin)
not sure which one was the key step, but that's all of them.
--
ScottR
------------------------------------------------------------------------
ScottR's Profile: http://forums.techarena.in/members/scottr.htm
I am having the same issues with joining winXP clients to 2008 server
after having been on a 2000 domain. Did you figure out what the
problem was?
--
Petrus4
------------------------------------------------------------------------
Petrus4's Profile: http://forums.techarena.in/members/126349.htm
Then, I put the IP address of my domain controller into the preferred
DNS area of the IP settings in my network connections.
--
Josh12984576
------------------------------------------------------------------------
Josh12984576's Profile: http://forums.techarena.in/members/134974.htm
I didn't go back to see the whole thread, since all we see in the Microsoft
Newsgroups (where Techarena posts and pulls posts from), is just this post
and Petrus4's post, but what I can say, if your machines, that is all
machines (DCs, member servers, TS, client machines, etc) have any other DNS
address in their IP properties other than the internal DNS that hosts the AD
zone, then I can understand why you are having problems.
ISA complicates things as well.
Other scenarios that will cause this issue:
Multihomed DCs (more than one NIC and/or IP address) as well as RRAS
installed on any of the DCs.
AD DNS Single Label Name domain name ("domain" vs the minimal requirement of
"domain.something").
Third party firewalls installed on the DCs or clients.
Third party security and/or AV software that is misconfigured and blocking
necessary ports or apps.
Improper routing (whether within the infrastructure, VLANs misconfigured, or
using VM).
Ace
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
I tried turning off the firewall on the Vista machine.
Adding only the DC IP address for the Vista DNS.
I flushed DNS and registered.
I activated the Administrator account and tried joining the domain.
I also tried to join using different domain admin accounts.
The weird thing is that I can join the domain just fine with an XP PC (in fact it was an XP install on a Mac!).
I get the same account creation and disable when I join using the Vista machine.
The time on both are the same (as well as the date!).
They are both on the same LAN (so no routing/VLAN issues).
Now I think I have covered all the possible suggestions so if anyone has any other ideas please let me know.
BTW I searched the event logs of the Vista machine AND the server and NOTHING is logged that has any relevance to this error. Another annoyance....
Ace Fekay [MCT] wrote:
Re: Specified server cannot perform requested operation - joining domain
13-Sep-09
"Josh12984576" <Josh12984...@DoNotSpam.com> wrote in message
news:Josh12984...@DoNotSpam.com...
I didn't go back to see the whole thread, since all we see in the Microsoft
Ace
--
Ace
EggHeadCafe - Software Developer Portal of Choice
Using Reflection to Create a Data Access Class
http://www.eggheadcafe.com/tutorials/aspnet/0763b128-4bf4-4d12-8892-134b46b44f20/using-reflection-to-creat.aspx
Dan,
The big question is how you are attempting to join it to the domain? Are you
using the NetBIOS name ("domain")? Or are you using the FQDN (domain.net,
domain.local, etc)? Vista does things a little differently when it comes to
the DNS client-resolution process.
Is the DC multihomed, or does it have RRAS installed on it? If so, when the
client queries DNS for a DC in the domain, it may be getting the outside IP
or one of the RRAS IPs, which the client machine cannot connect to.
You stated you added only the DC as DNS. Was it configured differently prior
to that, such as using an ISP, the router or some other exernal DNS?
Is the DC only using itself as DNS (if one DC), or itself, then a partner DC
as the second entry (recommended)?
Any errors on the DC?
Ace
--
kenmay
------------------------------------------------------------------------
kenmay's Profile: http://forums.techarena.in/members/173183.htm
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"kenmay" <kenmay...@DoNotSpam.com> wrote in message
news:kenmay...@DoNotSpam.com...
If the Client cannot Join the domain but can ping the server ok, this
either that the name already exist within DC/AD or....Windows
Firewall/other firewall is blocking it!
So....
delete computer from DC/AD restart both client and server (so server has
a chance to realise it is no longer there, then disable firewalls on
BOTH CLIENT AND SERVER.
And finally join the domain!
If this does not work, reinstall client and delegate it with a new PC
Name.
--
scubied
------------------------------------------------------------------------
scubied's Profile: http://forums.techarena.in/members/195250.htm