</whine>
Okay, I know this has been hashed out before, but while you-all (okay,
*most* of you-all) were enjoying yourselves in Chicago, I was working
76 hours a week getting the frame relay from Ohio to Texas up and running.
</whine off>
So, anyway, we bought a DTC from a third-party and while I'm waiting
for tomorrow to call their tech support, I thought I'd post it here
to see if the HP3000 gestalt mind can help me. The situation is a
918 in Ohio linked via Cisco router and frame relay to a 918 in
Texas with another Cisco router. The frame and routers are working,
at least as far as TCP/IP is concerned (I'm able to connect all of
our PC's in Texas to the 918 in Ohio - the master computer). I want
to run some spooled printers down here in Texas, so I specifically
asked the router and frame providers if they could handle (i.e.,
bridge) the HP DTC protocol (ADCP?), and of course, they said it
would be no problem. So the DTC finally arrives (only took a week!),
I hook it up via 10Base2 (now here's an oddity, the DTC has an AUI
port, not a coax connector, so I got a transceiver and connected
that between the AUI and the coax), I configure the new DTC in NMMGR
(on the machine in Ohio), and tell MPE to make the changes effective
immediately, which it does (I can see the DTC in TERMDSM of SYSDIAG).
However, RESET of this DTC (via TERMDSM/SYSDIAG) gives me a timeout
waiting for the DTC to respond, in other words, it can't "see" the
DTC. I double checked the new DTC's LAN address and it's correct.
So, I don't need to reboot the machine in Ohio, do I? I can reboot,
but it will be tomorrow evening.
Or, is there something wrong with the network?
Or, is the DTC bad?
Or, did I really screw this up?
Awaiting any and all responses. And hey, it's on topic, unlike the
science versus religion debate. :-)
Jim Phillips Manager of Information Systems
Voice: (915) 860-9933 Therm-O-Link of Texas, Inc.
Fax: (915) 860-9936 1295 Henry Brennan
Email: [log in to unmask] El Paso, Texas 79936
|
