Longshine : PS 110 printserver instellen

We set up the PS 101-2 USB print server using Telnet. And that's how we're going to do it with the 101 as well but now via the detour of first enabling the DHCP client. After it has set itself to my IP range, we will give it a fixed IP lateron.

Connect your pribtserver to the mains (with the wall wart adapter) and connect it to a PC with a UTP cable. You can do it straigh away; no need for a switch or hub.
The PS 101-2 USB printserver is, like most other Longshine products, Auto-MDI so it figures out by itself what the polarity of the cabling is.

Just like with the PS 101, the PS 110 is factory default supplied with the IP address 192.168.0.10 and since I use the IP range 192.168.56.xxx here, I must first sync the IP ranges. If you happen to be running with IP range 192.168.0.xxx you're home free and can skip to step 6 right now.
For the rest of us: log on as 'root' and edit the file '/etc/rc.d/rc.inet1.conf'
But first we make some backups for an easy return:

     cp /etc/rc.d/rc.inet1.conf inet1.conf.56

In this file, there are some code snippets like the one in the picture on the right. Change your IP adress such, that the third number from the left reads '000'. In my case, I ended up with 192.168.000.4 It may be a good idea to do this for the Gateway as well.
Now restart your network subsystem with the command '/etc/rc.d/rc.inet1 restart' or '/etc/rc.d/rc.inet1 restart_eth0' (depending on your flavor of Linux).
Check with 'ifconfig' that your IP address is changed.

root@Beryllium:/home/jan# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:d8:dd:79:d8
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
	  inet6 addr: fe80::211:d8ff:fedd:79d8/64 Scope:Link
	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
	  RX packets:9855 errors:0 dropped:0 overruns:1 frame:0
	  TX packets:10111 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:1000
	  RX bytes:5037487 (4.8 MiB)  TX bytes:6480206 (6.1 MiB)
          Interrupt:18 Base address:0x8000

First try to ping the print server to see if it's visible to us:

     root@Beryllium:/home/jan# ping -c 2 192.168.0.10
     
     PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
     64 bytes from 192.168.0.10: icmp_seq=1 ttl=32 time=0.618 ms
     64 bytes from 192.168.0.10: icmp_seq=2 ttl=32 time=0.575 ms

     --- 192.168.0.10 ping statistics ---
     2 packets transmitted, 2 received, 0% packet loss, time 999ms
     rtt min/avg/max/mdev = 0.575/0.596/0.618/0.032 ms

which looks just fine to me. Now it's time to log on to the PS 110:

     telnet 192.168.0.10

With the PS 101 we still had to learn that the -l switch was not necessary. The password is 'Enter' again.
We're now in the Telnet protocol and we are to set the printserver the old fashioned way. Not because we are old fashioned, but just because we decided to do so. To learn a few more tricks and for the fun of it. It's an experience for the future, when you suddenly need to do something on that old machine that only knows Telnet... Below is the Telnet dialog. Between brackets is some comment in dutch. Please ignore it.

jan@Beryllium:~$ telnet 192.168.0.10
Trying 192.168.0.10...
Connected to 192.168.0.10.
Escape character is '^]'.

Telnet Service on the PrintServer

Password:
** Main Menu on Printer Server **

  1. Look at status in Print Server
  2. Setting value in Print Server
  3. Load Default
  4. Reset Print Server
  0. Exit Setup

Enter your choice ->1		( eerst gaan we kijken )

** View Data in the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   0. Back To Last Menu

Enter your choice ->4		( we gaan naar TCP IP kijken )

** TCP/IP Information **

   DHCP/BOOTP  : Disable		( DHCP klant staat uit )
   IP Address  : 192.168.0.10		( IP adres staat vast  }
   Subnet Mask : 255.255.255.0
   Gateway     : 0.0.0.0
   0. Back To Last Menu

Enter your choice ->0		( we gaan terug )

** View Data in the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   0. Back To Last Menu

Enter your choice ->0		( nog verder terug )

** Main Menu on Printer Server **	( tot het hoofdmenu )

  1. Look at status in Print Server
  2. Setting value in Print Server	( deze moeten we hebben )
  3. Load Default
  4. Reset Print Server
  0. Exit Setup

Enter your choice ->2

** Setting Data into the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   8. Save And Reset
   0. Back To Last Menu

Enter your choice ->4		( we moeten het IP adres instellen )

** TCP/IP Setup **

   1. DHCP/BOOTP  : Disable
   2. Specify IP
   0. Back To Last Menu

Enter your choice ->1		( deze keer zetten we de DHCP aan )
Input(1.Enable 2.Disable): 1		( kies voor 'Enable'		  )

** TCP/IP Setup **

   1. DHCP/BOOTP  : Enable		( gelukt ! 	)
   2. Specify IP
   0. Back To Last Menu

Enter your choice ->0		( en terug naar het hoofdmenu )

** Setting Data into the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   8. Save And Reset
   0. Back To Last Menu

Enter your choice ->8		( we kiezen 'opslaan' )

Now the PC locks up. At least, that's what it looks like. But it's simpler than that: the printserver has set itself to another IP address and the PC is still listening to the old one... And so it freezes over.

Take care! If your system does not freeze here, the operation failed!

Lucky for us, we still got the previous values, so that's easy. Make sure you're still 'root'. First rescue the current config file (we might need it later on):

     mv /etc/rc.d/rc.inet1.conf inet1.conf.00
     cp inet1.conf.56 /etc/rc.d/rc.inet1.conf

and then restart your network subsystem (like you did in step 2); check again with 'ifconfig'.

Your printserver now runs with DHCP on and it has requested (and obtained) an IP address from your router. But you cannot predict which one.... So we're going to look for it. Log on to your router and consult the table with the dynamically assigned IP addresses. Look for something with 'printserver' in the name. In my case the PS 110 got address 158. So that's what we're gonna use now.

jan@Beryllium:~$ telnet 192.168.56.158
Trying 192.168.56.158...
Connected to 192.168.56.158.
Escape character is '^]'.

Telnet Service on the PrintServer

Password:
** Main Menu on Printer Server **

  1. Look at status in Print Server
  2. Setting value in Print Server
  3. Load Default
  4. Reset Print Server
  0. Exit Setup

Enter your choice ->2		( we gaan weer instellen )

** Setting Data into the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   8. Save And Reset
   0. Back To Last Menu

Enter your choice ->4		( TCP IP )

** TCP/IP Setup **

   1. DHCP/BOOTP  : Enable
   2. Specify IP
   0. Back To Last Menu

Enter your choice ->1		( DHCP client afzetten )
Input(1.Enable 2.Disable): 2

** TCP/IP Setup **

   1. DHCP/BOOTP  : Disable
   2. Specify IP
   0. Back To Last Menu


Enter your choice ->2		( IP adres opgeven )

** Specify IP **

   1. IP Address  :    192.168.56.158
   2. Subnet Mask :    255.255.255.0
   3. Gateway     :    192.168.56.99	( Gateway heeft ie van de DHCP server gekregten )
   0. Back To Last Menu

Enter your choice ->1		( IP adres aanpassen )
Input IP Address(x.x.x.x): 192.168.56.224

** Specify IP **

   1. IP Address  :    192.168.56.224
   2. Subnet Mask :    255.255.255.0
   3. Gateway     :    192.168.56.99
   0. Back To Last Menu

Enter your choice ->0		( Klaar )

** TCP/IP Setup **

   1. DHCP/BOOTP  : Disable
   2. Specify IP
   0. Back To Last Menu

Enter your choice ->0

** Setting Data into the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   8. Save And Reset
   0. Back To Last Menu

Enter your choice ->8Killed

Here again: a seeming lockup. For the same reason: the telnet client listens on 158 whereas the printserver is now talking at 224. So kill it from another console.
Now we log on for the third time to the printserver (and we know how to this by now):

jan@Beryllium:~$ telnet 192.168.56.224
Trying 192.168.56.224...
Connected to 192.168.56.224.
Escape character is '^]'.

Telnet Service on the PrintServer

Password:
** Main Menu on Printer Server **

  1. Look at status in Print Server
  2. Setting value in Print Server
  3. Load Default
  4. Reset Print Server
  0. Exit Setup

Enter your choice ->1

** View Data in the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   0. Back To Last Menu

Enter your choice ->4

** TCP/IP Information **

   DHCP/BOOTP  : Disable
   IP Address  : 192.168.56.224
   Subnet Mask : 255.255.255.0
   Gateway     : 192.168.56.99
   0. Back To Last Menu

Enter your choice ->0

** View Data in the Printer Server **

   1. System
   2. Printer
   3. Netware
   4. TCP/IP
   5. SNMP
   6. APPLETALK
   0. Back To Last Menu

Enter your choice ->0

** Main Menu on Printer Server **

  1. Look at status in Print Server
  2. Setting value in Print Server
  3. Load Default
  4. Reset Print Server
  0. Exit Setup

Enter your choice ->0

 Quit Print Server Console
Connection closed by foreign host.
jan@Beryllium:~$

Looks fine to me. We succeeded! This method is a lot more work than the one we used for the PS101. But we learned something else again.

Open the webbrowser of your choice and open 'http://localhost:631'. Choose 'Add printer' and follow the steps. As interface, choose 'Socket' and in the next screen I entered 'socket://192.168.56.224' After that choose the brand and type of your printer, do a testpage, set allowed users and you're done.
And that's it. Rerun CUPS on all your Linux machines. With Windows choose a LOCAL printer. The thing is on your network, but if you try to install a network printer things get hairy. So don't.
From now, you can print to this printer from anywhere in your network at high speed. Faster than with a normal parallel interface! And since the PS110 has 2 MB of printerbuffer memory, most print jobs fit in it right away. Reducing the load on your network!

Today I retired the HP JetDirect 170X printserver. The LCS PS 110 now does its job and it outperforms the 170X by miles! To start with, the 170X was just a 10 Mbps version whereas the LCS is Fast Ethernet. And the LCS has a webinterface built with plain old HTML and CGI. No more outdated Java rubbish.
While tuning the PS 110 I decided to give it a name appropriate for it's IP number: Berkelium. I also added some housekeeping information and gave it the same password as used by the other active components in house.
And that's when things went wrong... The new password should not exceed 8 characters. Mine was 9. You get no error message so you just do a 'Save & Restart' operation, and prepare for a new login to the printserver. Which did not work. The 9th token is not relevant, yet is accepted by the password checker. Hence: all log on attempts fail.

The solution was not to give it a factory defaults reset. Just plain old thinking did the job: use the Telnet server to log on! Telnet knows (and shows) that the password is only 8 tokens. When the first 8 are in (and correct) you are granted access. From there on things get simple. Just find the place where the password is set and erase it (hit 'Enter' twice) and top it off with a 'Save & Restart'. That's it!
This Longshine is much more fun than the old HP!

Pagina gemaakt op 27 juni 2009

Deze pagina is voorzien van FroogleBuster technologie