Re: Can't ping by name outside of subnet



"Joe" <jrogulski@xxxxxxxxxxx> wrote in message
news:1144694388.288424.264380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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]




.



Relevant Pages

  • Re: Possible routing problem because of subnet mask change.
    ... Could my DNS Servers be setup wrong? ... That is a subnet MASK not a subnet. ... (generally a single simple hub or same VLAN of a true switch). ... we're having problems with things losing connections. ...
    (microsoft.public.windows.server.general)
  • Re: DHCP relay, superscope and laptops
    ... I have two subnets A and B, one on each VLAN, connected through a L3 switch ... which acts as a DHCP relay to my single DHCP server on subnet A. ... A DHCP request from clients on subnet A are no problem as they are local on ... VLANs don't change anything, L3 Switches don't ...
    (microsoft.public.windows.server.networking)
  • Re: queer dns access problem
    ... Both DNS servers are on 10.1.1.x subnet. ... The path should be server to switch to firewall to switch to DNS. ...
    (RedHat)
  • Re: probably an easy routing question, so please help
    ... I've just realized that VLANs don't just divide subnets, ... router) I won't need to use a Layer 3 switch at all. ... both /28s are configured on the same Enet port, with proxy ARP enabled. ...
    (comp.dcom.sys.cisco)
  • Re: Switch Redundancy question !!
    ... switch) with respect to L3 default gateway for each of the VLANs ... I know STP is the solution for L2 redundancy & HSRP ... Sh int status will show port as routed when it is configured for use as ...
    (comp.dcom.sys.cisco)