Vista DNS ping issues

we have 2003 AD/ native mode with a few vista pro version.
we have equipment such as routers, AP's that we have setup IP address.
AD DNS structure (thumbnail)
SERVERNAME
mydomain.com
_msdcs
ap (has the access point records)
router (has the router records)
_sites

on our XP boxes we can Ping atlanta1.ap (which replies FQDN
atlanta1.ap.mydomain.com)
this does not work on any Vista with ping atlanta1.ap says cant find host.

any reason why cant ping in Vista. only FQDN works.
BTY I scripted out all the equipment this way with the DNSCMD
dnscmd server.mydomain.com /RecordAdd mydomain.com atlanta1.ap A 192.168.1.2

"poboy_n.o_style" <> wrote in message
news:92F8B799-275B-4A8C-8C8D-...
> we have 2003 AD/ native mode with a few vista pro version.
> we have equipment such as routers, AP's that we have setup IP address.
> AD DNS structure (thumbnail)
> SERVERNAME
> mydomain.com
> _msdcs
> ap (has the access point records)
> router (has the router records)
> _sites
>
> on our XP boxes we can Ping atlanta1.ap (which replies FQDN
> atlanta1.ap.mydomain.com)
> this does not work on any Vista with ping atlanta1.ap says cant find host.
>
> any reason why cant ping in Vista. only FQDN works.
> BTY I scripted out all the equipment this way with the DNSCMD
> dnscmd server.mydomain.com /RecordAdd mydomain.com atlanta1.ap A
> 192.168.1.2


Is the Search Suffix on the Vista machines set to both of the following?
mydomain.com
ap.mydomain.com

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer


For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay

yes, in the IPV4 DNS Suffixes in the Advanced TCP/IP settings.
ap.mydomain.com
router.mydomain.com
Etc.
ping required not find atlanta1.ap


"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "poboy_n.o_style" <> wrote in message
> news:92F8B799-275B-4A8C-8C8D-...
> > we have 2003 AD/ native mode with a few vista pro version.
> > we have equipment such as routers, AP's that we have setup IP address.
> > AD DNS structure (thumbnail)
> > SERVERNAME
> > mydomain.com
> > _msdcs
> > ap (has the access point records)
> > router (has the router records)
> > _sites
> >
> > on our XP boxes we can Ping atlanta1.ap (which replies FQDN
> > atlanta1.ap.mydomain.com)
> > this does not work on any Vista with ping atlanta1.ap says cant find host.
> >
> > any reason why cant ping in Vista. only FQDN works.
> > BTY I scripted out all the equipment this way with the DNSCMD
> > dnscmd server.mydomain.com /RecordAdd mydomain.com atlanta1.ap A
> > 192.168.1.2
>
>
> Is the Search Suffix on the Vista machines set to both of the following?
> mydomain.com
> ap.mydomain.com
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
>
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right
> things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>

"poboy_n.o_style" <> wrote in message
news:7AD2FB27-A300-4FDE-B17C-...
> yes, in the IPV4 DNS Suffixes in the Advanced TCP/IP settings.
> ap.mydomain.com
> router.mydomain.com
> Etc.
> ping required not find atlanta1.ap

Is ".ap" a domain name? Do you have a 'single label name' zone in DNS
created called 'ap'?

That sounds like a single label domain name, which is an illegal DNS name
that newer operating systems will ignore. DNS is hierarchal, and requires a
minimum of two layers, for example ap.com or ap.net ('com' or 'net' in this
example are first level names, and 'ap' is the second level).

Therefore, if you try to ping a single name, the system uses the host
resolution method first. It will append the search suffix and query DNS
until it finds it, then if it cannot, it will go to NetBIOS resolution.

If a DNS zone called 'ap' exists, and the search suffix, 'ap' exists, the
system will suffix ap to atlanta1 to come up with atlanta1.ap, then query
DNS, however, this becomes a domain name query because there is no host
name prefixed. So to the system, it looks like you are querying for
'domain.com' when you query 'atlanta1.pa'. Does that make sense?

Ace

"Ace Fekay [Microsoft Certified Trainer]" <>
wrote in message news:...

In addition, post an unedited ipconfig /all from a Vista and XP machine so I
can compare the difference, please.

Thanks

C:\>ipconfig /all (Vista)

Windows IP Configuration

Host Name . . . . . . . . . . . . : VISTAPC
Primary Dns Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com
ap.mydomain.com (I put these in
Manually)
dsl.mydomain.com
frame.mydomain.com
switch.mydomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Controlle
r
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
IPv4 Address. . . . . . . . . . . : 192.168.197.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, June 05, 2009 2:17:17 PM
Lease Expires . . . . . . . . . . : Thursday, June 25, 2009 10:02:03 AM
Default Gateway . . . . . . . . . : 192.168.197.1
DHCP Server . . . . . . . . . . . : 192.168.195.1
DNS Servers . . . . . . . . . . . : 192.168.195.24
192.168.195.25
Primary WINS Server . . . . . . . : 192.168.195.24
Secondary WINS Server . . . . . . : 192.168.195.25
NetBIOS over Tcpip. . . . . . . . : Enabled

Here is XP
Windows IP Configuration

Host Name . . . . . . . . . . . . : computerroom7
Primary Dns Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . :
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.197.191
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.197.1
DHCP Server . . . . . . . . . . . : 192.168.195.1
DNS Servers . . . . . . . . . . . : 192.168.195.24
192.168.195.25
Primary WINS Server . . . . . . . : 192.168.195.24
Secondary WINS Server . . . . . . : 192.168.195.25
Lease Obtained. . . . . . . . . . : Monday, June 22, 2009 6:27:15 AM
Lease Expires . . . . . . . . . . : Thursday, June 25, 2009 6:27:15 AM

Also, I think that might be making more sense since ap.mydomain.com is not a
Zone, it is just how the DNSCMD put in in when I ran the script to add them
years ago, our DNS is setup like this:
Servername
Forward Lookup Zones
mydomain.com
_msdcs'
_sites
_tcp
_udp
ap
domainDnsZone
dsl
ForestDnsZones
switch
Reverse Lookup Zones

Since it is not a Zone, Vista and 2008 does not see them, but XP can.

"poboy_n.o_style" <> wrote in message
news:F8CD5663-0768-4AE7-89C8-...
> C:\>ipconfig /all (Vista)
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : VISTAPC
> Primary Dns Suffix . . . . . . . : mydomain.com
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : mydomain.com
> ap.mydomain.com (I put these in
> Manually)
> dsl.mydomain.com
> frame.mydomain.com
> switch.mydomain.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : mydomain.com
> Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
> Controlle
> r
> Physical Address. . . . . . . . . :
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> IPv4 Address. . . . . . . . . . . : 192.168.197.10(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Friday, June 05, 2009 2:17:17 PM
> Lease Expires . . . . . . . . . . : Thursday, June 25, 2009 10:02:03 AM
> Default Gateway . . . . . . . . . : 192.168.197.1
> DHCP Server . . . . . . . . . . . : 192.168.195.1
> DNS Servers . . . . . . . . . . . : 192.168.195.24
> 192.168.195.25
> Primary WINS Server . . . . . . . : 192.168.195.24
> Secondary WINS Server . . . . . . : 192.168.195.25
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Here is XP
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : computerroom7
> Primary Dns Suffix . . . . . . . : mydomain.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : mydomain.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : mydomain.com
> Description . . . . . . . . . . . : NVIDIA nForce Networking
> Controller
> Physical Address. . . . . . . . . :
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.197.191
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.197.1
> DHCP Server . . . . . . . . . . . : 192.168.195.1
> DNS Servers . . . . . . . . . . . : 192.168.195.24
> 192.168.195.25
> Primary WINS Server . . . . . . . : 192.168.195.24
> Secondary WINS Server . . . . . . : 192.168.195.25
> Lease Obtained. . . . . . . . . . : Monday, June 22, 2009 6:27:15
> AM
> Lease Expires . . . . . . . . . . : Thursday, June 25, 2009 6:27:15
> AM
>
> Also, I think that might be making more sense since ap.mydomain.com is not
> a
> Zone, it is just how the DNSCMD put in in when I ran the script to add
> them
> years ago, our DNS is setup like this:
> Servername
> Forward Lookup Zones
> mydomain.com
> _msdcs'
> _sites
> _tcp
> _udp
> ap
> domainDnsZone
> dsl
> ForestDnsZones
> switch
> Reverse Lookup Zones
>
> Since it is not a Zone, Vista and 2008 does not see them, but XP can.


But they are zones. If they are yellow folders under mydomain.com, then they
are zones. Vista and XP should be able to ping them, if pinged normally.

Earlier you said you tried to ping "ping atlanta1.ap." But that is not a
proper ping, unless I am missing something. Normally, let;s say there's a
host under ap.mydomain.com called atlanta, then simply "ping atlanta" and
the resolver service will try each suffix until it gets a hit, or simply
ping atlanta.ap.mydomain.com. Otherwise pinging 'atlanta.ap," the resolver
service will think it's a domain name, such as 'domain.com.' This is the way
the resolver works.

So I am not sure exactly how you are pinging. Are you trying to ping just
'atlanta.ap"?

Ace

Yes, from the Vista I am just trying to ping atlanta.ap (does not work), yes
the FQDN ping of atlanta.ap.mydomain.com does work on vista.
On xp, i can ping both atlanta.ap (no mydomain.com) and the FQDN.

I have some heavy pc users that know what PING is and they use it to verify
the AP and Routers (etc) when users call. With Vista they can't ping the way
they use to with XP. Now they have to put the the FQDN, they dont like to
have to type. I think that I have everything right on the DNS servers, they
will just have to type in the FQDN from now on.

>
> But they are zones. If they are yellow folders under mydomain.com, then they
> are zones. Vista and XP should be able to ping them, if pinged normally.
>
> Earlier you said you tried to ping "ping atlanta1.ap." But that is not a
> proper ping, unless I am missing something. Normally, let;s say there's a
> host under ap.mydomain.com called atlanta, then simply "ping atlanta" and
> the resolver service will try each suffix until it gets a hit, or simply
> ping atlanta.ap.mydomain.com. Otherwise pinging 'atlanta.ap," the resolver
> service will think it's a domain name, such as 'domain.com.' This is the way
> the resolver works.
>
> So I am not sure exactly how you are pinging. Are you trying to ping just
> 'atlanta.ap"?
>
> Ace
>
>

"poboy_n.o_style" <> wrote in message
news:619E4F8C-3502-4AAB-8447-...
> Yes, from the Vista I am just trying to ping atlanta.ap (does not work),
> yes
> the FQDN ping of atlanta.ap.mydomain.com does work on vista.
> On xp, i can ping both atlanta.ap (no mydomain.com) and the FQDN.
>
> I have some heavy pc users that know what PING is and they use it to
> verify
> the AP and Routers (etc) when users call. With Vista they can't ping the
> way
> they use to with XP. Now they have to put the the FQDN, they dont like to
> have to type. I think that I have everything right on the DNS servers,
> they
> will just have to type in the FQDN from now on.


If you remove the search suffixes that you manually added in Vista, does it
work?

Also, compare the settings in Vista's and XP's NIC properties if the 'append
suffix...' settings and other related settings under IP properites,
Advanced, DNS tab, are the same or different.

Ace

Yes, I removed them and added them in Vista neither way works. Both XP and
Vista are DHCP. I do not have to do anything on the XP boxes. No changes were
ever made to XP as Ping works as it should. I never added any suffixes in GPO
on XP or Vista only manually on Vista.