From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Will Message-ID: <66615df7.0301151215.1945a119@posting.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: [9fans] Trouble connecting to and/or bringing up auth server Date: Thu, 16 Jan 2003 09:47:05 +0000 Topicbox-Message-UUID: 4256e42c-eacb-11e9-9e20-41e7f4b1d025 I'm new to Plan 9 and have been working on bringing up a CPU server that also runs as an auth server. This is all under VMWare, althought that doesn't seem to be causing a problem. CPU server kernel successfully built following the docs in the the wiki. Net configured following the docs in the wiki as well. Using two (virtual) machines one configured as a terminal, the other as cpu and auth server. IP addresses are fixed and domain name resolution seems OK. Telnet and ftp work fine other machines, that is, linux and windows. On the cpu machine, auth commands, e.g. changeuser, wrkey, etc seem to execute OK and show messages in the log. I do have warnings in the auth log about keyfs starting. Examination of /net/il and /net/tcp shows ports 566 and 567 respectively in listen mode. The optional parameter on ip/ipconfig was used in cpurc and termrc on the respective machines to set the address of the auth server and verified in /net/ndb. auth/wrkey was used to set, as I understand it, the auth domain to willnet. Upon issuing the cpu command on the terminal the following message returned: cpu: can't authenticate: glenda: auth_proxy rpc write: bootes: no auth server found for willnet Upon issuing a telnet to the cpu machine to following message was returned: authentication failure: auth server protocol botch glenda really is the cpu machine. bootes really is the authid used in the wrkey command. Folks, I'm sure I've screwed up something simple and probably don't clearly understand the ins and outs of the setup. It seems like it's almost there and just needs a tweak or two. Thanks for any help in advance. Will