how to connect 2 Solaris systems remotely?

Hello,

I have several Solaris x86 systems on a local network, and that works
out nicely.
I have a remote user that I'd like to connect his Solaris x86 onto my
local network,
as if he was locally connected.

I need his connection to be always on. If there are network drives
that the other
local systems see, then, his system need to see them too, and so
forth ...
Whenever he boots up, his system will need to do some network drives
mounting also.

Should I call my ISP to get this done? If so, what do I ask for?
What's involved
in terms of the configuration? Thanks.

Michelle wrote:
> Hello,
>
> I have several Solaris x86 systems on a local network, and that works
> out nicely.
> I have a remote user that I'd like to connect his Solaris x86 onto my
> local network,
> as if he was locally connected.
>
> I need his connection to be always on. If there are network drives
> that the other
> local systems see, then, his system need to see them too, and so
> forth ...
> Whenever he boots up, his system will need to do some network drives
> mounting also.
>
> Should I call my ISP to get this done? If so, what do I ask for?
> What's involved
> in terms of the configuration? Thanks.

You will need a static IP address for which there may be a substantial
extra charge. You will also need to review your contract with your ISP
to see if you are allowed to operate a server; my ISP (Comcast) does
prohibit me from operating a server using the service I have purchased.
YMMV.

You may be able to use something called Dyn DNS or Dynamic DNS which
will allow you to work around an IP address that changes every time you
reboot.

You will also need to be very careful not to allow the whole world to
get at your system and try to hack it. My router rejects three or four
attempts per minute!

On Aug 27, 7:38*pm, "Richard B. Gilbert"
wrote:
> Michelle wrote:
> > Hello,
>
> > I have several Solaris x86 systems on a local network, and that works
> > out nicely.
> > I have a remote user that I'd like to connect his Solaris x86 onto my
> > local network,
> > as if he was locally connected.
>
> > I need his connection to be always on. *If there are network drives
> > that the other
> > local systems see, then, his system need to see them too, and so
> > forth ...
> > Whenever he boots up, his system will need to do some network drives
> > mounting also.
>
> > Should I call my ISP to get this done? *If so, what do I ask for?
> > What's involved
> > in terms of the configuration? *Thanks.
>
> You will need a static IP address for which there may be a substantial
> extra charge. *You will also need to review your contract with your ISP
> to see if you are allowed to operate a server; my ISP (Comcast) does
> prohibit me from operating a server using the service I have purchased.
> YMMV.
>
> You may be able to use something called Dyn DNS or Dynamic DNS which
> will allow you to work around an IP address that changes every time you
> reboot.
>
> You will also need to be very careful not to allow the whole world to
> get at your system and try to hack it. *My router rejects three or four
> attempts per minute!

Static addresses with some form of VPN router in a peered
configuration is your most secure option if the requirement is 24/7
connectivity, although this could prove too costly, however it will
meet your stated requirements. A VPN router on your side configured
with dyndns and dynamic vpn client connectivity might be a cheaper
option, but you're forgoing the permanent link.

Note that remote Network drives/mounts performance is going to be
average to poor. If any of this is alien to you, you might want to
call in the help of some professional services.