OT Ping Query
Basil Holloway
8580 aix 1.3 192.168.0.101
8565 aix 1.3 192.168.0.25
7012 aix 4.3 192.168.0.177
7012 aix 3.2 192.168.0.218
gigabyte XP 192.168.0.21
7044 aix 5.3 192.168.0.142
9114 aix 6.1 192.168.0.80
router 192.168.0.1
They can all ping one another and can transfer files via ftp.
Tutorial states
"ping sends an ICMP ECHO_REQUEST message to a network host every second.
ping 192.0.0.255 Generates responses from all the other nodes connected on
a class C network.
If you wish to see what nodes are up and responding on your network, this is
a simple test to run. "
ping 192.0.0.255 on any computer just times out.
ping 192.168.0.255 on any computer just shows a no packets loss from
192.168.0.1
Anyone know why 192.0.0.255 does not work.
Looks like a great tool to see if all turned on computers on a network are
communicating okay.
I presume when 192.0.0.255 is used on one computer the others are shown up
one by one on the screen.
Thanks
Basil
Cheers
In article <cXsCm.48326$ze1....@news-server.bigpond.net.au>,
farl...@bigpond.com says...
>
> Have following on P2P network
>
> 8580 aix 1.3 192.168.0.101
> 8565 aix 1.3 192.168.0.25
> 7012 aix 4.3 192.168.0.177
> 7012 aix 3.2 192.168.0.218
> gigabyte XP 192.168.0.21
> 7044 aix 5.3 192.168.0.142
> 9114 aix 6.1 192.168.0.80
> router 192.168.0.1
>
> They can all ping one another and can transfer files via ftp.
>
> Tutorial states
>
> "ping sends an ICMP ECHO_REQUEST message to a network host every second.
> ping 192.0.0.255 Generates responses from all the other nodes connected on
> a class C network.
what they meant here is the 192.x.x.255 subnetting in the range for
example 192.168.0.1-192.168.0.255
and so on......
> If you wish to see what nodes are up and responding on your network,
this is
> a simple test to run. "
>
> ping 192.0.0.255 on any computer just times out.
obvious, unless you set the subnetmask to 255.0.0.0 on each node
something you don't want to do!.
> ping 192.168.0.255 on any computer just shows a no packets loss from
> 192.168.0.1
thats good
>
> Anyone know why 192.0.0.255 does not work.
read above
> Looks like a great tool to see if all turned on computers on a network
> are
there's a much easier and more efficient way to do it, nmap :-)
> communicating okay.
> I presume when 192.0.0.255 is used on one computer the others are
> shown up
> one by one on the screen.
now bare in mind that only 192.168.x.x is a private ip address.
http://en.wikipedia.org/wiki/Private_network
all arrived Basil, thanks again for the early x-mas gift.
the rs6000 arrived safely and booted ok, but can't work out the user
name!
will test the HD as soon as i get the other RS6000 going.
>
> Thanks
> Basil
--
The information contained in this post is copyright of
the poster, and specifically may not be published in,
or used by http://www.jlaforums.com
Basil Holloway
"Cheers" <mous...@hotmail.com> wrote in message
news:MPG.25450a7f3...@192.168.1.253...
Thanks Moussa
found nmap for AIX 5.1 at
http://bio.gsi.de/DOCS/AIX/aixpdslib.seas.ucla.edu/packages/nmap.html
and will give it a go 7043-140.
Basil
supervinx
xxx.xxx.xxx.0 identifies the net itself
xxx.xxx.xxx.255 is referred as "broadcast"
so if you want to "broadcast" a message to every PC on a certain subnet,
you send it to xxx.xxx.xxx.255.
In your case, 192.168.0.255.
Some ping flavours need a -b to ping a broadcast address
ping xxx.xxx.xxx.255 -b
But nmap is a more efficient way to do this, expecially when ping
requests are ignored or filtered ...
nmap 192.168.0.0/24 scans all address in your subnet
supervinx
Uli Link
> AFAIK
> xxx.xxx.xxx.0 identifies the net itself
> xxx.xxx.xxx.255 is referred as "broadcast"
Only if you use a 24bit subnet mask (a.k.a 255.255.255.0 == FF.FF.FF.00)
There may other netmasks, so neither .0 nor .255 implicate any special
meaning without the proper mask.
Something like ClassC does not exist any more since decades.
Nonetheless a /24 netmask is the default for very most SoHo routers and
192.x.x.x is in the old ClassC range.
--
ULi
supervinx
for me ... (and for Basil ...)
supervinx
Dr. Jim
> But nmap is a more efficient way to do this, expecially when ping
> requests are ignored or filtered ...
>
> nmap 192.168.0.0/24 scans all address in your subnet
If you have a Windoze box on your net (I know, sacrilege), there are
some interesting free tools here:
-Jim
Basil Holloway
Down loaded nmap on XP and on transfering it to the AIX box during unpacking
and get the checksum error. Tried a few downloads all with same result.
Although all my AIX boxes have browsers installed don't like to go on web
with them as no anti virus installed.
Made an exception and this happened on all seven AIX boxes.
Open the browser and up pops my home page 168.0.0.1. Log in and then connect
to my dial up ISP okay.
Select a favourite and at the bottom of the router page it says
" looking up www.google.com.au "
or any other web address I put there and then just sits there for several
minutes until I close it down or the address not found message comes up.
Put http://74.125.91.104 into the browser address bar and the google page
nearly opens but the bottom of the router page it says
" looking up clients 1 google.com " and just sits there until the address
not found message comes up.
I can ping my isp, google or any other web address from any AIX box but
cannot complete the connection.
All the W98, W2K and XP boxes on the same P2P network work okay.
I just cannot fathom out what has happened to the AIX boxes.
Double checked all the settings in the router and all AIX boxes and they are
as per set up logs.
Any ideas where to look next ?
Basil Holloway
the same result.
Did a complete new reinstall of bos and still get the same strange
behaviour.
Had a spare router so installed it. Win boxes okay AIX boxes not.
Think something must be happening at ISP.
Filled out their service report. They usually take a few days to react.
Cheers
In article <4ROCm.48536$ze1....@news-server.bigpond.net.au>,
farl...@bigpond.com says...
DNS is not properly installed, and you should not be using 168.0.0.1
range if you're behind a router, you need to use one of the private
subnet range, example 192.168.0.1-192.168.254.254
am trying to adapt linux to aix, look in /etc for resolv.conf, you
should have something like, nameserver "your isp dns ip".
more here http://theos.in/desktop-linux/resolve-conf-linux-example/
Moussa
Basil Holloway
Sorry typo. Router is 192.168.0.1
/etc/resolv.conf is
nameserver 139.134.5.51
domain sy-dns03.tmns.net.au
Dug into DNS
The opening page of router under DOMAIN NAME SERVER
used to say 139.134.5.51 , 139.134.2.190
and it now says 203.49.70.20 , 139.134.2.190
BigPond web site says
Primary DNS 139.134.5.51
Secondary DNS 139.134.2.190
In AIX under smit only one DNS can be used.
I tried one AIX computer yesterday on 139.134.2.190 sy-dns04.tmns.net.au
and it did not fix the problem.
Just now went to try 203.49.70.20 but the tools on the web says it is
garbage no ISP name so cannot input it into SMIT.
What do you think BigPond is up to. Funny Windows can handle it.
Cheers
> Moussa
>
> Sorry typo. Router is 192.168.0.1
>
> /etc/resolv.conf is
> nameserver 139.134.5.51
> domain sy-dns03.tmns.net.au
>
> Dug into DNS
> The opening page of router under DOMAIN NAME SERVER
> used to say 139.134.5.51 , 139.134.2.190
> and it now says 203.49.70.20 , 139.134.2.190
>
> BigPond web site says
> Primary DNS 139.134.5.51
> Secondary DNS 139.134.2.190
you should place those into the router
and turn on dnscache if your router support it
your router should supply one of the above dns ip as primary, and is own ip
as secondary,
use autodhcp on the client node side whenever is possible.
>
> In AIX under smit only one DNS can be used.
> I tried one AIX computer yesterday on 139.134.2.190 sy-dns04.tmns.net.au
> and it did not fix the problem.
> Just now went to try 203.49.70.20 but the tools on the web says it is
> garbage no ISP name so cannot input it into SMIT.
>
> What do you think BigPond is up to. Funny Windows can handle it.
sacre Rouje !:-)
according to traceroute "tracert under windblows), is Tel$tra gateway....
supervinx
to the router, ie
Primary DNS: xxx.xxx.xxx.xxx
Secondary DNS: yyy.yyy.yyy.yyy
(both set on the router)
or let the router be automatically assigned DNSes.
Every PC in the LAN has as DNS the router address (in your case
192.168.0.1).
I see that your router is set to receive DNS addresses from the provider,
while in the AIX box was statically set to LAN external address, that,
maybe is down.
Set resolv.conf to 192.168.0.1, it should work ...
Peter H. Wendt
> Although all my AIX boxes have browsers installed don't like to go on web
> with them as no anti virus installed.
That caught my attention.
You don't need no stinkin' antivirus when you use AIX ... ;-)
Or OS/2.
Unless you'd installed a decent variant of JAVA and / or Javascript.
Then it might be no better than Winbloat.
--
Peter from Germany
http://www.mcamafia.de
Rick Ekblaw
> What do you think BigPond is up to. Funny Windows can handle it.
The good news is that you don't *have* to use BigPond's DNS servers if
they aren't working well for you. Check with your buddies that use
other ISPs (iiNet is a big Aussie ISP, as I recall) and try some other
DNS servers until you find a couple that work well with your AIX boxes.
Rick Ekblaw
Basil Holloway
Yesterday all the Windows boxes completely collapsed like the AIX boxes the
day before.
Can get onto ISP okay but cannot connect to mail server nor any web page.
Did complete virus scans, tested router, reset up router and rebooted. Ran
ipconfig /renew etc etc etc and still no solution.
Just set up XP now with its own serial modem and can connect to internet
read web pages and mail. Hence this posting.
A complete unsolved mystery.
Cheers
In article <Ex7Dm.48775$ze1....@news-server.bigpond.net.au>,
farl...@bigpond.com says...
funny , when i turned the aix box yesterday, the router got bashed badly
for few hours, http://members.iinet.net.au/~moussa/cpu-day.png, this is
a proper dual xeon server 2 x 1.2ghz, i can only described as DoS
attack, all the traffic was directed at the AIX box on the network,
turned off the box, the attack scaled down.
i will look into the box later, as i am on busy schedule today :-(, not
enough time for me to play with my toys.
Moussa
Basil Holloway
Moussa
That is strange.
Today I turned on my AIX 5.3 box and it took 20 minutes to boot up but it
only got to the blue screen just before the cde desktop and I got the error
"DT messaging could not be started and to hit okay then go into fail safe
mode and check /etc/hosts and /etc/resolv.conf."
Hosts file checked out okay but resolv.conf had a blank line put at the
start of the file and the nameserver line moved down one line. The domain
line had been deleted.
Fixed it all up and on restart the DT message came up again. resolv.conf had
been trashed again.
Thinking I may have made a mistake in vi redid the correct entries, shut
down vi and reopened resolv.conf with vi and my corrections held.
Rebooted and DT again with a trashed resolv.conf.
Went back in under fail safe and completely deleted resolv.conf and built a
new one. It was trashed again on restart.
Put back my mksysb of a few days ago and AIX 5.3 restarts up okay.
Looked at my AIX 5.2 and 6.1 boxes and they had trashed resolv.conf files
too which I could not correct.
Will have to put back mysysb's tomorrow. I suppose the same has happened to
my other three AIX boxes.
Tomorrow will also have to hunt for the resolv.conf equivalent in W95,98,W2K
and XP to see if the same has happened there.
Can a master virus be implanted in a router ? Don't want to connect the AIX
boxes to it yet to see if they will bring up web pages. Each mksysb
reinstall takes 1hr 25 minutes.
Basil
Uli Link
> Today I turned on my AIX 5.3 box and it took 20 minutes to boot up but it
> only got to the blue screen just before the cde desktop and I got the error
> "DT messaging could not be started and to hit okay then go into fail safe
> mode and check /etc/hosts and /etc/resolv.conf."
> Hosts file checked out okay but resolv.conf had a blank line put at the
> start of the file and the nameserver line moved down one line. The domain
> line had been deleted.
The CDE desktop needs to resolve its own name/ipaddress.
So if you use DHCP as suggested earlier, your DNS resolver *must*
resolve the machine's name.
Your ISP's DNS won't resolve the private ipaddresses behind your router.
--
ULi
supervinx
To resolve private IP addresses, should be enough to set /etc/hosts (or
something similar on AIX) ?
On my Linux machines I did so ... private addresses are resolved lookin'
into /etc/hosts, external address by the DNS(es)
supervinx
OpenDns nameservers are: 208.67.220.200 & 208.67.222.222
Horst Franke
wrote:
> Can get onto ISP okay but cannot connect to mail server nor any web
> page. Did complete virus scans, tested router, reset up router and
> rebooted. Ran ipconfig /renew etc etc etc and still no solution.
Hi Basil
what do You mean by "reset up router"? SW or HW related?
I had similar symptoms sometimes:
(my OS is Win XP Home sp3 - but that should not matter)
then I needed to perform a *hardware reset* on my DSL-router box:
i.e. a power OFF/ON sequence!
> Just set up XP now with its own serial modem and can connect to
> internet read web pages and mail. Hence this posting.
> A complete unsolved mystery.
NO! Looks like Your problem is Your router hardware.
Try a hardware reset (without any changes on SW setup).
Horst