Conference decwet::windows-nt

5691.0. "lps17 remote load" by MEOC02::DWYERMICHAEL () Wed Feb 12 1997 18:07

      Hi
    
    This is an update to a problem I had unsolved over a month ago. It is
    still a problem that needs resolution immediately. See note 5422. I
    have more info. I repeat some of the words and add more :
    
        I recently installed V51-11I.EXE;1 kit onto an -NT (3.51)Alpha
    server in
        order to load a LPS17/600 in a local subnet. Worked fine using the
        wizard etc.  Prints great.
    
        Problem : Moved the same LPS17 to a remote (different) subnet
    across a pair
        of Ciscos (IGS + 4000 V10.x) via a serial line .
    
        Reconfigured the wizard for the printer's new address and
        subnet with the printer's local Cisco (gateway) address as the
    gateway
        parameter, enabled IP helper on the two  Ciscos for broadcast
    address ie in both directions the helper address is the local bcast so
    the -NT box sees the bootp as a broadcast (previously only had one
    helper enabled and that was to the server's address only.
    
        The LPS17 now loads by bootp to the stage of the LCD showing 
    VAXELN V4.5 LPS17 
    but doesn't go any further - it will not load the secondary boot config
    files. Still Boots  locally OK. 
                 
    I can see the TFTP blocks being loaded into the LPS17 OK by a sniffer
    and the parameters being passed to the LPS17 from the bootp reply include:
    
    self assigned IP address - 0 OK
    server assigned IP address - 203.0.242.10 OK
    server IP address - 203.0.233.9 - OK
    Gateway IP address -203.0.242.1 - OK
    vendor info  - ..
    subnet mask - 255.255.255.0 - OK
    Gateway address (again ?) - 203.0.242.1  - OK ??? this is duplicated
    client HW - LPS17
    Host name - EHCN 9
    Boot file - 3
    These parameters were loaded into the LPS17 by the first TFTP (1406
    blocks)
     After loading the first blocks I can ping the LPS17 (.242.10) locally
    OK but cannot across the routers. SO I think it hasn't reacted to its
    gateway address that was loaded via the tftp.
    
    I can ping from the server any attached devices on .242.x LAN so it has
    a path to the remote subnet where the LPS resides.
    
    The LPS attempts a seond round of bootp after the first but the -NT
    doesnt respond. Should it ? The -NT attempts a TCP connection to the
    LPS17 but doesnt see it as the LPS17 doesn't have a gWay configured ??
    
    I include the -NT log file (copied manually). 
    . 
    Any ideas ??
    
    
            Timeout waiting for connection
    02/04/1997 12:25:41 Mgmt Client: Mgmt connection to PR-FRED timed out,
    retrying
    in 2 seconds
    02/04/1997 12:25:43 Mgmt Client: Opening control channel to
    203.0.242.10
    02/04/1997 12.25:43 Mgmt Client: Connecting to port 170 on 203.0.242.10
    (203.0.242.10)
    02/04/1997 12:26:15 bs: ProcessRequest: client ethernet address:
    08-00-2b-9f-9c-f1
    02/04/1997 12:26:15 bs: ProcessRequest: specifying filename "3"
    02/04/1997 12:26:16 bs: DoCommandA: arp-d 203.0.242.10 203.0.233.9
    02/04/1997 12:26:16 ts: ProcessRequest
    02/04/1997 12:26:16 regread: GetPrintServer: Filename: sys\lps17.sys
    02/04/1997 12:26:16 regread: GetPrintServer: Root path: C:\WIN32APP\
    DECPSMON
    02/04/1997 12:26:16 regread: GetprintServer: Full filename:
    C:\WIN32APP\DECPSMON\sys\lps17.sys
    02/04/1997 12:26:16 ts: sendfile: filename:
    C:\WIN32APP\DECPSMON\sys\lps17.
    sys
    02/04/1997 12:26:16 ts: sendfile: sent block 0
    02/04/1997 12:26:37 ts: sendfile: sent block 256
    02/04/1997 12:26:58 ts: sendfile: sent block 512
    02/04/1997 12:27:20 ts: sendfile: sent block 768
    02/04/1997 12:27:41 ts: sendfile: sent block 102402/04/1997 12:28:02
    ts:
    sendfile: sent block 1280
    02/04/1997 12:28:13 Setting reconnect & urgent flags for PR_FRED
    02/04/1997 12:28:15 Mgmt Client: interrupting connect to 203.0.242.10,
    urgent
    event waiting
    02/04/1997 12:28:15 Mgmt Client: Couldn't connect to server PR_FRED
            Callback function returned TRUE
    02/04/1997 12:28:15 Mgmt Client: Unexpected error while establishing
    mgmt
    session to PR_FRED
    02/04/1997 12:28:15 Mgmt Client: Unable to establish mgmt session to
    PR_FRED
    02/04/1997 12:28:15 Mgmt Client: Resetting connection to PR_FRED...
    02/04/1997 12:28:15 Mgmt Client: MSSN message for PR_FRED is:
    PASSWORD=lpsv51'HOST=ehcn9'CFREAD=1'FILEIO=1'ACCOUNT=0'PRINTERHOST=203.0.
    242.10'
    CLIENTID=V5.1'PROTOCOL=V2.1'KEEPALIVE=2
    02/04/1997 12:28:15 Mgmt Client: Opening controlc channel to
    203.0.242.10
    02/04/1997 12:28:15 Mgmt Client: Connecting to port 170 on 203.0.242.10
    (203.0.242.10)
    02/04/1997 12:28:17 bs: ProcessRequest: client etherent address:
    08-00-2b-9f-9c-f1
    02/04/1997 12:28:17 bs: ProcessRequest: specifying filename"3"
    02/04/1997 12:28:17 bs: DoCommandA: arp -d 203/0/233/9
    02/04/1997 12:29:06 StartDocPort() -- Tue Feb 04 11:29:06 1997
          printer=PR_APERUSE
    02/04/1997 1229:06 StartDocPort:
            PrintServer flag: 0
            DEClaser TCP/IP flag: 1
            RapidPrint TCP/IP flag: 0
    
    
    Thanks Michael