Issues with WinXP Pro and Win2003 server computers in a W2K SBS domain.

  • Thread starter Thread starter Vitalik
  • Start date Start date
V

Vitalik

Hello there,

We have recently introduced 2 WinXP Pro (SP1&2) computers and 3 Win2003
Servers to our W2K Small Business Server domain and have 2 issues.

The 1st problem applies to all new computers and is that new computers after
some period of time (XP after~1-3 hours and W2K3 after ~24 hours) loose
local network connectivity and cannot see mapped drives that point to either
AD controller (only one on the network) or some other computers (with W2K
Pro). People who work on the XP computers have to type in userid/password
in the popup box before access is restored, but sometimes need to reboot in
order to get network connectivity back. For the W2K3 servers the current
solution is to type in passwords from screen saver in the morning and that's
enough to keep them up for a day.

Second problem is only with the new servers, where we cannot add domain
users/groups to local groups on those computers like we can do on any W2K
Pro and WinNT4 computers. This forces us to use Everyone group when we want
to make a folder or drive shared on the network. When adding a resource,
the dialog box only allows to pick from local computer and domain name is
not even available.
If this will help, I'd like to mention that all the new servers came with
preinstalled OS (we just finished the installation) and we didn't change any
of the default settings.

The rest of the computers is W2K Pro SP4 and some Win NT4 SP6a and none have
any issues described above.

Thanks for any help.

Vitaliy
 
Have you joined the new member servers to the domain? They will need to be joined to the domain before domain accounts can be added to them, or a trust is created with whatever domain they belong to.

--
Tony Eversole MCSE, MCSA, Net+, A+
Hello there,

We have recently introduced 2 WinXP Pro (SP1&2) computers and 3 Win2003
Servers to our W2K Small Business Server domain and have 2 issues.

The 1st problem applies to all new computers and is that new computers after
some period of time (XP after~1-3 hours and W2K3 after ~24 hours) loose
local network connectivity and cannot see mapped drives that point to either
AD controller (only one on the network) or some other computers (with W2K
Pro). People who work on the XP computers have to type in userid/password
in the popup box before access is restored, but sometimes need to reboot in
order to get network connectivity back. For the W2K3 servers the current
solution is to type in passwords from screen saver in the morning and that's
enough to keep them up for a day.

Second problem is only with the new servers, where we cannot add domain
users/groups to local groups on those computers like we can do on any W2K
Pro and WinNT4 computers. This forces us to use Everyone group when we want
to make a folder or drive shared on the network. When adding a resource,
the dialog box only allows to pick from local computer and domain name is
not even available.
If this will help, I'd like to mention that all the new servers came with
preinstalled OS (we just finished the installation) and we didn't change any
of the default settings.

The rest of the computers is W2K Pro SP4 and some Win NT4 SP6a and none have
any issues described above.

Thanks for any help.

Vitaliy
 
Thanks Tony for your response.

Well, from what I can see, it seems that the computers are members of the domain (we used the same procedure we used before for other computers, since we use W2K SBS and needed to create computer account on DC first). I can see them in My Network Places > Entire Network > Ms Windows Network (or Directory) and can see/open files in shared folders. Is there anything else, I can do to make sure everything is ok? If you can be more specific it would be greatly appreciated.

Thanks,
Vitaliy

Have you joined the new member servers to the domain? They will need to be joined to the domain before domain accounts can be added to them, or a trust is created with whatever domain they belong to.

--
Tony Eversole MCSE, MCSA, Net+, A+
Hello there,

We have recently introduced 2 WinXP Pro (SP1&2) computers and 3 Win2003
Servers to our W2K Small Business Server domain and have 2 issues.

The 1st problem applies to all new computers and is that new computers after
some period of time (XP after~1-3 hours and W2K3 after ~24 hours) loose
local network connectivity and cannot see mapped drives that point to either
AD controller (only one on the network) or some other computers (with W2K
Pro). People who work on the XP computers have to type in userid/password
in the popup box before access is restored, but sometimes need to reboot in
order to get network connectivity back. For the W2K3 servers the current
solution is to type in passwords from screen saver in the morning and that's
enough to keep them up for a day.

Second problem is only with the new servers, where we cannot add domain
users/groups to local groups on those computers like we can do on any W2K
Pro and WinNT4 computers. This forces us to use Everyone group when we want
to make a folder or drive shared on the network. When adding a resource,
the dialog box only allows to pick from local computer and domain name is
not even available.
If this will help, I'd like to mention that all the new servers came with
preinstalled OS (we just finished the installation) and we didn't change any
of the default settings.

The rest of the computers is W2K Pro SP4 and some Win NT4 SP6a and none have
any issues described above.

Thanks for any help.

Vitaliy
 
Delete the computer from AD. and use the "wizard" as much as i hate to say it... the wizard seems to help out on getting the correct sid to the AD and everything. just adding the computer name will not all the computer to be joined to the domain because the computer/server information is not proper in the sam data base.

right click my computer and go to properties.
click computer name and click network id. and just follow from there. I alway enter the admin acout information all the way through.

username admin
password *********
domain yourdomain.com (used in AD wiht DNS) or domainname

computer name
domain

then will ask you for the account that has rights to add computer/servers to the domain.

that should add the computer to the domain with no issues. Make sure that you delete the old computer name from AD first or else you will receive an error that the computer name exist. and if you run 2 AD controllers ie backup then make sure that it is deleted form both, connect to both if you don't want to wait for a sync and remove the computer name. then should be safe to join to the domain with no issues and would be ablt to see the domain from the login.

and last thing that i just thought about.... make sure you are logging into the domain and not the local computer as the servers may not talk from local admin to domain admin even with same username/password like in 98 to NT servers.
Thanks Tony for your response.

Well, from what I can see, it seems that the computers are members of the domain (we used the same procedure we used before for other computers, since we use W2K SBS and needed to create computer account on DC first). I can see them in My Network Places > Entire Network > Ms Windows Network (or Directory) and can see/open files in shared folders. Is there anything else, I can do to make sure everything is ok? If you can be more specific it would be greatly appreciated.

Thanks,
Vitaliy

Have you joined the new member servers to the domain? They will need to be joined to the domain before domain accounts can be added to them, or a trust is created with whatever domain they belong to.

--
Tony Eversole MCSE, MCSA, Net+, A+
Hello there,

We have recently introduced 2 WinXP Pro (SP1&2) computers and 3 Win2003
Servers to our W2K Small Business Server domain and have 2 issues.

The 1st problem applies to all new computers and is that new computers after
some period of time (XP after~1-3 hours and W2K3 after ~24 hours) loose
local network connectivity and cannot see mapped drives that point to either
AD controller (only one on the network) or some other computers (with W2K
Pro). People who work on the XP computers have to type in userid/password
in the popup box before access is restored, but sometimes need to reboot in
order to get network connectivity back. For the W2K3 servers the current
solution is to type in passwords from screen saver in the morning and that's
enough to keep them up for a day.

Second problem is only with the new servers, where we cannot add domain
users/groups to local groups on those computers like we can do on any W2K
Pro and WinNT4 computers. This forces us to use Everyone group when we want
to make a folder or drive shared on the network. When adding a resource,
the dialog box only allows to pick from local computer and domain name is
not even available.
If this will help, I'd like to mention that all the new servers came with
preinstalled OS (we just finished the installation) and we didn't change any
of the default settings.

The rest of the computers is W2K Pro SP4 and some Win NT4 SP6a and none have
any issues described above.

Thanks for any help.

Vitaliy
 
Back
Top