XP losing domain access



Recently after installing one of MS many 'security' updates, I now find
that our XP workstations can no longer access certain servers on the
domain without having to 're-login' to that particular server. I can't
quite put my finger on the timeout interval, but it appears to be
around 15 minutes or so.

The servers in question are all running Server 2003 and the
workstations are all XP-SP2. The connections are on a single backbone
and the XP firewall has been disabled. The workstation IP addresses
are assigned via DHCP and are all private. Power configuration for all
systems is Always On. Can't think of anything else which might affect
the connection. I also don't recall ever experiencing this problem
prior to the updates loaded within the last month. It isn't viable to
uninstall them at this time.

The current configuration is two domains, one 2003 with ASD and one NT4
with reciprocal trust relationships. The problem occurs within the
2003 domain - both the workstations and the servers are on the same
domain. The workstation is currently logging in using a user ID with
administrative access rights, and when the workstation first boots up
and logs in, it sees and can access the servers with no problems
through Win Explorer, My Network Places, Entire Network, Microsoft
Windows Network, XDomain, ServerA. After 15 minutes or so, clicking on
ServerA (which is still visible in the list even after refreshing)
brings a long wait, followed by a dialog window with the "Connect
as..." user ID and password prompt.

I've searched everywhere but while some topics allude to timeout
parameters, I cannot seem to locate anything which addresses this
particular problem nor how to configure a parameter short of editing
the registry.

Ideas/suggestions?

.



Relevant Pages

  • Re: Cisco Aironet 1200 Series - optimization question
    ... Windoze and anti-virus updates, and cloggs the network for about 15-30 ... see what's actually moving on the wireless link. ... Bittorrent servers running on corporate LAN's and users watching ...
    (alt.internet.wireless)
  • Re: Network slow after 2nd DC
    ... You can consider this a new network. ... It is the only DC running DNS and DHCP ... All servers have fixed IP's ... every hour for the last 3 hours because the updates did not change the ...
    (microsoft.public.windows.server.active_directory)
  • Slow Network Access
    ... servers, 5 working workstations and about 4 test workstations. ... runs on a 100base network with serval switches through out the office. ... Some michines work fine others have problems. ...
    (microsoft.public.win2000.networking)
  • Slow network browsing after original NT4 PDC removed from W2K network
    ... I have a network built originally around a single WinNT 4 ... Primary Domain controller and 15 Windows 2000 Pro ... Servers all configured as Domain Controllers and running ... workstations, and switches, and then restarting it without ...
    (microsoft.public.win2000.networking)
  • RE: Optimize SMB on server to accomodate slow WAN link
    ... The lack of bursting is really a function of the carrier, ... especially if you have servers in the ... Advertising of shares/printers by workstations and servers ... the central office that they do not need to be connecting to. ...
    (microsoft.public.win2000.networking)

Quantcast