OK Pete (and everybody else, of course), I admit that was a *long* break
since I brought that up last time - but now I think I have collected enough
information for a new chapter...So, where did we get stuck?
Pete Turnbull wrote:
>>>Have you tried pinging the printer by it's IP address instead of
>>>it's name? Try a broadcast ping?
>>
>>As we're not too familiar with the commands, how is a broadcast
>>ping done?
>
>Instead of giving the IP address of a particular machine, give the
broadcast address of the local subnet. >The broadcast address is the subnet address
but with the host part set to all 1's. For example, for the >class C network
192.168.5.0, the broadcast address is 192.168.5.255. For the class B
network >176.18.0.0, the broadcast address is 176.18.255.255, and for the class A
network 10.0.0.0, it's >10.255.255.255.
>You should get a response from every device on that segment (every device
in that broadcast domain, >actually) which has an IP address within the subnet
range.
OK, as the IP Adress of the SUN 1+ is 111.0.0.14 and the Subnet Mask
ff:00:00:00 (says so at boot):
ping -s 111.255.255.255
(if everything on the network is powered up and the PC is configured for
TCP/IP transfer) gets answers from:
hombre (111.0.0.14);the sending machine itself
papa (111.0.0.23);the SUN SPARCstation 2 on the next desk
? (111.0.0.83);a PC I've finally set up for sniffing
Nothing however from the printer. :-(
>>>Have you checked the printer settings to make sure it's using the
>>>correct IP address? Is that set from its panel, or by RARP/BOOTP/
>>>DHCP? If the latter, it needs a server to boot.
>>
>> Tony Duell wrote:
>>>That printer isn't attempting to get information (IP address,
>>>software, whatever) from a server, is it?
No idea whether that helps, but if both the SUN 1+ and the printer are
powered up, an arp -a shows:
pa3 111.1.0.1 at (incomplete)
and out of 25 packets I sniffed (Man, am I high now ;-)), 20 were ETHER type
0806 (ARP), the remaining 5 were type 0800. See also section "Configuring
the 971" (Ethernet adapter card of the printer).
>Another way to see what's happening, is to use 'snoop' if you have it on
one of the Suns (tcpdump for >Linux/BSD/etc is similar). You need to be logged
in as root, and type "snoop -v" or "snoop -V". That >will show you (in some
detail; -V gives less detail) all the traffic visisble to the le0 interface.
For >example: (...)
OK, as I didn't finde snoop on the Suns (and didn't want to fiddle with
compiling programs by myself at this stage...), I set up a PC with a network
card, packet drivers and EtherLoad 2.00. Connected this to the idle transceiver,
started with -r (record traffic), powered up one SUN and recorded the first
10 packets from it, then powered up the printer and recorded until I had 25
(the printer had then finished its warmup cycle and was displaying "READY").
Got only packets sent by the SUN (MAC: 08.00.20.09.BC.D7) destined for
FF.FF.FF.FF.FF.FF (everybody?).
The sniffer's HEX output file decodes to a lot of unreadable characters if
interpreted as ASCII; only in the second packet that appears after switching
the SUN on, the host name 'hombre' is readable.
Decoding the whole data to decimal numbers show up the SUN's IP adress in
all packets, the address the printer should have in the eighth and every
following packet.
Is there a DOS based sniffer out there which will produce output as
understandable as snoop?
If not, and if anybody wants a go at making sense out of the output, I'll
mail the files private (HEX and decimal 6kB each, data ASCII decoded 2kB)...
>On most of the Ethernet-enabled printers I've come across (mostly HPs,
Lexmarks, and Xeroxes) you >can do the setup from the front panel -- sometimes
tedious, but usually not too hard to understand.
No such menu item or anything related to Ethernet. AFAICFO (as far as I
could find out, adding to the current acronymania...) on the Internet, this is
the procedure for configuring the Ethernet adaptor used in this printer:
#Configuring the 971
#
#Connect the network cable to the appropriate connector.
#
#The following tasks are accomplished by the system administrator:
#-Make an entry in the ARP table
#-Telnet to port 2002
#-Configure the 971 in accordance with your operating system's requirements
#
#The 971 queue is 'raw'.
#
#Refer to Model 971 Network Interface User's Guide P/N M0016-490 and CalComp
Ethernet Software #Guide P/N M0062-240 for information pertaining to your
specific UNIX configuration.
#
#Refer to CalComp Model 971 Ethernet Hardware Guide P/N 501987 for
additional information.
However, with us there is no sys admin - so how can we 'accomplish these
tasks'?
I couldn't find the 'refer to' titles on the web - anybody knowing if/where
they're out there, or having them & willing to scan them for me? Any help
would be much appreciated.
>Have you tried printing out status pages? Sometimes that will show you
things like IP address, >protocols enabled, that sort of thing. Usually you can
do it by holding down one of the buttons when you >turn the power on.
The printer manual tells that test printing is invoked by a long press on
the key PRINT FONTS/TEST after switching the printer OFF LINE. Out comes a page
which does tell absolutely nothing about network settings. It must however
also be possible to print out these settings because in the paperwork, we
found a page which reads as follows:
CalComp Internal Ethernet Adapter
Revision 4.11, Datecode 12/20 1994 10:20
Burnin Value = 0 SRAM = 256K bytes, Novram = 128 bytes
Ethernet address 00 C0 E2 00 0C 8E
Ethernet options: Ignore Alignment Errors Auxilliary data port = 0
IP address: 111.1.0.1
Telnet password security: OFF
Netware options:
!!! Netware DISABLED (use 'N' menu to re-enable) !!!
Auto sense ethernet type between Ethernet II and 802.3
Apple EtherTalk options:
EtherTalk DISABLED !!! (use 'N' menu to re-enable )
Printer name: CalComp CCL600ES
Internally stored zone name: *
Ethertalk Phase 2
LPD ( remote printer queues ) options:
LPD enabled
Output Control-D at end of job on Postscript queues
Output FF at end of job on ASCII queues
Console status monitoring configured as:
Telnet port only
But no idea on how to get this printed again to verify the settings haven't
changed (e.g. due to bitrot in the Novram)...
Sorry for the long post
Sincerely yours
Arno Kletzander
Arno_1983_at_gmx.de
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
Received on Fri Nov 02 2001 - 03:13:18 GMT