From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrey mirtchovski To: 9fans@cse.psu.edu Subject: Re: [9fans] NAT'ing a drawterm connection In-Reply-To: <87smnlgk2l.fsf@rgristroph-austin.ath.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Date: Thu, 28 Aug 2003 22:50:12 -0600 Topicbox-Message-UUID: 256aed30-eacc-11e9-9e20-41e7f4b1d025 On 28 Aug 2003, Rob Ristroph wrote: > Suppose in your "import" command that "plan9" isn't a machine running > Plan 9 but another computer that can see the plan9 computer. Can you > forward some set of ports to make it work, or are you just out of luck > ? import expects exportfs to be running on the other side. it should be fine by just redirecting the exportfs port. if that's what you want to achieve. > client version: RFB 003.003 > [550] 192.168.1.1!4719 /net/tcp/28: auth > vncs: vncchal: auth server protocol botch in my case that usually means i've gotten the authdoms in /lib/ndb/local on the auth server wrong. can you cpu from the same machine to itself? try that with 'auth/debug' and see what's wrong. > Nothing seems to be printed in /sys/log/auth. If I run a vnc server > on linux, I have to set a password; have I not done the equivalent on > Plan 9 ? How do I do it ? you do not, vncs is smart enough to use the password already set for the user on the auth server. do you have a password set? another thing, suggested some time ago by Geoff Collyer -- cd /adm/keys on the console of the auth server and type 'ls' -- if you see valid user names for the system you're ok, of not, the nvram on the system doesn't contain the proper password to decode the password.. but: my auth server was set a few months ago, so i may be out of sync... andrey