ping to trace hops?

[leco]

I guess so:( Is there another way of checking what's happening on my connection?

[elloyd69]

Can't tracert from school..........hits our server then continually times out. Any ideas??

[Martin]

Your firewall is blocking the Ping (ICMP) packets.

 

mb

[mac_shinobi]

Your firewall is blocking the Ping (ICMP) packets.

 

mb

 

Is it possible to do something like this on the internal network so that when trying to do an nslookup that nslookup will not work with regards to resolving network device hostnames to ip addresses or visa versa regardless of whether its a photocopier, computer or whatever ??

[mac_shinobi]

No, NSLOOKUP queries your DNS server to find an IP address from a name (and vice versa). It's nothing to do with pings.

 

So take it if nslookup does not work on copiers ie resolving hostnames to ip addresses and visa versa then the copier(s) have or has not registered with dns or has had said A host records deleted out of dns?

[mac_shinobi]

That's right. Most likely that the copier isn't DNS aware (or has its DNS incorrectly configured), so you have to add the records into DNS.

 

Try and find out if the copier can be set up to use DNS.

 

Am pretty sure it is setup on DNS as it uses DNS to resolve computer names when doing scan to folder and scan to email ( resolving hostname of smtp / email server to its ip address ) and visa versa but as soon as I do an nslookup on either the hostname or ip address of any of the copiers we have it won't do it for the copiers.

 

However the strange thing is - when using the hostname of any of the copiers for a standard tcp/ip port for printing it resolves fine as it obviously finds out the correct ip address / details etc so not sure if its a restriction or what exactly bit of an odd one.

[mac_shinobi]

One way to check is to use NSLOOKUP in debug mode - not many people know you can do this.

 

At the command prompt, type NSLOOKUP

 

This will enter NSLOOKUP's interactive mode.

 

Type

SET DEBUG

 

Now type the device you want to look-up. e.g.

copier1

 

You'll see a lots of lines, the important one is the QUESTIONS: line. This is what's being queried in your DNS system. With luck it should be obvious what's going wrong. My money is on a problem with the DNS suffix.

 

thats how i normally do an nslookup in command prompt but will give that a go tommorow