Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

logon hangs at applying personal settings


  • Please log in to reply

#16
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
Yes. new ones that come with xp pro and the other computers that had xp pro already on them do not experience this lag.
  • 0

Advertisements


#17
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
Yes. the new computers that come with Pro on them and the other ones that had pro already on them do not experience this lag
  • 0

#18
amw_drizz

amw_drizz

    Member

  • Member
  • PipPipPip
  • 329 posts
do you have any other AD servers in your domain forest?
  • 0

#19
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
I just added another DC in the domain. It is used strictly to run our Accounting Program, but it is a DC
  • 0

#20
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
why is it a dc? if all it's doing is running the accounting program?
  • 0

#21
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
I set it up that way so that I didn't have to enter the users in the local user database. Everyone uses this server so I would have had to put everyone as a user in it. It was easier to make it a DC. The reason everyone uses it is because our timesheet is done throught this program

Edited by ehosto, 03 March 2006 - 09:11 AM.

  • 0

#22
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
if you've got a full active directory structure....you would have just needed it to be a member server...not a dc at all...they still would have been able to log on as users and everything else..because AD would be controlling authentication....not the server...no one should be logging on with local accounts in an ad domain
  • 0

#23
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
I tried it as a member server and no one could logon to the machine without credentials.
  • 0

#24
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
huh...well..however it's set up i gues...heheh...if it's a dc...then it's got to be doing replication with the pdc....how is the wins replication set up on both machines?
  • 0

#25
ehosto

ehosto

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
WINS is only running on the pdc.
  • 0

Advertisements


#26
Amdy

Amdy

    New Member

  • Member
  • Pip
  • 1 posts
Active directory uses DNS - not wins. Wins was used for NT Domains and should be discarded once you have an Active Directory environment.
The other server you made into a DC should have been a member server under the current AD Domain. If users couldnt get to that server, your server wasnt in the domain correctly.

As for the upgraded machines taking an unusual amount of time applying computer settings, its probably a SID issue, you may have to move the computer accounts into the same OU as the user accounts. How did you structure your AD environment? Ideally you want the user and computer accounts in the same OU so you can apply computer and user group policies

Andy
  • 0

#27
scottsonline

scottsonline

    New Member

  • Member
  • Pip
  • 2 posts
I have exactly the same problem. I am running a SBS 2003 with 6GB RAM. Clients in the small LAN are mixed XP Pro and Vista. All machines have a delay and hang logging on and off. The Vista machines are particularly bad. I have done all the obvious checks, local RAM, spyware etc and all systems are healthy. There appears to be a DNS problem. For some reason clients are using 194.72.9.34 and 194.72.9.38. The server is using 192.168.16.2. However....when I changed a client PC to match the server DNS the log on was no quicker and the internet was painfully slow. I hope that someone can advise:

1. Is the DNS set up incorrect?
2. Is this causing the slow log ons?
3. Whats the correct settings for DNS, DHCP?

Thanks!!!
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP