RSH - printing Not working

[TWBSupport]

We have a new office location. I have set them up so network traffic works fine, however, we use a horrible ERP system that MUST use RSH on hpux. The offices have XP w/the RSH version we use and they connect to our unix server to access the ERP. I have set up several remote offices and never had a problem with RSH getting through, until now. I get the following error from the remote plant when trying to print via RSH:
Socket Error(accepting stderr connection) -10060
Connection Timed Out.

Any advice would be greatly appreciated. Thank you.

[TWBSupport]

it would probably help if I gave you the hpux version... sorry about that.. got click happy.

11i

[skt_skt]

is there a print queue defined on the UNIX side?

Could u explain how the rsh works to print?

[TWBSupport]

Yes, there is a print queue on the server side set up exactly like all the other remote printers.

I'll be honest with you, I really don't know how the RSH works for this application. I just know that this application only works with RSH (per dba and programmers).

But maybe we can start troubleshooting with just trying to login from the remote site via rsh, I get the same error.

So, this has to mean it has something to do with rsh? The remote user can log into the application with no problems, ping it, it's just when I try to rsh from a command line on the remote users desktop, I get the error as well as when they try to print out of the application.

[TWBSupport]

one more thing. I can print to this printer (remote site) from the corporate location. The remote site can not print to this printer from their location, which the printer is sitting in the remote location. So it seems the printer is setup properly, but something is not forwarding the proper information from remote site to server site (corporate site).

[Pete Randall]

I'm assuming maybe rsh is actually what is referred to as remsh (remote shell) on HP-UX. Other OS's refer to it as rsh, which, in HP-UX, refers to the restricted shell.

Anyway, if we are indeed talking about the remote shell, you need to have either /etc/hosts.equiv or a .rhosts file set up in order for your new location to connect. Check to see if you have a /etc/hosts.equiv file and add the new office server's name to it if you do. If you don't, then you probably have a file called .rhosts located in the user's home directory and you need to add the server name to that file.


Pete

[TWBSupport]

hosts.equiv is ++

.rhosts has nothing in it, but my previous remote sites never needed anything in them.

I added the server name as well as ip address (in case there is a dns issue)to the user .rhosts file and same error.

[David Bellamy]

Denda are you issuing the command as rsh or as remsh ?

[TWBSupport]

I'm using rsh.

[David Bellamy]

use remsh

[TWBSupport]

What is the command line for the remsh? When I type in remsh hostname OR remsh ipaddress, it comes back with 'unrecognized command'. If I use my rsh command, the server confirms that it received it.

[David Bellamy]

my mistake rsh is for the Windows systems, remsh would be used on a HPUX system.

[Patrick Wallek]

What operating system are you issueing the rsh command from? Is it windows? If so, then Windows uses rsh.

If you were issueing the command on the HP-UX machine, then you would use 'remsh', but I don't think you are doing that.

You are rsh'ing from Windows to HP-UX? Is that correct?

[TWBSupport]

Yes, I am issuing rsh from a windows xp system. I'm sorry, I should have been more descriptive.

[TWBSupport]

So, to add on to the last post..

I execute rsh -l username hostname on any pc that is not at this one specific remote location and the command returns a blank command line, which tells me it found the HPUX server fine.

If I execute that same command at the remote location I get the socket error - connection timed out.

Thanks for all your help.

[TWBSupport]

Ok - I've got a little more info. After uninstalling the sorry monitoring tool I was using, I installed wireshark. Wireshark shows the client accessing the server and when it tries sending the RSH packet, a checksum error comes up. Every time I do this, the checksum error comes up so it is consistent. Another thing Wireshark states after the error is "maybe caused by tcp checksum offload?" Anyone ever had something like this going on?

[TWBSupport]

Well, forget that. It was just something with wireshark. Granted the error did not happen on the good client, only on the bad. Once I made a preference change on the bad client, it no longer gets the error either, but it also just gets one packet of RSH client to server and nothing more, whereas on the good client, I rec'd about 4 lines of the process. UGH.. back to the drawing board.

[TWBSupport]

ok, I'm getting closer, HOPEFULLY... On the 'good client'... prior to the RSH traffic, the system and the server exchange giFT communication. This does not happen on the 'bad client'.