| Title: | Digital PostScript printers and their associated software |
| Moderator: | REGENT::LASKO HER |
| Created: | Wed Jan 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7230 |
| Total number of notes: | 31971 |
Hi
I have a problem with an LPS17 being loaded across a pair of ciscos by
a win-nt server. Basically the LPS17 loads the primary boot code by
tftp from the server, comes back with VAXELN V4.5 LPS17 on the LCD
panel but will go no further. I can ping its address locally but not
across the WAN. I can ping devices on either lan from the other LAN
thus the routers are OK and the default gways of the server seems to be
ok. AM using IP helper address (Cisco) of all 1's
in both directions. The tftp load is fine, the secondary bootp request
from the LPS is ignored by the WIN-NT box and the NT box attempts a TCP
connection but fails as it looks as though the LPS17 is not making use
of the default GWAY address loaded with the primary bootp relpy and TFTP
I have cross referenced it in DECWET::WINDOWS-NT conference note 5691.
See there for a more detailed description if you can help.
Thanks
Michael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7078.1 | LPS printers need that second bootp reply | NECSC::HARVEY | Printserver Support- America's Zone | Thu Feb 13 1997 11:17 | 9 |
Michael,
That second bootp from the printer is where the printer gets its
ip address, subnetmask and gateway information. The printer doesn't
have dynamic ip routing so its critical that the correct gateway
address is given the printer. Is the gateway address the ip address of
the routers interface on the subnet that the printer is on?
Renis
| |||||
| 7078.2 | they are in the first bootp reply ?? | MEOC02::DWYERMICHAEL | Thu Feb 13 1997 16:13 | 21 | |
Hi Renis,
On the sniffer I saw the first bootp reply from the -NT box arrive at
teh LPS17 after the FIRST
bootp req from the LPS17 have as its bootp parameters the correct
gateway address that the LPS17 sees on its local LAN and its IP address
that the server sends it. They seeem OK. The LPS17 then sends out another
bootp req
after it has its VEAXELN code loaded but thereafter nothing happens.
The -NT doesn't reply to the second bootp req (it seems ?).
I am able to ping the LPS locally after it
stops the boot process (hangs), but am not able to see it from another subnet,
even though I can ping across to the routers to/from other devices.
Can I refer you to the -NT notes file (DECWET::mindows-nt) note #5691
for more info . Maybe that will assist ?? Not ethe parameters I have
included as the bootp reply from the -NT.
Thanks
Michael
| |||||