As you guessed, the hex version works as suggested:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
c:\>ping 0xC0.0xA8.0.0x38
Pinging 192.168.0.56 with 32 bytes of data:
Reply from 192.168.0.56: bytes=32 time<10ms TTL=128
Reply from 192.168.0.56: bytes=32 time<10ms TTL=128
Reply from 192.168.0.56: bytes=32 time<10ms TTL=128
Reply from 192.168.0.56: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.0.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
c:\>
At least it all makes sense now.
Bob Comeau
Sr. Systems Programmer Analyst
Tandus Canada / Crossley Carpet Mills Ltd.
(902)895-5491 ext 139
"Keven Miller (rtt)" <[log in to unmask]>
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
05/30/07 03:19 PM
Please respond to
"Keven Miller (rtt)" <[log in to unmask]>
To
[log in to unmask]
cc
Subject
Re: Printer woes resolved
I believe all current routines that read ip addresses,
use something written in C, and use its defaults of
leading 0 numbers are octal, unless lead by 0x.
I wonder if 0xC0.0xA8.0.0x38 would do?
(192.168.0.56)
hmm, seems to work from my Win2K ping to my printer.
NMMGR however, is a bit older, and doesn't use those
nice routines to read the ip address.
So on the Gateway page, you need leading zeros.
Keven
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
