ping problem

  • Thread starter Thread starter Ton Kraanen
  • Start date Start date
T

Ton Kraanen

Hello,

I'm running a windows 2000 advanced server with two workstations (XP and
2000Pro). I entered the IPnumber of the server in my workstation.
When I try to ping my workstations from my server ZoneAlarm asks the ping
utility if it may access the internet and ZA gives a different IP number
than that of the workstation. This IPnumber changes everytime I try to ping
the workstations.
If I don't allow ZoneAlarm to access the internet the ping utility gives the
correct IPnumber but without the FQDN, just the name of the machine, on the
other hand if I give ZA access to the internet it gives the FQDN.
Pinging the server from my ws doesn't give a problem.

Greetings, Ton
 
In
Ton Kraanen said:
Hello,

I'm running a windows 2000 advanced server with two workstations (XP
and 2000Pro). I entered the IPnumber of the server in my workstation.
When I try to ping my workstations from my server ZoneAlarm asks the
ping utility if it may access the internet and ZA gives a different
IP number than that of the workstation. This IPnumber changes
everytime I try to ping the workstations.
If I don't allow ZoneAlarm to access the internet the ping utility
gives the correct IPnumber but without the FQDN, just the name of the
machine, on the other hand if I give ZA access to the internet it
gives the FQDN.
Pinging the server from my ws doesn't give a problem.

Greetings, Ton
Click to expand...


I assume in your server that you are ONLY pointing to itself for DNS (and
not your ISP's). I'm also assuming that you've configured a forwarder to
your ISP.

If only pointing to itself, then I cannot see how it would ask another IP.

Can we see an ipconfig /all from the workstation and from the server?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
That's correct, the server points only to itself and I've forwarders
pointing to my nameservers on the internet.
If I use ipconfig /all there's no problem at the workstation, but using this
command at the server I get the same reaction from ZA and it doesn't show a
connection specific DNS suffix.


"Ace Fekay [MVP]"
 
In
Ton said:
That's correct, the server points only to itself and I've forwarders
pointing to my nameservers on the internet.
If I use ipconfig /all there's no problem at the workstation, but
using this command at the server I get the same reaction from ZA and
it doesn't show a connection specific DNS suffix.
Click to expand...

Hmm, that was one of the reasons I wanted to see an ipconfig /all. It tells
us a few things:

1. Your DNS config
2. IP, subnet mask and gateway
3. The Primary DNS Suffix
4. The Search Suffix
5. Node Type

So if you're saying there is no search suffix, then it's leading me to
believe that the Primary DNS Suffix is empty as well. This whole thing comes
down to how you are pinging, such as:

--this will depend on your search suffix:
ping computername

--this does not:
ping computername.domain.com

So if your search suffix is empty or a single label name, then it maybe
hitting your forwarder or the roots. Tell you what, can you at least post
what IP addresses ZA is showing?

Also, if you don't mind me asking at this point, is your AD DNS domain name
a single label name?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
ZA is showing followoing IPnumber: 216.168.1.22. I discovered that when I
ping the server on the server I get the same reaction of ZA and the same IP
number.
My AD DNS name is domain.com.


"Ace Fekay [MVP]"
 
No, I've one LAN and an internet connection through a router, server is dhcp
and dns server.
 
In
Ton said:
ZA is showing followoing IPnumber: 216.168.1.22. I discovered that
when I ping the server on the server I get the same reaction of ZA
and the same IP number.
My AD DNS name is domain.com.
Click to expand...

Running a lookup on 216.168.1.22, I get this below....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>nslookup 216.168.1.22
Server: rbru.br.rs.els-gms.att.net
Address: 199.191.128.103

Name: trinity.ranger.supernews.net
Address: 216.168.1.22
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Apparently this machine is a DNS server.
Is this what you have set as your forwarder?

Without any additional info about your configuration that's about my best
guess at this time. When we ask questions, we're not prying, but asking for
specifics to help diagnose errors or behaviors. One thing I did ask was
simply "how are you pinging?", which can shed light partially why it's going
on, but then if you were to answer that, then I would maybe have needed to
ask you "What is your search suffix?", which you would probably not reply.

Kind of like going to the doc's.... hey doc, my arm hurts. Yes, where does
it hurt? Can't tell you, just that it hurts, so your the doc, tell me....

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
What's so special with the posting two 'ipconfig /all' as Ace asked for 3
times already? You think it's not related but nobody knows your
configuration. If the server looks up in the Internet without getting local
echo, then there can be a lot of reasons.

First, kill or at least disable that ZA and ping yourself. Second, post
'ipconfig /all' (or is it first? :)
 
TK> When I try to ping my workstations from my server ZoneAlarm asks
TK> the ping utility if it may access the internet [...]

Wrong. ZoneAlarm asks _you_ if _ping_ may access the network.

TK> If I don't allow ZoneAlarm to access the internet the ping
TK> utility gives the correct IPnumber but without the FQDN,
TK> just the name of the machine, on the other hand if I give
TK> ZA access to the internet it gives the FQDN.

As is to be expected. "ping" performs two DNS lookups: One to map the
domain name that it is supplied (if it is supplied with a domain name)
to a set of IP addresses, and one to map the IP address that it sends
its test datagrams to back to a (possibly different) domain name.
These DNS lookups involve "ping" sending a DNS query datagram to a
proxy DNS server (the proxy DNS server that you have configured your
DNS Client to use) and receiving a DNS response datagram back.

<URL:http://homepages.tesco.net./~J.deBo...ped-firewall-holes.html#ExternalProxyDirectly>

If you block the DNS lookup datagrams, "ping" can still use other,
non-DNS, sources of information. "ping" is not, after all, a DNS
diagnosis tool.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-results-different-to-ping.html>
 
Back
Top