Re: Help - main dc playing tricks
From: Alan (Alan_at_discussions.microsoft.com)
Date: 03/01/05
- Next message: Bill Nitz: "Re: script and email accounts"
- Previous message: Gerry: "Setting Proxy Settings with GP"
- In reply to: ptwilliams: "Re: Help - main dc playing tricks"
- Next in thread: ptwilliams: "Re: Help - main dc playing tricks"
- Reply: ptwilliams: "Re: Help - main dc playing tricks"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Mar 2005 04:41:08 -0800
regardless of this, the computers still take ages to start up.
what can i look into.. as the computer doesn't log any errors, it just hangs
on "applying computer settings" , the servers arn't showing anything and once
the logon box appears, the user accounts log in fine. the profiles and files
are located on the main dc
"ptwilliams" wrote:
> According to this, /registerdns won't work and you need to do a /release and
> then a /renew
> --
> http://www.eventid.net/display.asp?eventid=11163&eventno=1746&source=DnsApi&phase=1
>
>
> --
>
> Paul Williams
>
> http://www.msresource.net
> http://forums.msresource.net
>
>
> "Alan" <Alan@discussions.microsoft.com> wrote in message
> news:4A7F6EFA-FC1D-420F-8BD3-62C9968E7684@microsoft.com...
> Just tested a second workstation for a static ip to see if dhcp is the
> cause...
> did a ipconfig /registerdns after setting the static ip and got the
> following in the eventlog
> a static ip didn't make any difference either.
>
>
> Event Type: Warning
> Event Source: DnsApi
> Event Category: None
> Event ID: 11163
> Date: 01/03/2005
> Time: 10:58:56
> User: N/A
> Computer: E1102
> Description:
> The system failed to register host (A) resource records (RRs) for network
> adapter
> with settings:
>
> Adapter Name : {0C3E2681-6E43-4D42-A300-1D04D9A4C51A}
> Host Name : e1102
> Primary Domain Suffix : sps.local
> DNS server list :
> 192.168.0.2, 192.168.0.3
> Sent update to server : 192.1.1.1
> IP Address(es) :
> 192.168.0.28
>
> The reason the system could not register these RRs was because the DNS
> server failed the update request. The most likely cause of this is that the
> authoritative DNS server required to process this update request has a lock
> in place on the zone, probably because a zone transfer is in progress.
>
>
> Any idea why it's being sent to 192.1.1.1
>
>
>
- Next message: Bill Nitz: "Re: script and email accounts"
- Previous message: Gerry: "Setting Proxy Settings with GP"
- In reply to: ptwilliams: "Re: Help - main dc playing tricks"
- Next in thread: ptwilliams: "Re: Help - main dc playing tricks"
- Reply: ptwilliams: "Re: Help - main dc playing tricks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|