Hey, I actually solved a problem instead of just posing them. :) I think that
falls under the "just walk away and deal with something else for a while"
method.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Stefan Jafs
Sent: Wednesday, October 26, 2016 8:43 AM
To: [email protected]
Subject: RE: [NTSysADM] Ping -a does not work anymore
Bingo, no Reverse lookup Zones for the other subnets, added and it works now on
all subnets.
Thanks for steering me in the right direction
__________________________________
Stefan Jafs
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Tuesday, October 25, 2016 15:20
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] Ping -a does not work anymore
Assuming you already know all this but sometimes it just helps to start from
ground zero and go through the data flow to see where things stop working.
Ping -a uses the reverse lookup zones. Do they exist for the failing subnet?
Assuming yes, are they properly updated?
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Stefan Jafs
Sent: Tuesday, October 25, 2016 1:10 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] Ping -a does not work anymore
Ping works fine but not ping -a also same problem with nslookup works on subnet
1 but not on the others
192.168.1.100 works fine, 192.168.21.34 not but can be pinged
__________________________________
Stefan Jafs
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of HELP_PC
Sent: Tuesday, October 25, 2016 02:43
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] Ping -a does not work anymore
But what do you get if you just ping without -a ?
GuidoElia
HELPPC-HELPPCSERVICE
________________________________
Da: [email protected]<mailto:[email protected]>
[[email protected]] per conto di Stefan Jafs [[email protected]]
Inviato: lunedì 24 ottobre 2016 19.50
A: [email protected]<mailto:[email protected]>
Oggetto: RE: [NTSysADM] Ping -a does not work anymore
So to narrow it down, I can ping -a my subnet, and resolve name, however I
can't resolve other subnets I assume its my DNS server settings then.
__________________________________
Stefan Jafs
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of CESAR.ABREG0 .
Sent: Tuesday, October 18, 2016 17:15
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] Ping -a does not work anymore
Most certainly is in our case. It is a highly secure environment.
On Tue, Oct 18, 2016, 2:06 PM Micheal Espinola Jr
<[email protected]<mailto:[email protected]>> wrote:
I can only imagine that this is a firewall/filtering related issue for you. As
Don pointed out, this functionality works across all versions of Windows.
--
Espi
On Tue, Oct 18, 2016 at 12:46 PM, Stefan Jafs
<[email protected]<mailto:[email protected]>> wrote:
For some reason ping -a does not resolve any DNS name anymore, it used to work,
tried it on 2 PC's and 2 Servers.
Google is no help, any ideas?
__________________________________
Stefan Jafs
--
Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non infetto.
Clicca qui per segnalarlo come
spam.<http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=7772B40154.A5268>
Clicca qui per metterlo in
blacklist<http://mx01.enter.it/cgi-bin/learn-msg.cgi?blacklist=1&id=7772B40154.A5268>
