| View previous topic :: View next topic |
| Author |
Message |
arand
Apprentice
Joined: 22 Apr 2003
Posts: 215
|
 Posted: Fri Oct 01, 2004 2:03 pm Post subject: Fake Hostename |
 |
|
I am trying to set up an nfs share between my two gentoo computers. How ever I have run into a problem with my universities router (I think its the uni's router).
Heres the info, when I try to connect ot the server machine with the remote, this shows up in the servers logs.
| Code: | Oct 1 21:43:56 [rpc.mountd] Fake hostname netXXX-XXX.ssme.eng.tohoku.ac.jp for 172.XXX.XXX.XXX - forward lookup doesn't exist
Oct 1 21:43:56 [rpc.mountd] refused mount request from 172.XXX.XXX.XXX for /usr/portage/distfiles (/): no export entry |
And obviously the client machine says,
| Code: | mount -t nfs 172.XXX.XXX.YYY:/usr/portage/distfiles /usr/portage/distfiles/
mount: 172.XXX.XXX.YYY:/usr/portage/distfiles failed, reason given by server: Permission denied
|
When I try adding the fake host name I get this,
| Code: | * Starting NFS statd... [ ok ]
* Exporting NFS directories...
exportfs: netXXX-XXX.ssme.eng.tohoku.ac.jp has non-inet addr
exportfs: netXXX-XXX.ssme.eng.tohoku.ac.jp has non-inet addr [ ok ]
* Starting NFS daemon... [ ok ]
* Starting NFS mountd... [ ok ]
|
Also I cannot ping the machine using the odd host name so I am not sure what do do.
Oh here is the /etc/exportfs
| Code: | # /etc/exports: NFS file systems being exported. See exports(5).
/usr/portage/distfiles/ 172.XXX.XXX.XXX(rw,async)
/usr/portage/distfiles/ netXXX-XXX.ssme.eng.tohoku.ac.jp(rw,async)
|
and /etc/hosts.allow
| Code: |
ALL: 172.XXX.XXX.XXX, netXXX-XXX.ssme.eng.tohoku.ac.jp |
Thanks |
|
| Back to top |
|
 |
Tsonn
Guru
Joined: 03 Jun 2004
Posts: 550
|
| Posted: Fri Oct 01, 2004 3:30 pm Post subject: |
|
|
It sounds like your university is using addresses internally which aren't valid on the internet. This is perfectly normal practice... for example, on a LAN you might use 192.168.0.x. The computers will still be able to connect to the internet via a NAT box, but will report their address to anyone who asks as 192.168.0.x.
There's not much you can do about that directly... you could either relax security on the server so it doesn't do that check, or give ssh tunnelling a try. I believe this is the right command:
| Code: |
ssh -L <port nfs uses>:<hostname of server>:<port nfs uses> <username>@<hostname of server>
|
Then on the client you connect to localhost, and the server sees a connection from localhost.
_________________
If your question was answered, please edit the first post and add [SOLVED] to the title. Thanks! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
