In a good jam here, could use some . Have a couple of 2000
servers that I re-ip addressed from another office. Put them on my
subnet of 10.0.13.x . They can ping anything in the 10.0.13 using dns
and IP. I have other vlans in the network and they can ping 10.0.14.x
and 10.0.2.x by IP but not using DNS. If I do a nslookup it finds the
dns server and resolves from there but you cannot ping anything outside
of 10.0.13.x 255.255.255.0 using DNS. If you go by IP it works
wonderfully. Thanks.

Whittled it down to one server that is having the issue. Changed
cables, switches the whole 9. Machine can ping outside its own network
by IP but not name. Thanks.

Joe wrote:
> In a good jam here, could use some . Have a couple of 2000
> servers that I re-ip addressed from another office. Put them on my
> subnet of 10.0.13.x . They can ping anything in the 10.0.13 using
> dns and IP. I have other vlans in the network and they can ping
> 10.0.14.x and 10.0.2.x by IP but not using DNS. If I do a nslookup
> it finds the dns server and resolves from there but you cannot ping
> anything outside of 10.0.13.x 255.255.255.0 using DNS. If you go by
> IP it works wonderfully. Thanks.

Check the Advanced tab to see if recursion has been disabled or if there is
a "." forward lookup zone, delete it.
If neither of these fix it, make sure the DNS server has a valid Gateway on
its subnet. (Netdiag will test this)
Possible root hints corruption, replace the root hints with the cache.dns
file. http://support.microsoft.com/kb/249868/en-us

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

All other servers are not having this issue - just one Windows 2000
Server. The rest of the environment and DNS looks healthy. The ip
settings on that server have the correct gateway and subnet
assignments. The host file and lmhost.sam files are factory. This
machine just will not ping by name to anything on another subnet. All
machines on the same switch/segment are ok.

Joe

"Joe" <jrogulski@hotmail.com> wrote in message
news:1144690219.949598.241370@i40g2000cwc.googlegr oups.com...
> All other servers are not having this issue - just one Windows 2000
> Server. The rest of the environment and DNS looks healthy. The ip
> settings on that server have the correct gateway and subnet
> assignments. The host file and lmhost.sam files are factory. This
> machine just will not ping by name to anything on another subnet. All
> machines on the same switch/segment are ok.
>

We presume it WILL ping by address.

Will it fetch DNS using NSLookup from EVERY one of
the DNS servers listed in the NIC->IP properties or
shown when you do "IPConfig /all".

The symptoms of pinging on the local subnet and NOT
across routers TEND to suggest that you are resolving
local names through NetBIOS broadcasts (which is
a normal fail over mechanism for MS-NetBIOS machines.)

A common reason for client DNS failure (which this seems
to be) is configuring the WRONG DNS server or a MIXTURE
(of internal and external) DNS servers on the client NIC->
IP properties.

By testing explicitly using NSLookup you will prove that the
client can actually contact the DNS listed.

It is also MUCH BETTER to cut and paste the IPconfig /all
output to avoid any typos AND avoid overlooking any
mistakes in the settings (our eyes tend to see what we expect
to see, cut and paste is not fooled.)

nslookup NameAcrossRouter IP.DNS.Server.Preferred
nslookup NameAcrossRouter IP.DNS.Server.Alternate
nslookup NameAcrossRouter IP.DNS.Server.etc

You may only have a PREFERRED but try every one if you
have more than one listed on the client NIC settings (and
for ANY NIC showing in IPConfig /all).


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

It will ping by IP. Keep in mind that all servers are in the same
switch with different vlans. This one server is in vlan 13. The
servers that are in vlan 2 are the .2 address and the .14 address is
vlan 14. The server will ping by name and ip any server in the
10.0.13.x network. It will not ping anything by name in any other
network. It will ping the IP - not the name. this switch uplinks to
a L3 switch so routing is correct and trunking between vlans is working
fine. This is the only machine effected.

If I use NSLOOKUP it is like there aren't any problems at all. It will
communicate with the DNS server fine that way.


Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : wnspfap03
Primary DNS Suffix . . . . . . . : fake.domain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82546EB Based Dual
Port Net
work Connection
Physical Address. . . . . . . . . : 00-09-6B-F1-8D-AA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.13.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.13.1
DNS Servers . . . . . . . . . . . : 10.0.2.25
10.0.14.25

Default Server: cpspad11.fake.domain.com
Address: 10.0.2.25

> rhspsql03
Server: cpspad11.fake.domain.com
Address: 10.0.2.25

Name: rhspsql03.fake.domain.com
Address: 10.0.2.41

> server cpspad12
Default Server: cpspad12.fake.domain.com
Address: 10.0.14.25

> rhspsql03
Server: cpspad12.corp.fake.domain.com
Address: 10.0.14.25

Name: rhspsql03.corp.aleagroup.com
Address: 10.0.2.41

>

"Joe" <jrogulski@hotmail.com> wrote in message
news:1144694388.288424.264380@v46g2000cwv.googlegr oups.com...
> It will ping by IP. Keep in mind that all servers are in the same
> switch with different vlans.

Then they are different SUBNETS (one hopes) and NOT
on the same "broadcast domain".

It really doesn't matter whether this is a Switch with separate
VLANs or Router(s) with separate physically subnet (except
we have HEARD a significant number of reports on 'buggy'
switches.)

> This one server is in vlan 13. The
> servers that are in vlan 2 are the .2 address and the .14 address is
> vlan 14.

Separate subnets. Other than hardware bugs this is an
irrelevant distinction (i.e., the switch/VLAN).

> The server will ping by name and ip any server in the
> 10.0.13.x network.

Then it will ping off its SUBNET as you have described
it (but your description was VERY VAGUE since you
didn't provide the actual subnet masks or even full IPs.)

> It will not ping anything by name in any other
> network. It will ping the IP - not the name. this switch uplinks to
> a L3 switch so routing is correct and trunking between vlans is working
> fine. This is the only machine effected.

So it is NOT a "subnet problem" but some sort of Local
versus WAN (or other remote) issue, perhaps the only thing
not working is Internet access.

As long as it can resolve names* on another VLAN/Subnet then
I would expect that you have SOME DNS working since
broadcasts (NetBIOS failover) won't work across subnets by
default (unless you have enabled such broadcasts which is
unlikely with today's hardware/practices.)


> If I use NSLOOKUP it is like there aren't any problems at all. It will
> communicate with the DNS server fine that way.

Did you try BOTH DNS servers?

> DNS Servers . . . . . . . . . . . : 10.0.2.25
> 10.0.14.25

You seem to have used NSLookup "within the shell" instead
of performing it explicitly as I suggested -- I see no indication
that you switched servers (from the Preferred to the Alternate)
which was part of the SPECIFIC test I suggested.

They must BOTH work for ALL addresses (your clients need.)

And since you edited your IPConfig /all by hand we
cannot be certain you didn't remove critical information.

If both/ALL DNS servers work with NSLookup, then you
do NOT have a (permanent DNS issue).

Clear cache in case you have an (old) problem that is now
fixed (ipconfig /flushdns) but from here I would go to tracert.

When name resolution works but ping does not, you test by
determining how far you can ROUTE by using tracert (or
pathping, but I really don't like the latter.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

>

Herb -

I guess I wasn't making myself clear. Aside from the vlan config
picture this. You have a server with an ip address of 10.0.13.120
255.255.255.0. From this server you can basically ping anything via
IP or DNS in the 10.0.13.x network. You can also ping any server in
the company no matter what routable subnet it is on via IP. However
you cannot ping them through DNS. This is the only server on the
switch/network that is having this problem. It recently had the IP
address changed. NSLOOKUP works fine. Below is a tracert
C:\>tracert 10.0.2.25

Tracing route to CPSPAD11 [10.0.2.25]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 10.0.13.1
2 <10 ms <10 ms <10 ms CPSPAD11 [10.0.2.25]

Trace complete.

C:\>ping cpspad11
Unknown host cpspad11.

As you can see if does resolve the name there but will not ping it by
name. I have performed an ipconfig/flushdns several times. Not
getting cranky but I did manually edit my ipconifg/all above but took
great care in doing so. Although I did not do the nslookup
specifically as you suggested, the result was the same from all 6 DNS
servers in the domain. DNS is fine. The machine will ping another
machine on any subnet but will only ping them USING DNS if it is on its
own subnet.

Thanks.