test-drb November 2001

test-drb@ccmp.vtda.org

247 participants
886 discussions

Sun / CalComp Printer networking problems (was: Thick Ethernet/Sun networking problems)

by pete＠dunnington.u-net.com

On Nov 5, 7:40, Arno Kletzander wrote: > We're positive that the IP address is still the one it was set to all the > time (111.1.0.1) because we finally got the Ethernet Adapter Status Page > printed out. OK, so we assume the printer knows its own address. > I'd already found and read this page. Amazingly, they mention only two of > the three LEDs my Ethernet Adapter has (IP, DATA and LINK). During the warmup > phase, IP (green) and DATA (amber) are illuminated. After that, the IP LED > goes on with a blink (rather 2 than 5 Hz, I'd say...), while the DATA LED > flickers whenever something is transmitted on the Ethernet. The LINK LED > stays off all the time. All of this seems to belong to the "NORMAL" column. If the LINK LED stays off, I'd be inclned to believe the interface isn't working; on all the devices I've seen it, the LINK LED is on if the network is live. Seems odd if the DATA LED blinks when there's traffic, though. I wonder what that LINK LED really is for? > 3. Pete Turnbull wrote: > >> 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): > > > >Which is correct for a Class A network... > > But isn't it outside the address section which is allowed for equipment > which might possibly be connected to Internet? - But the PC we want to connect > has got a modem!!! (OK, skip that until they work with their current addresses) Er, no, 111.0.0.0 is a real Internet address. Perhaps you're thinking of the "private" Class A network address, 10.0.0.0? The private addresses are NOT allowed to be connected to the Internet. > >For Arno, this means: > >create /etc/ethers if it doesn't exist > >append a line with printer name and MAC (Ethernet) address > >/etc/hosts must already exist for the Sun to work, so append a line for the > printer > >start up rarpd if it's not already running > >(the order in which you do these shouldn't matter) > >If we call the printer "calcomp", the line in /etc/ethers is: > > > >00:C0:E2:00:0C:8E calcomp > > hombre_tcsh (2) arp -s calcomp 00:0c:e2:00:0c:8e > > arp: calcomp: unknown host Well, to use rarpd the name in /etc/ethers has to match the line in /etc/ hosts. Also the name in the "arp -s" must match the name in /etc/hosts. Whn I wrote the descriptin, I didn't know the printer name so I just picked one. > /etc/ethers does not exist, but...I must stress once again that the system > worked once and I don't suppose it existed back then (because nobody who had > access to the system since then would have deleted anything). Then they didn't use RARP, or if they did, not from that Sun. > >Ethan Dicks wrote: > >> I think it's useful when you have an ancient network where the broadcast > address uses 0-bits, rather >>than 1-bits - i.e., ip 192.168.1.1 with a > netmask of 192.168.1.0 and a broadcast address of >>192.168.1.0 *not* > 192.168.1.255. It's archaic, but allowed. > > > >So it is -- I forgot about that! The rest of what I wrote may well be > drivel :-) > > That might be contributing to our problem. What, my drivel? Yes, quite likely :-) > At boot, the complete network section reads: > > network interfache configuration: > le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING> > inet 111.0.0.14 netmask ff000000 broadcast 111.0.0.0 > ether 8:0:20:9:bc:d7 ^^^^^^^^^ Using the old-style "wrong" broadcast address might affect ARP (which as I explained is used to get a MAC address of a destination before sending IP packets), but otherwise won't break anything. Besides, you said it worked before. > ;logging in as SU: > hombre# arp -s pa3 00:0c:e2:00:0c:8e > > hombre# > > ;Seems to have succeeded, checking: > > hombre# arp -a > pa3 (111.1.0.1) at 0:c0:e2:0:c:8e permanent > > hombre# telnet pa3 2002 > Trying 111.1.0.1 ... > telnet: connect: Connection timed out > > ;Same as it was before...pinging also still times out (no answer from pa3). Assuming 0:c0:e2:0:c:8e is the printer's MAC address, and it does know its address is 111.1.0.1, that should work -- unless the printer interface is broken or it doesn't respond to port 2002. You could try ports 9099, 9100 (used by HP JetDirect printers), 515 (lpd port), 161 (SNMP), 7 (echo). Some of those normally use UDP rather than TCP, so you might need to get something like netcat instead of telnet, though. > Oh, and "permanent": After a reboot, the old (incomplete) is there again > instead of the MAC address. Very permanent indeed... It means it doesn't age out of the arp table the way normal entries do. Normal entries age out in case IP addresses change, or in case routers are doing proxy ARP for hosts on a different subnet (in which case if the route changes, so does the ARP entry). All entries still get lost on reboot; they're stored in kernel memory but nowhere else. -- Pete Peter Turnbull Network Manager University of York

24 years

Sun / CalComp Printer networking problems (was: Thick Ethernet/Sun networking problems)

by Arno_1983＠gmx.de

Oh Gosh, that's a lot of stuff... I think I should've mentioned I'm in digest mode... 1. Douglas Quebbeman and Dan Wright wrote about scanning all possible IP adresses. Besides taking an awful lot of time, this is no longer necessary because we got a status page printed out which states the IP address to be still 111.1.0.1. 2. Lawrence LeMay wrote: >So, it would help me if you briefly restated the exact problem. I'm assuming you have a calcomp plotter >(but i dont know which one), that it has a M971 ethernet card... That is, mostly, correct. What we're having here is a CalComp CCL600ES, a large laserprinter, hooked up to a Thick Ethernet segment together with two SUN SPARCstations (1+ and 2) (and a 486 PC for sniffing purposes). >...and that you dont know what the IP address is set to. (...) Well, one way of solving this problem is to >reset the M971 card back to factory defaults, and then setting the IP address. Unfortunately I dont >have the manuals, but if you have the manuals you should be able to look some of this up. There is a >reset jumper on the ethernet card, so you power down the printer, remove the card, install the jumper, >power it up, then repeat to remove the jumper (assuming i recall the procedure correctly). We're positive that the IP address is still the one it was set to all the time (111.1.0.1) because we finally got the Ethernet Adapter Status Page printed out. This is done by setting the JP1 jumper on the 971, reinserting the card into the printer, and then powering up. (I suppose this means we don't have to do all that 'automated pinging' stuff...). >http://www.calgraphinc.com/Support/unix_networking.html I'd already found and read this page. Amazingly, they mention only two of the three LEDs my Ethernet Adapter has (IP, DATA and LINK). During the warmup phase, IP (green) and DATA (amber) are illuminated. After that, the IP LED goes on with a blink (rather 2 than 5 Hz, I'd say...), while the DATA LED flickers whenever something is transmitted on the Ethernet. The LINK LED stays off all the time. All of this seems to belong to the "NORMAL" column. 3. Pete Turnbull wrote: >> 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): > >Which is correct for a Class A network... But isn't it outside the address section which is allowed for equipment which might possibly be connected to Internet? - But the PC we want to connect has got a modem!!! (OK, skip that until they work with their current addresses) >For Arno, this means: >create /etc/ethers if it doesn't exist >append a line with printer name and MAC (Ethernet) address >/etc/hosts must already exist for the Sun to work, so append a line for the printer >start up rarpd if it's not already running >(the order in which you do these shouldn't matter) >If we call the printer "calcomp", the line in /etc/ethers is: > >00:C0:E2:00:0C:8E calcomp > >and the line in /etc/hosts is > >111.1.0.1 calcomp (...) OK. /etc/hosts is present, reading in total: # Local Net 111.x.x.x -- 10 Mb/s Ethernet -- DAZIX # 127.0.0.1 localhost loghost 111.0.0.14 hombre 111.0.0.23 papa 111.1.0.1 pa3 /etc/ethers does not exist, but...I must stress once again that the system worked once and I don't suppose it existed back then (because nobody who had access to the system since then would have deleted anything). Also, at boot time, a line appears reading Starting local daemons: auditd sendmail (...) rarpd (...). >Is "pa3" the printer name? Yes. >Some more experimentation is needed to be sure what all the symptoms really mean. However, >obviously the printer isn't responding to an ARP request for what should be its own IP address. >Therefore either it is using some other IP address, or it has lost it's configuration and needs to be >supplied an IP address (by RARP or otherwise), or the interface is broken/dormant. I agree to that. We now know the IP adress is still correctly stored. We also know the Ethernet interface is receiving every packet transmitted (flickering DATA LED). And we know that it doesn't respond - from the (incomplete); so the interface might really be kaputt - I don't hope so, however... >Ethan Dicks wrote: >>(...) >> I think it's useful when you have an ancient network where the broadcast address uses 0-bits, rather >>than 1-bits - i.e., ip 192.168.1.1 with a netmask of 192.168.1.0 and a broadcast address of >>192.168.1.0 *not* 192.168.1.255. It's archaic, but allowed. > >So it is -- I forgot about that! The rest of what I wrote may well be drivel :-) That might be contributing to our problem. At boot, the complete network section reads: network interfache configuration: le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING> inet 111.0.0.14 netmask ff000000 broadcast 111.0.0.0 ether 8:0:20:9:bc:d7 ^^^^^^^^^ lo0: flags=49<UP,LOOPBACK,RUNNING> inet 127.0.0.1 netmask ff000000 4. Iggy Drougge wrote: >You can find out the ethernet MAC address for the printer, right? Then create an ARP entry for that one. >On BSDs (the UNIX type I'm familiar with), it's done with: >arp -s arp -s hostname ether_addr >(...) >Try: >telnet 111.1.0.1 2002 hombre_tcsh (1) telnet 111.1.0.1 2002 Trying 111.1.0.1 ... telnet: connect: Connection timed out telnet> quit ;>All right, if that doesn't work, we'll have to do the abovementioned entry in the ARP table, using the ;>Ethernet address seen above: ;>arp -s calcomp 00:c0:e2:00:0c:8e hombre_tcsh (2) arp -s calcomp 00:0c:e2:00:0c:8e arp: calcomp: unknown host ;>Now you've made an ARP entry. ;Seemingly not...trying with the correct hostname: hombre_tcsh (3) arp -s pa3 00:0c:e2:00:0c:8e pa3: Not owner ;logging in as SU: hombre# arp -s pa3 00:0c:e2:00:0c:8e hombre# ;Seems to have succeeded, checking: hombre# arp -a pa3 (111.1.0.1) at 0:c0:e2:0:c:8e permanent hombre# telnet pa3 2002 Trying 111.1.0.1 ... telnet: connect: Connection timed out ;Same as it was before...pinging also still times out (no answer from pa3). Oh, and "permanent": After a reboot, the old (incomplete) is there again instead of the MAC address. Very permanent indeed... Okay, that's it for this time. I hope we'll bring that printer back up again. Thanks for your given and coming assistance. Arno Kletzander DO4NAK (2m; 70cm) Arno_1983(a)gmx.de -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

24 years

VT330/VT340 Manual

by vance＠ikickass.org

Anyone know where I might find the manual for a VT330 or VT340 online? I am looking for configuration info and factory default settings and other things of that nature. I would also appreciate it if someone could give me pointers on my DECserver 700. Thanks a lot. Peace... Sridhar

24 years

Friden Flexowriter (fwd)

by doug＠nut.net

Flexowriter available in Chicago (contact MHardig(a)aol.com). ---------- Forwarded message ---------- Date: Sun, 4 Nov 2001 19:12:32 EST From: MHardig(a)aol.com To: doug(a)blinkenlights.com Subject: Friden Flexowriter I have used these. As recently as a few years ago. I own one. It works, to the best of my knowledge, the punch feature anyway. I haven't figured out how to make the read feature work, but then this one is a lot newer than the one I trained on. The model I have is a late 60's, and spent most of it's life punching tape for CNC machines. Do you think anyone would be interested in this? I've had people interested but they're too far away to ship this ungainly bastard. I live near Chicago. Thanks in advance. Cool website! Mark Hardig

24 years

connectors needed

by jhellige＠earthlink.net

I'm in need of the following pieces and would like some input on where to pick them up: - 8bit ISA slot connector, female, 31pins - 31pin ribbon cable, approx. 3-4 inches long - dual row header, female connector, 31pins each row, spacing the same as the ISA connector. What I want to do is make a short adapter to go from the Tandy 1000 PLUS-style bus connector to an 8bit ISA bus connector. I have a small circuit board already that does the conversion the other way, allowing PLUS style boards to be used in an ISA slot but I wish to plug an 8bit ISA board into the PLUS slot. The adapter board is single layer and it shows it to be a straight conversion from the ISA bus to the first row of pins. I'm told that at one time DCS Industries provided such an adapter cable with some of their upgrades but I've not been able to get any answers from them as far as if they still have any. Thanks Jeff -- Home of the TRS-80 Model 2000 FAQ File http://www.cchaven.com http://www.geocities.com/siliconvalley/lakes/6757

24 years

Thick Ethernet/Sun networking problems

by dhquebbeman＠theestopinalgroup.com

> > > Don't forget to restore the original address with "ifconfig le0 111.0.0.1 > > > broadcast 111.255.255.255 netmask 255.0.0.0 up" when you've finished > :-) > > > > What does 'broadcast' do (other than the obvious)? > > It's just a way of explicitly stating what the broadcast address for that > interface is. In every legitimate case I can think of, it should be > redundant if you provide the netmask (or the netmask is redundant if you Oh, it's the broadcast paramater for the ifconfig command, when the lines wrapped, it made it look like a separate command, thus my confusion... -dq

24 years

AT&T 6300 SOTA Cable?

by tarsi＠binhost.com

Would anyone out there have the 24" cable for the i386 SOTA card for the 6300? I have the 14" cables but they're not long enough and aren't shaped right to use in the 6300. Thanks! Tarsi 210 -- ---------------------------------------------- Homepage: http://tarsi.binhost.com binHOST.com: http://www.binhost.com Forever Beyond: http://www.foreverbeyond.org ----------------------------------------------

24 years

Termcap for VT340

by vance＠ikickass.org

Does anyone have a termcap/terminfo entry for a VT340 which will allow ReGIS color sequences in things like the Linux 'ls'? Is such a thing even possible? The terminfo entry in my database seems to be written for the VT330. Peace... Sridhar

24 years

RD54 and RT-11 5.4D

by dittman＠dittman.net

I recently swapped the MV II CPU and memory in my BA23 with a PDP-11/73 CPU and memory. I booted RT-11 V5.4D and attempted to init the RD54, which failed: .init /segment:5 du0: DU0:/Initialize; Are you sure? Y ?DUP-F-Directory output error DU0: . The drive was working just fine as a ODS-2 volume. I don't have to low-level format, do I? -- Eric Dittman dittman(a)dittman.net Check out the DEC Enthusiasts Club at http://www.dittman.net/

24 years

RD54 and RT-11 5.4D

by dittman＠dittman.net

> Okay, I'm back from a DR exercise and have started trying to get > this PDP-11/73 working with RT-11. I have a copy of the XXDP > formatter now, and trying to format the hard drive gives this > error: > > Unit Cylinders Drive Name > 0 1225 RD54 > 1 RX50 Diskette (UNFORMATABLE) > 2 RX50 Diskette (UNFORMATABLE) > > > MSCP Controller Model: 19 > Microcode Version: 1 > > ZRQC SYS FTL ERR 00007 ON UNIT 00 TST 001 SUB 000 PC: 105742 > Controller has reported a fatal error in the FORMAT program. > Status: FCT write error (check write protect switch) > > Drive 0 was not formatted successfully. > > ZRQC EOP 1 > 1 TOTAL ERRS > > > Since this drive worked fine under VMS before I started the > conversion, I am starting to think there is a jumper on either > the RQDX3 or the RD54 that has to be changed to use the drive > under RT-11, since the write protect switch is NOT enabled (I > even toggled it to make sure). Okay, I've tried different disks, RQDX3 controllers, and disk cables, and nothing seems to work. I even took an RD52 out of my Pro-380 that I know works and tried to use the formatter and it gives the same error. The WP switch is definitely not pressed, and when I press it I do get a light. I've downloaded the RQDX3 manual and checked the jumpers. -- Eric Dittman dittman(a)dittman.net Check out the DEC Enthusiasts Club at http://www.dittman.net/

24 years

← Newer
1
...
78
79
80
81
82
83
84
...
89
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb November 2001