Can not connect to the domain - seacon

Similar Threads:

1.can not c any computer in network place - seacon

I can not locate any computer in the network place, my domain name is 
displayed but dont show any computers.i tryied to accses computers useing 
below methods and failed. this machine is the DC.
1.  Run - \\computer name
2 . tryied to map a network drive, it shows my domain name nothing else I 
can select or displayed.

From other machine I can connect to this machine and can map driver which is 
on Domain controler.
DC can access internet. other machines can not. they can ping to the DC but 
can not ping the router.
they can access resources in the DC


pls help me to sole this matter

2.cans' move a computer account to a new OU within same domain

I don't understand why this does not work, I took this straight from the 
technet script repository and amended it to my domain. I am signed on as the 
domain admin when I run this script. Why does it not work?

I want o move a computer account from the default container, "computers" to 
a more suitable OU, that being "userComps", an OU directly in the root of the 
domain.

Please help!

Set objNewOU = GetObject("LDAP://OU=userComps,DC=daniel-ct,DC=co,DC=uk")

Set objMoveComputer = objNewOU.MoveHere _
    ("LDAP://CN=daniel-pjr0vps7,CN=Computers,DC=daniel-ct,DC=co,DC=uk", 
"CN=daniel-pjr0vps7")

3.Vista trying to connect to domain when not connected

I am using Vista Enterprise which is setup by my corporation and I don't 
have access to all settings, some might be related to group policies 
etc. It is using a "roaming profile".

When I am home (connected to internet but not to my domain) Vista 
sometimes try to connect to the domain, for example when I open a file 
open/save dialog causing computer to stop responding for a while which 
is very annoying. 

Is there any way to avoid this problem other than using a local account 
when I am at home (which I don't like because of having to duplicate 
settings etc). Any magical setting to make it understand that I am not 
connected to doamin and to stop trying. 

Magnus

4.error - Windows can not connect to the domain...domain controller

#1
Briefly here's the sequence:
- Running SBS2003 network
- Client machine is wireless laptop running XP Pro
- Want to connect this client to network
- Set up client computer account on server
- Set up user account on server
- ran \connectComputer on client - I logged in as network administrator
- Migrated user profile to maintain the users settings
- no errors in this process
- On reboot can only login locally as user, not to domain
- When I try to login to the domain (which shows up as an option) using the 
login name of the user account as set up on server I get the error msg:
"Windows can not connect to the domain either because the domain controller 
is down or otherwise unavailable, or because your computer account was not 
found...."

I checked computer account on server
Properties of client computer show nothing for the DNS name

Question: Should I just rerun  \connectComputer or should I delete the 
computer and user accounts, recreate them and the run \connectComputer?

#2 - Also, when setting up the client account on the server/client 
applications page, if the client has Office 2003 installed and is updated do 
I need to check IE6 and Outlook 2003? or have checked the "During Client 
Setup, allow the selected applications to be modified"?  I'm not sure of the 
relationships here and what's going on in the background.


I'd appreciate a shove in the right direction - ... many thanks!
-- 
Tom Mc

5.error - Windows can not connect to the domain...domain control

6. 'canned' script from scriptcenter works on W2k3 but not W2k

7. Cannot use a domain logon when not connected to domain

8. Connect machine to domain when the domain is not accessible