Re: Client Machine cannot see Active Directory
- From: Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 Sep 2005 06:19:02 -0700
I set the DHCP server to use internal.briess.com as the dns suffix for
clients so invoicing01 should be using the correct DNS suffix...
however the latest netdiag still produces the same errors (see below) might
there be some replication issues at play? Even though I only have 1 internal
DNS/DHCP server?
Netdiag results for invoicing01
.........................................
Computer Name: INVOICING01
DNS Host Name: invoicing01.internal.briess.com
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
List of installed hotfixes :
KB834707
KB873333
KB873339
KB883939
KB885250
KB885835
KB885836
KB886185
KB887472
KB887742
KB888113
KB888302
KB888310
KB890046
KB890175
KB890859
KB890923
KB891781
KB893066
KB893086
KB893756
KB893803v2
KB894391
KB896358
KB896422
KB896423
KB896428
KB896727
KB898461
KB899587
KB899588
KB899591
KB901214
KB903235
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : invoicing01.internal.briess.com
IP Address . . . . . . . . : 192.168.1.133
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.254
Primary WINS Server. . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.1
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Passed
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{83A3CA29-E14D-4EA9-86A4-6EAA6DFBDAF3}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{83A3CA29-E14D-4EA9-86A4-6EAA6DFBDAF3}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{83A3CA29-E14D-4EA9-86A4-6EAA6DFBDAF3}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed
Secure channel for domain 'BRIESS' is to
'\\w-server2k.internal.briess.com'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC
'web2k.internal.briess.com'.
[WARNING] Failed to query SPN registration on DC
'solomon2k.internal.briess.com'.
[WARNING] Failed to query SPN registration on DC
'w-server2k.internal.briess.com'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
Service status is: Started
Service startup is: Automatic
IPSec service is available, but no policy is assigned or active
Note: run "ipseccmd /?" for more detailed information
The command completed successfully
"Derek Schauland" wrote:
> Hello Ace,
>
> I do remember using a single name rather than the FQDN when adding this box
> to the domain.
>
> the IP info is below, sorry for not providing it sooner...
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : invoicing01
>
> Primary Dns Suffix . . . . . . . : internal.briess.com
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : internal.briess.com
>
> BRIESS
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . : BRIESS
>
> Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
> Controller
>
> Physical Address. . . . . . . . . : 00-12-3F-2E-4A-70
>
> Dhcp Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
>
> IP Address. . . . . . . . . . . . : 192.168.1.133
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.1.254
>
> DHCP Server . . . . . . . . . . . : 192.168.1.1
>
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> Primary WINS Server . . . . . . . : 192.168.1.1
>
> Lease Obtained. . . . . . . . . . : Monday, September 12, 2005
> 7:50:52 AM
>
> Lease Expires . . . . . . . . . . : Thursday, October 27, 2005
> 7:50:52 AM
>
> I am guessing that removing the PC and adding it back to the domain using
> internal.briess.com as the domain name would correct this?
>
> Derek
>
> "Ace Fekay [MVP]" wrote:
>
> > In news:6CB3B2B9-2E03-4F0E-A932-46D6FA01C114@xxxxxxxxxxxxx,
> > Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
> > which I then commented about below:
> > > Thanks Ace.
> > >
> > > I looked through the DNS Zones that are set up and this pc
> > > (invoicing01) points to xxx.xxx.1.133 anywhere in DNS that it is
> > > referenced. I also checked the properties for TCP/IP and set the
> > > local DNS server as the only one to be used...
> >
> > I am assuming you are hiding the IP because it is a public IP? If it is
> > private, then hiding 192.168.1.133 is really not necessary.
> >
> >
> > > I ran netdiag on invoicing01 and got a [Warning] failed to query SPN
> > > registration on DC 'dc fqdn' might this have something to do with the
> > > problem?
> >
> > SPN is based on the FQDN called invoicing01.yourdomain.com. Do you have a
> > single label name domain name?
> >
> > > Also when trying to browse the network in net neighborhood, Active
> > > Directory doesnt appear in Entire Network.. it just shows Windows
> > > Network. And trying to access the DFS using \\domain produces an
> > > error about being unavailable, but if I try \\domain\dfsrootname the
> > > window pops right up...
> >
> > It's starting to look like a single label domain name. I'm guessing at this
> > point with the limited info provided. That was why I asked for that info to
> > actually see everything one shot.
> >
> > A single label name is "domain" rather than the required format of
> > "domain.com", "domain.net", "domain.local", or "domain.derek".
> >
> > Ace
> >
> >
> >
> >
.
- Follow-Ups:
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- References:
- Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- From: Derek Schauland
- Client Machine cannot see Active Directory
- Prev by Date: ADMT - 2000 to 2003
- Next by Date: RE: Removing Kerberos Trust relationships that will not remove.
- Previous by thread: Re: Client Machine cannot see Active Directory
- Next by thread: Re: Client Machine cannot see Active Directory
- Index(es):
Relevant Pages
|
Loading