XP PRO on 2003 Domain

I am having weird issues. Users that loose connection to shares. They will
work fine for a while but just quit for no reason. The share is visable but
when you attempt to open it the local machine just hangs for a long time
then may return a error that the user does not have access to the share.
Rebooting the xp machine fixes it for a while.

New computers are added to the domain and then a user logs on to the domain.
A share is mapped and then a error says the user does not have permisson.
Rebooting several times (up to 5) will eventually allow the user to connect
to the share.

Also is there a setting (maybe group policy) on server that will allow local
machine users to change their power settings? Domain users cannot change
their power setting on the local machine and when you sign in as
addministrator on the local machine you cannot always see the domain to bring
the domain user into the power users group on the local machine.

Extremely slow log ons, even when the priamry dns server is set to the
domain controller ip address.









Tom

Do you have an internal DNS? Any errors when using nslookup?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Tom" <(E-Mail Removed)> wrote in message news:EE4F479A-297E-43D3-8B76-(E-Mail Removed)...
I am having weird issues. Users that loose connection to shares. They will
work fine for a while but just quit for no reason. The share is visable but
when you attempt to open it the local machine just hangs for a long time
then may return a error that the user does not have access to the share.
Rebooting the xp machine fixes it for a while.

New computers are added to the domain and then a user logs on to the domain.
A share is mapped and then a error says the user does not have permisson.
Rebooting several times (up to 5) will eventually allow the user to connect
to the share.

Also is there a setting (maybe group policy) on server that will allow local
machine users to change their power settings? Domain users cannot change
their power setting on the local machine and when you sign in as
addministrator on the local machine you cannot always see the domain to bring
the domain user into the power users group on the local machine.

Extremely slow log ons, even when the priamry dns server is set to the
domain controller ip address.

"Tom" <(E-Mail Removed)> wrote in message
news:EE4F479A-297E-43D3-8B76-(E-Mail Removed)...
>I am having weird issues. Users that loose connection to shares. They
>will
> work fine for a while but just quit for no reason. The share is visable
> but
> when you attempt to open it the local machine just hangs for a long time
> then may return a error that the user does not have access to the share.
> Rebooting the xp machine fixes it for a while.
>
> New computers are added to the domain and then a user logs on to the
> domain.
> A share is mapped and then a error says the user does not have permisson.
> Rebooting several times (up to 5) will eventually allow the user to
> connect
> to the share.
>
> Also is there a setting (maybe group policy) on server that will allow
> local
> machine users to change their power settings? Domain users cannot change
> their power setting on the local machine and when you sign in as
> addministrator on the local machine you cannot always see the domain to
> bring
> the domain user into the power users group on the local machine.
>
> Extremely slow log ons, even when the priamry dns server is set to the
> domain controller ip address.
>
1. All servers and workstations should specify *only* the internal (usually
AD-integrated) DNS server's IP address in their network settings. No public
DNS server IPs should be 'seen' by servers or clients in their ipconfig /all
settings. The DNS server should be set up with forwarders to your ISP's DNS
servers (and use root hints) for external resolution.
>
2. Re GPO, not sure, but you might post this in
microsoft.public.windows.group_policy. I've usually gotten round this by
temporarily granting the domain user local admin rights, changing the power
settings then, and then revoking the local admin permissions.




>
>
>
>