Workstation can ping printer but SCO server cannot

[masinc1]

I have a fresh install of 5.0.7 - previously on 5.0.5. We upgraded our server to an dual Xeon processor with 2 gigabyte network cards on the board - an Intel and a Marvell Yukon. I have one HP 2300 laser printer w/Jetdirect plugged directly into the router - it is not attached to a workstation. I used the HP manager to install the printer. Any workstation can ping this printer or the SCO server, but the SCO server cannot ping the printer and correspondingly the printer does not print. I installed driver for the Marvell Yukon and the card showed up in Network Config Manager, but it would not ping the printer. After reboot, the Network Config Manager shows the Intel card (at which point I switched the network cable to the Intel); the Marvell card does not show, but the Marvell driver is in the hardware list without a MAC address and is not linked to the card. I have searched the SCO site and followed all instructions without any success. This is the exact printer that worked flawlwssly under 5.0.5, but it was on a Kingston card. The new motherboard does not have enough slots to install this card. Any help would be appreciated.

 

[Annihilannic]

Are the SCO server and the workstations on the same subnet? If they aren't, are they configured to use the same gateway?

Annihilannic.

 

[masinc1]

They are on the same subnet.

 

[Annihilannic]

Have you checked that the netmasks are the same on SCO, the workstations, and the JetDirect card?

Are you pinging (and printing) by name or IP address? If it's by name, how is it being resolved, and is that part working?

Annihilannic.

 

[masinc1]

We are pinging by both IP and name. Being resolved through the etc/hosts file and that is working for the workstations, but not the printer - 5.0.7 can ping the workstations. I believe all the subnet masks are the same, but I will double check. I had to bring the system down and will not get back to it for a few hours. I appreciate your response.

 

[motoslide]

I haven't seen (nor heard of) the Marvel NIC.
When you configured BOTH cards, did each have seperate class of IP address?
Please post the results of these commands:

hwconfig -h
ifconfig -a
netstat -rn
arp -a

These might help spark an idea out here for all of us.

Is there a need for both cards to be operational?

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[PHV]

For completeness, please, post also the output of ipconfig /all in the console window of a workstation able to ping the printer.

 

[masinc1]

I only need one NIC. I had never heard of the Marvell Yukon either. I installed it first because it was on the SCO certified hardware list and had SCO drivers; the Intel card was not on the SCO hardware list, although there were two similiar. Currently, I am not at the system site, but will post results later today. Thank you for your response.

 

[masinc1]

#hwconfig -h
device address vec dma comment
====== ======= === === =======
Kernel - - - rel=3.2v5.0.7 kid=2003-02-18
cpu - - - unit=1 family=15
cpuid - - - unit=1 vend=GenuineIntel tfms=1:15:4:10 (0)
fpu - 13 - unit=1 type=80387-compatible
pci 0xcf8-0xcff - - am=1 sc=1 buses=8
PnP - - - nodes=0
clock - - - type=TSC/2.992499949Ghz
console - - - unit=vga type=0 12 scoansi=1 scroll=50
adapter 0xac00-0xacff 10 - type=ad160 ha=0 slot=0 bus=0 id=7 fts=sto
adapter 0xb000-0xb0ff 3- type=ad160 ha=1 slot=0 bus=0 id=7 fts=sto
floppy 0x3f2-0x3f7 6 2 unit=0 type=135ds18
kbmouse 0x60-0x64 12 - type=Keyboard mouse|PD/2 mouse (wheel) id=0x03
parallel 0xbc80-0bc82 11 - unit=3
parallel 0xcc80-0xcc82 2 - unit=0
udi - - - UDI environment
adapter - - - ha=0 type=usb_msto UDI SCSI HBA
adapter 0x1fo-0x1f7 14 - type=IDE ctlr=priMARY dvr=wd
mrvl - 10 - Marvell Yukon Ethernet Controller 7.12.3.3
eeG0 0xec80-0xec9f 10 - type=PRO/1000
:04:23E:9C:48
cd-rom - - - type=IDE unit=0 ctlr=pri cfg=mst dvr=Srom->wd
tape - - - type=S ha=0 id=8 lun=0 bus=0 ht=adl60 unit=0
disk - - - type=S ha=0 id=0 lun=0 bus=0 ht= adl60 unit=0
Sdsk - - - cyls=8924 hds=255 secs=63 fts=stdb
Sdsk-0 - - - Vnd=SEAGATE Prd=ST373207LW REV=0005
usb_ehci - 5 - PCI bus=0 dev=29 func=7
usb-uhci - 10 - PCI bus=0 dev=29 func=0
usb-uhci - 3 - PCI bus=0 dev=29 func=1
usb-uhci - 15 - PCI bus=0 dev=29 func=2

# ifconfig -a
net1: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.199.120 netmask ffffff00 broadcast 192.168.199.255
perf. params: recv size: 32768; send size: 32768; full-size frames: 1
ether 00:04:23:de:9c:49
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
perf. params: recv size: 57344; send size: 57344; full-size frames: 1
atl0: flags=404a<BROADCAST,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 0.0.0.0 netmask ff000000
perf. params: recv size: 4096; send size: 8192; full-size frames: 1

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 2 0 lo0
192.168.199 192.168.199.120 UC 1 0 net1
192.168.199.120 127.0.0.1 UGHS 1 0 lo0
192.168.199.125 192.168.199.120 UGHS 0 0 net1
224 192.168.199.120 UCS 0 0 net1

# arp -a
? (192.168.199.255) at (incomplete) (802.3)

ipconfig /all
Windows IP Configuration Host Name . . . . . . . . . . . . : TOWER2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ethernet NIC Physical Address. . . . . . . . . : 00-16-EC-71-90-8C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.199.101 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.199.1 DNS Servers . . . . . . . . . . . : 216.107.93.8
165.873194.244

 

[motoslide]

One thing I don't understand is that the MAC address of your Intel(?) adapter is 1 off between the "hwconfig" report and the "ifconfig" command. That seems very odd.
If you don't need both adapters enabled, I'd remove the MARVEL using "netconfig", then disable it in BIOS.
(I just re-read your first POST and you state this adapter doesn't show in "netconfig")

I don't know if the Intel has the option to modify it's MAC address, but this seems suspect. If the JetDirect maintains an IP/MAC Address mapping (arp), this could explain why it doesn't respond to a PING request.
You should also try setting the SCO's default gateway to 192.168.199.1

Sorry I couldn't be of more help. Anybody else have some ideas?

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[masinc1]

Thanks - I will use your suggestions and report back.

 

[masinc1]

I removed the Marvell Yukon card and now the Intel NIC does not have varying MAC addresses. I loaded the latest Intel PRO 1000 driver from SCO web site. I am using lpn, not lpr - if I am correct lpn is for printers on a network node and lpr for printers on another computer. The printer is HP laserjet 2300 w/ a jetdirect 600N, J3110A. Removed and reinstalled the printer - problem remains the same.

 

[motoslide]

I've not heard of "lpn".

I think I would start over on the printer configuration part of this exercise. You can leave whatever you currently have alone, but lets add a new logical printer entry for that printer: (IP and printername are examples)

Add an entry in /etc/hosts:
192.168.1.101 p7 # HP2300 printer

Run this command:
#/usr/lib/hpnp/hpnpcfg
Only use Option6 on that menu.

Please enter selection: 6
Enter the lp spooler destination name: p7
Enter the network peripheral name (default=p7): p7
Enter model script name: ('*' to see choices ) HPLaserJet

Let it create the printer queue, then exit.
Try printing using the standard "lp" command:
# lp -dp7 /etc/hosts

Are you still unable to get a PING response? You might try disabling some of the extra network protocols on the JetDirect (if they aren't required), such as Ethertalk, DLC/LLC, and IPX/SPX.


"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[masinc1]

Well some success!!! Followed your instructions. SCO now pings printer but does not print to printer. Turned printer off/on; verified configuration page; returned to /usr/lib/hpnp/hpnpcfg and used the test print option - Test returned: Printer test failed. Add scosysv.<NETWORKNAME>.com to printer access list.

 

[motoslide]

It doesn't surprise me that the TEST PRINT option on hpnpcfg fails. That utility was a kludge at best and was really meant to be run on an HPUX box. That's why I only run Option-6.
You should be able to telnet to the printer and view the configuration info. You should also be able to telnet to the printer on port 9100 and what you type should print.

HPNP sends an SNMP query before submitting the job. If the response isn't received, the print jobs will not spool. You can check SCO's site for "workarounds" for that symptom, or you can switch from HPNP to NETCAT. There are a few HP's which don't do well with either of these protocols and they must be configured with LPD (which I use only as a last resort).

I'd see if you can bypass the spooler and telnet to the device: (IP is only example)

# telnet 192.168.1.101 9100
What you type here should hit the paper
Cntl-]
#

Let me know if you can't find NETCAT. I'm sure I have it lying around here somewhere.


"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[PHV]

Have a look here:

http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[masinc1]

Telnet returns: telnet: socket: protocol not supported.

...much thanks for your time with this.

 

[motoslide]

Running out of ideas over here. This beast just doesn't want to communicate. It's not a HOST version of the O/S, right?
Check out the link below. It might help.

http://www.sco.com/ta/107687

Are you able to telnet into any other device? Do you get the same "protocol not supported" error if you telnet without the "9100" port specification? Can the SCO box telnet to itself?





"Proof that there is intelligent life in Oregon. Well, Life anyway.