On Mon, Nov 15, 2004 at 04:03:04PM +0100, Caloro Maurizio wrote:
> Hello everyone,
> 
> i have two pc's one with Netbsd 1.6.2 x86 and integrated dat drive 
> (mt -f /dev/rst0 rewind (on netbsd machine working fine))
> 
> the second machine has solaris x86, now i try to backup the following
> slice="/dev/dsk/c0t0d0s6" over network to my netbsd machine to this dat
> drive
> 
> here my try :
> 
> # ufsdump 0fcu Pluto:/dev/rst0 /dev/dsk/c0t0d0s6
>   DUMP: pluto: Connection refused
>   DUMP: Cannot connect to tape host `pluto'
>   DUMP: The ENTIRE dump is aborted.

The connection refused part is what you need to work on.  Is rshd
enabled on pluto?  Check /etc/inetd.conf, it is probably commented out,
uncomment it, and kill -HUP inetd's PID.

You can test this by using rsh:

solaris# rsh pluto uname -a

If you get the answer you're looking for, you're golden.

> and here me .rhosts and hosts.equive file on my netbsd machine
> 
> #cat .rhosts
> solaris	root
> 
> #cat /etc/hosts.equiv
> solaris	root
> 
> i have read that's enought, but iam not successful 
> 
> ? and i dont know it is risk to open the machine on this way  ?
> :-);-/:-(

If both machines are properly firewalled, then you're safer than most.

To be even safer, don't do this over rsh, but over ssh.  Move the rsh
binary on your solaris machine out of the way and symlink ssh to rsh.
Then set up shared keys between the two hosts.

Once you have this all set up, you can test it in a similiar fashion as
above, just substitute ssh for rsh:

solaris# ssh pluto uname -a

In many cases, ssh can be a drop-in replacement for rsh.  With proper
key management, it is MUCH more secure.

-- 
Michael Parson
mparson@bl.org