[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Q: Connecting to remote system.
- To: email@example.com
- Subject: Re: Q: Connecting to remote system.
- From: bruce westergren <firstname.lastname@example.org>
Let's first make sure everything is setup correctly. You do not need to do the bind and start of the connection service (cs). The srv service is all you need. On the Solaris (Signer) box you need to setup a directory for your login under the usr directory and the create a keyring subdirectory. Now do the following after starting the emu: Solaris$ lib/srv Solaris$ changelogin <your login name> Solaris$ getauthinfo default Now you should be ready for remote connections. You only need to changelogin once and if you decided to save the authinfo you do not need to do this again either. Bruce Justin W. Hitt wrote: > > I have found a Sparc10 running Solaris 2.5.1, and a Win95. I am trying = > to connect these two systems using inferno, to do a little testing. I = > get the Solaris box up with ``emu'', and the following: > > bind '#I' /net > lib/cs > lib/srv > > My Win95 box can not connect to the Solaris box. I get the following on = > the Solaris box. > > New client (STYX): /net/tcp/5 126.96.36.199!1313 > bad message type in exportproc > > I can do a ``getauthinfo'' from the Win95 box (using the Solaris box as = > the Signer) and it works correctly. I can also make another emu window = > on the Win95 box, and clone the Solaris environment. This gives me a = > good connection with the remote directory tool. > > There are some network differences between the two emu sessions. The = > emu sessions on the Win95 box are using loopback, and between the Win95 = > box -> Solaris I use a dial-up line over the internet. > > If anyone knows what is going on, please let me know. > > Justin (email@example.com) > > -- > Open Systems Networking, Inc. (http://www.osn.net) =20 > voice: 301-475-8721 fax: 301-475-0324