ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: new telnet failed  (Read 1577 times)

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« on: November 16, 2004, 01:07:49 pm »

Version 5.1.25
windows xp client
windows 2k server

I'm having an issue getting a new client to connect.  I believe I upgraded the license server correctly and all that jaz.  I have read through 99% of these topics and didn't find anything to help me with my situation.

When I tried to connect via telnet I get a time out and when I check the ssh box I get a pop up msg stating that "new telnet failed"  I can't find anything that points me in any directions.  Could someone give me a hand. It would be much appreciated.

also the old clients that were running can not connect now either.

Thanks

Nic
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
Re:new telnet failed
« Reply #1 on: November 16, 2004, 01:29:37 pm »

after looking agian at it.

the install errors I get are none things look fine.
I was mistaken about the time out thing.   no matter which I try and connect with I get the net telnet failed pop up.

This is a fresh install of the client on the xp machine under.  I also installed it on a 2k machine and gets the same errors.
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
new telnet failed
« Reply #2 on: November 16, 2004, 02:09:30 pm »

What version of windows?
Can you connect with windows telnet??
Try changing the port to 23 (type it into the port box). Don't use ssh unless you have an sshd daemon on your server.

Are you saying clients with versions older than 5.1.25 cannot connect either?? That would point to a network problem.
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #3 on: November 18, 2004, 09:19:31 am »

I'm trying to run it on an xp and 2k neither works.  Yeah older ones do not talk to it that once did. and i cannot get any connectivity with it. I can not telnet to it, I can not ping it.  The nic is plugged in and the light is on the nic (green)  It's not used too much and there has been some power issues.  Perhaps the nic went south?  I'm trying to take a look at the traffic on the network from it and I don't see anything at all.  Also I'm seeing that only two of the 3 hdds in it have green lights. It's an old compact proliant 1500.  I'm going to check out what it looks like with a monitor hooked up to it.

Thanks for the help.
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #4 on: November 18, 2004, 10:23:56 am »

HAHA, it was more than just a network issue.  It was a couple issue such as incorrect documentation for it.  and the fact that the OS didn't boot all the way b/c it needed user interaction b/c of the the hdd problem.  Users can now get into it.  I just need to now get the printing issues figured out.  Things have change so much since the days of this behemath.

Thanks agian for your help if you can point me in a direction of some good printer FAQs or posts that would be great..
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
new telnet failed
« Reply #5 on: November 18, 2004, 10:28:57 am »

There are many possible methods of printing with unix in combination with ICE. Which are you using?

You could be getting printouts on the unix spooled printer or
Via pass through printing to Pro and a windows printer or
Via LPR/LPD to a networked printer from the unix machine or
Via Icelp to a windows printer or
some combination of the above.

Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #6 on: November 18, 2004, 10:39:39 am »

Uhmm I'm really not sure because this is the first time I have worked with ICE.TCP.  I would like to use the easiest to set up and for the user to interact with.  So any recommandation would be of great help. thanks.  You know what your doing with it a whole lot more than I do.  ;D
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
new telnet failed
« Reply #7 on: November 18, 2004, 10:49:12 am »

Well it depends on what application you are running on the unix machine, what kind of printing it supports and where you want to get it to print.
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #8 on: November 18, 2004, 10:58:56 am »

Uhmm well there are really only two users that are using the system right now. And it's a sco openserver 5.  It's a really really really old box that doesn't have some of the nice new features like tab complete and stuff.  It's some sort of medical thing.  but they just print to one of two printers at x.x.x.44 or x.x.x.36.  I'm not sure how the preconfigured client is working, but she's out to lunch right now.  I'll check her's out.

Thanks agian.
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #9 on: November 18, 2004, 11:21:50 am »

Well I just looked at the other one and well she couldn't really printer either. the only thing that she could print was the screen from going File->print then selecting the printer.

It looks like the application is trying to use LPR to print straight to the printers.  I hope this helps.  Thanks so much.
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
new telnet failed
« Reply #10 on: November 18, 2004, 11:45:20 am »

What kind of things does the application print? reports, etc??
Was it printing before and then stopped working or are you trying
to get printing going for the first time??

Is the app: Medical Manager??

On the SCO box you can check the configured printers (the spooled ones anyway) by doing an

lpstat -t

Post back the results. BTW, you can get a better shell for SCO, called bash. It's just like the linux version.

http://www.sco.com/skunkware/

the openserver stuff is at:

ftp://ftp2.sco.com/pub/skunkware/osr5/vols/
« Last Edit: November 18, 2004, 12:23:58 pm by Bob »
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #11 on: November 18, 2004, 11:57:43 am »

Well they need to print reports.
Yes it is Med Manager.

When I ran the  command and I got this:
[smi8660-root] /etc> lpstat -t
NCIPC_COLOR_1:
                queuing is enabled
ncipc_591: No route to host
connection to NCIPC_COLOR_1 is down
ncipc_591: No route to host
couldn't connect to printer 'NCIPC_COLOR_1'hp5nurse2:
                queuing is enabled
nurse2hp5: No route to host
connection to nurse2hp5 is down
nurse2hp5: No route to host
couldn't connect to printer 'hp5nurse2'okidata_591:
                queuing is enabled
smi8660.cfhc.com: waiting for okidata_591 to come up
Req-Id                  Owner           Size     Date
okidata_591-719         ***             984      Nov 18 09:53

okidata_591: No route to host
connection to okidata_591 is down
ncibill_laser:
                queuing is enabled
ncibill_laser: No route to host
connection to ncibill_laser is down
ncdata:
                queuing is enabled
ncdata: No route to host
connection to ncdata is down
scheduler is running
no system default destination
device for OKIDATA_LASER: /dev/null
device for okidata_591: okidata_591@okidata_591
device for patty_ink: /dev/patty_ink
device for ncipc_591: /dev/null
device for laser_5p_1: /dev/null
device for laser_5p_2: /dev/null
device for OKILASER: /dev/null
device for ncins: /dev/ncins
device for NCIPC_COLOR_1: NCIPC_COLOR_1@NCIPC_COLOR_1
device for minolta: /dev/null
device for okidata_INS: /dev/null
device for ncipc_hp5: /dev/ncipc_hp5
device for drs01: /dev/null
device for pedshp5: /dev/ncipc_hp5
device for peds_hp5: /dev/null
device for bus_laser: /dev/null
device for hp5nurse2: hp5nurse2@nurse2hp5
device for drs02: /dev/null
device for drs03: /dev/null
device for nurse1hp5: /dev/null
device for ncibill_laser: ncibill_laser@ncibill_laser
device for hp1200: /dev/null
device for ncdata: ncdata@ncdata
device for cfhc_nurse1: /dev/null
OKIDATA_LASER accepting requests since Tue Apr 25 09:17:53 2000
okidata_591 not accepting requests since Wed Jan 12 10:56:09 2000 -
        new destination
patty_ink accepting requests since Tue May 04 11:06:07 1999
ncipc_591 accepting requests since Mon Jan 18 14:22:51 1999
laser_5p_1 accepting requests since Mon Mar 29 15:19:33 1999
laser_5p_2 accepting requests since Wed Nov 12 20:42:41 1997
OKILASER accepting requests since Tue Dec 23 10:52:33 1997
ncins accepting requests since Wed Jun 20 12:52:44 2001
NCIPC_COLOR_1 not accepting requests since Mon Jan 18 13:25:49 1999 -
        new destination
minolta accepting requests since Fri Apr 07 15:03:00 2000
okidata_INS accepting requests since Wed Aug 11 10:24:03 1999
ncipc_hp5 accepting requests since Fri May 14 09:51:52 1999
drs01 accepting requests since Mon Apr 03 13:41:11 2000
pedshp5 accepting requests since Thu Jun 24 10:09:40 1999
peds_hp5 accepting requests since Thu Jun 24 10:12:02 1999
bus_laser accepting requests since Tue Aug 10 11:32:06 1999
hp5nurse2 not accepting requests since Mon Apr 03 13:41:10 2000 -
        new destination
drs02 accepting requests since Mon Apr 03 13:41:39 2000
drs03 accepting requests since Mon Apr 03 13:41:56 2000
nurse1hp5 accepting requests since Mon Apr 03 15:13:53 2000
ncibill_laser not accepting requests since Wed Sep 12 11:14:54 2001 -
        new destination
hp1200 accepting requests since Fri Oct 19 10:33:03 2001
ncdata not accepting requests since Mon Apr 01 10:17:50 2002 -
        new destination
cfhc_nurse1 accepting requests since Mon Apr 01 10:17:51 2002
printer OKIDATA_LASER now printing OKIDATA_LASER-130566. enabled since Tue Apr 25 09:17:53 2000. available.
printer okidata_591 is idle. enabled since Tue Aug 14 08:53:56 2001. available.
printer patty_ink is idle. enabled since Tue May 04 11:06:07 1999. available.
printer ncipc_591 is idle. enabled since Mon Jan 18 14:22:51 1999. available.
printer laser_5p_1 is idle. enabled since Mon Mar 29 15:19:33 1999. available.
printer laser_5p_2 is idle. enabled since Wed Nov 12 20:42:41 1997. available.
printer OKILASER is idle. enabled since Tue Dec 23 10:52:33 1997. available.
printer ncins is idle. enabled since Tue Aug 14 08:58:43 2001. available.
printer NCIPC_COLOR_1 is idle. enabled since Tue Nov 16 12:00:57 1999. available.
printer minolta is idle. enabled since Fri Apr 07 15:03:01 2000. available.
printer okidata_INS is idle. enabled since Wed Aug 11 10:24:03 1999. available.
printer ncipc_hp5 now printing ncipc_hp5-130571. enabled since Tue Aug 14 08:42:19 2001. available.
printer drs01 is idle. enabled since Mon Apr 03 13:41:11 2000. available.
printer pedshp5 is idle. enabled since Thu Jun 24 10:09:41 1999. available.
printer peds_hp5 is idle. enabled since Thu Jun 24 10:12:03 1999. available.
printer bus_laser now printing bus_laser-130569. enabled since Tue Aug 10 11:32:07 1999. available.
printer hp5nurse2 disabled since Mon Apr 03 13:41:10 2000. available.
        new printer
printer drs02 is idle. enabled since Mon Apr 03 13:41:39 2000. available.
printer drs03 is idle. enabled since Mon Apr 03 13:41:56 2000. available.
printer nurse1hp5 is idle. enabled since Mon Apr 03 15:13:53 2000. available.
printer ncibill_laser disabled since Wed Sep 12 11:14:54 2001. available.
        new printer
printer hp1200 is idle. enabled since Fri Oct 19 10:33:03 2001. available.
printer ncdata disabled since Mon Apr 01 10:17:50 2002. available.
        new printer
printer cfhc_nurse1 is idle. enabled since Mon Apr 01 10:17:51 2002. available.
OKIDATA_LASER-130566    ***              16592   Nov 20 15:25 on OKIDATA_LASER
bus_laser-130569        ***               1015   Nov 18 09:54 on bus_laser
bus_laser-130570        ****          26537   Nov 18 10:22
ncipc_hp5-130571        ****         13019   Nov 18 10:39 on ncipc_hp5

I just hate Old OSes.

Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
new telnet failed
« Reply #12 on: November 18, 2004, 12:26:54 pm »

Yow, that machine has a LOT of defined printers!

We are going to need to find out how they are SUPPOSED to be printing. Check to see if icelp is running on the client PC(s). If it is, check the printing configuration in the active profile. If it isn't, I assume MM is using pass-thru printing. Is there any way you can find out the printing configuration of  MM?? We are pretty much working in the dark without it.
Logged

nic

  • Jr. Member
  • **
  • Posts: 9
  • Place Personal Text Here
new telnet failed
« Reply #13 on: November 18, 2004, 01:15:45 pm »

Yeah I can found out what the print config is.  I think. I got admin access :-D.
I don't see a icelp running on the client.  BUT this is the first time in like 6 years they needed to print something besides a screen.

See why I'm having a bit of an issue with the printer stuff.  And the sad part of it is that they are all set to some old network that was using public IP's in a private network that we switched from a long time ago.

I'm more fermilar with BSD than SCO and SCO more than MM.

Thanks for all your help.  It means a lot.
Logged
 

Page created in 0.01 seconds with 21 queries.