Re: Can't access W2K shares after approx 24 hours
From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 07/03/04
- Next message: Jim Bohan: "Re: TCP/IP Packet Filtering"
- Previous message: Roger Abell: "Re: Disabling ADODB.Stream could break applications ?"
- In reply to: harry: "Re: Can't access W2K shares after approx 24 hours"
- Next in thread: harry: "Re: Can't access W2K shares after approx 24 hours"
- Reply: harry: "Re: Can't access W2K shares after approx 24 hours"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 3 Jul 2004 01:26:45 -0700
You are best off checking your DNS support, rather than
tweaking what may be one symptom. If it is invalid DNS
support you will sooner than later need to get this fixed.
-- Roger Abell Microsoft MVP (Windows Server System: Security) MCSE (W2k3,W2k,Nt4) MCDBA "harry" <harry@nospam> wrote in message news:uvKrI8MYEHA.2140@TK2MSFTNGP11.phx.gbl... > if the autodiconnect doesn't solve it I'll check out detdiag & dcdiag. > > Thanks for your help. > > > "Steven L Umbach" <n9rou@n0-spam-for-me-comcast.net> wrote in message > news:x2hFc.14312$IQ4.4966@attbi_s02... > > When you reinstalled, did you rebuild the domain or was this an additional > domain > > controller?? The proper way to reinstall a dead dc is to restore via > Directory > > Services restore Mode from a backup that includes the System State. I > would run > > netdiag and dcdiag on your domain controller looking for configuration > problems and > > run netdiag on one of those clients next time it "disconnects" to see if > it reports > > errors such as failed tests. Dns misconfiguration is the usual culprit in > that the > > domain controller needs to point to itself or the pdc fsmo as it's only > preferred dns > > server and the domain clients need to point only to AD domain controllers > running dns > > for the domain [they all do by default in W2K]. --- Steve > > > > http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382 > > http://support.microsoft.com/default.aspx?scid=kb;en-us;301423 -- how to > install > > netdiag and dcdiag. Same goes for netdiag on non servers. > > > > "news.microsoft.com" <harry@nospam> wrote in message > > news:%23Qn6%23g$XEHA.2972@tk2msftngp13.phx.gbl... > > > Hi > > > > > > I have couple of WinXP Pro pcs, connected to W2K Server. > > > > > > Just reinstalled W2K server (with AD) recently due to HDD crash. > > > > > > Now I find after approx 24 hours the WinXP pc's don't have permission to > > > access the shared directories on W2K server. When they login to the > domain > > > they have permissions and no problems. > > > > > > However after 24 hours or so (not sure exactly how long - seems to be > > > overnight some time this hapens) all the WinXP pc's can't access the > shares. > > > They can see the domain + W2K server in 'Microsoft Widonws Network' in > > > windows explorer however don't have permission to view the shares. When > I > > > clikc the shared directory, a popu box asks for username + password, but > I'm > > > logged into the domain as Administrator and have max possible rights. > > > > > > Any clue to this weird problem please? > > > > > > Thanks > > > Harry > > > > > > > > > > > >
- Next message: Jim Bohan: "Re: TCP/IP Packet Filtering"
- Previous message: Roger Abell: "Re: Disabling ADODB.Stream could break applications ?"
- In reply to: harry: "Re: Can't access W2K shares after approx 24 hours"
- Next in thread: harry: "Re: Can't access W2K shares after approx 24 hours"
- Reply: harry: "Re: Can't access W2K shares after approx 24 hours"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
