Re: Client Machine cannot see Active Directory

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
>
>
>
>
.

Relevant Pages

  • Re: network path not found when i use FQDN on Shares
    ... DNS woks fine, nslookup and ping works fine on both, FQDN and NetBIOS ... Networking, Internet, Routing, VPN Troubleshooting on ... How to Setup Windows, Network, VPN & Remote Access on ... We have a Windows 2003 SP2 fileserver with some shares and Windows XP Sp3 ...
    (microsoft.public.windows.server.networking)
  • Cross Post from ActiveSync Newsgroup - Problem Resolving Internal and FQDN Addresses when Using
    ... a Windows Mobile device in our SBS 2003 network. ... if I use the FQDN of our server for the Proxy name in the ... the device will not find the server to ActiveSync. ... My role as "SBS Administrator" is a completely unpaid adjunct to my real ...
    (microsoft.public.windows.server.sbs)
  • Re: How is DNS resolution working?
    ... When we did the ping, we used the FQDN ... >> This is going to get a bit complicated, so here's what the network ... >> If you look in the DNS server on machine B, ...
    (microsoft.public.win2000.dns)
  • Re: How is DNS resolution working?
    ... When we did the ping, we used the FQDN ... >> This is going to get a bit complicated, so here's what the network ... >> If you look in the DNS server on machine B, ...
    (microsoft.public.win2000.networking)
  • Re: mail confusion
    ... if you're using names then there probably are cases that a FQDN ... >> I certainly find having a local network domain name useful. ... On one PC that I have, it didn't associate "localhost" with the ... > insisted that a reserved domain name is needed for local networks; ...
    (Fedora)