Re: Forced client disconnect problem.

What are they being disconnected from and what error or warning message do
they get or what happens?? Look in the logs via Event Viewer of the domain
controller, the domain client, and any server they are being disconnected
from to see if any pertinent logon failure or other events are being
recorded. Make sure that auditing of logon events for success and failure is
enabled in Domain Security Policy. By default Windows 2003 servers should
have this enabled. Though it should not matter [since accounts are not
restricted] check the Local Security Policy [secpol.msc] to make sure that
Network Security: Force logoff when logon hours expire is shown as disabled.
Also when this happens see if the client computers can ping the servers by
name and IP address to see if basic network security exists or not and check
the servers to make sure that the server service is started and run the
support tool netdiag on them to see if any problems are found that may be
related. It would also be a good idea to run dcdiag and gpotool on your
domain controllers to check for their domain configuration health. The
support tools are on the install disk in the support/tools folder where you
have to run the setup program. --- Steve


"Gerry Armstrong" <gerrya@xxxxxxxxxxx> wrote in message
news:11p8tl7qtt6ni9c@xxxxxxxxxxxxxxxxxxxxx
>I have a problem with my clients being disconnected form the network at the
>same time every day that is driving me around the bend. I have set the
>Network Security: Force logoff when logon hours expire policy to Disable
>but it is still happening. I have also checked that the Logon Hours for the
>users has no time restrictions at all so they should have access to the
>network at any time of day. The domain consist of a SBS2003 server and a
>2003 Standard server both Domain controllers and 25 Windows 2000/XP Pro
>clients. Currently the SBS2003 server is only providing Exchange services
>and is not being used as a file server, the 2003 Standard server is
>providing fileservices only.
>
> Is there something I am missing here? Any suggestions as to what I should
> look for?
>
> Thanks for any input guys.
>


.

Relevant Pages

  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.exchange2000.general)
  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Network Connection
    ... For the clients make sure that you use following policy to prevent logon with cached credentials: ... Additional post an unedited ipconfig /all from the DC/DNS server and a problem machine so we can exclude DNS configuration problems. ... From last December I have been experiencing network connection problem ... out client pc some with Vista and the rest with XP. ...
    (microsoft.public.windows.server.networking)
  • Re: Slow domain logon (with detail try out)
    ... "The speed of the logon is directly related the size of the profile and the ... rather than copying the profile from the server. ... Uninstall "Client for Microsoft Network", restart, install it again ... Boot the client machine and logon (TCP/IP configured to get IP from ...
    (microsoft.public.windows.server.general)
  • Re: Still strange not fully working DNS server
    ... At logon on the network with a client the error event ID 1054 appears. ... The new server is global catalog and has joined the domain as a member, ... If the clients are domain members they have to be registered in your DNS ...
    (microsoft.public.windows.server.dns)