5:06 p.m.
Hi people!
I would like to see your opinion on this matter. I am running a home lan
with two computers, one ASUS MB K8-VX SE and another K8-VX, both onboard
lan, FC6 and a radio connection with a D-Link DI-604 broadband ethernet
router. Both computers can access internet at the same time smoothly,
but they cannot see each other's shared folders. NETFS, Network, NFS,
NFSLOCK and PORTMAP services are all up and running. Even if I disable
guarddog firewall on both computers, I still cannot see shared folders.
Any hints on how to setup NFS???
--
**********************************************
* Carlos Alberto Alves *
* Rio de Janeiro, Brazil *
* mailto:drcaa@predialnet.com.br *
**********************************************
7:52 p.m.
Carlos Alberto Alves wrote:
Hi people!
I would like to see your opinion on this matter. I am running a home lan
with two computers, one ASUS MB K8-VX SE and another K8-VX, both onboard
lan, FC6 and a radio connection with a D-Link DI-604 broadband ethernet
router. Both computers can access internet at the same time smoothly,
but they cannot see each other's shared folders. NETFS, Network, NFS,
NFSLOCK and PORTMAP services are all up and running. Even if I disable
guarddog firewall on both computers, I still cannot see shared folders.
Any hints on how to setup NFS???
What does /etc/exports look like?
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
8:51 a.m.
Mikkel L. Ellertson wrote:
Carlos Alberto Alves wrote:
> Hi people!
> I would like to see your opinion on this matter. I am running a home lan
> with two computers, one ASUS MB K8-VX SE and another K8-VX, both onboard
> lan, FC6 and a radio connection with a D-Link DI-604 broadband ethernet
> router. Both computers can access internet at the same time smoothly,
> but they cannot see each other's shared folders. NETFS, Network, NFS,
> NFSLOCK and PORTMAP services are all up and running. Even if I disable
> guarddog firewall on both computers, I still cannot see shared folders.
> Any hints on how to setup NFS???
What does /etc/exports look like?
Mikkel
Hi Mikkel!
Here you are:
1- /etc/exports
/home/carlos sempron(ro)
/home/download sempron(ro)
2- /etc/hosts
127.0.0.1 localhost.localdomain localhost k6
127.0.0.1 k6 localhost.localdomain localhost
3- /etc/hosts.allow
portmap: sempron
lockd: sempron
mountd: sempron
rquotad: sempron
statd: sempron
cupsd: ALL
4- /etc/hosts.deny
lockd: ALL
mountd: ALL
rquotad: ALL
statd: ALL
This setup worked fine in a peer-to-peer network.
:(
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
10:40 a.m.
Carlos Alberto Alves wrote:
Mikkel L. Ellertson wrote:
Hi Mikkel!
Here you are:
1- /etc/exports
/home/carlos sempron(ro)
/home/download sempron(ro)
2- /etc/hosts
127.0.0.1 localhost.localdomain localhost k6
127.0.0.1 k6 localhost.localdomain localhost
3- /etc/hosts.allow
portmap: sempron
lockd: sempron
mountd: sempron
rquotad: sempron
statd: sempron
cupsd: ALL
4- /etc/hosts.deny
lockd: ALL
mountd: ALL
rquotad: ALL
statd: ALL
This setup worked fine in a peer-to-peer network.
:(
Dumb question - can this machine resolve the host name sepron?
"nslookup sepron" or "dig sepron"
Also, are there any errors in the logs when you try to connect?
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
3:02 p.m.
Mikkel L. Ellertson wrote:
Carlos Alberto Alves wrote:
> Mikkel L. Ellertson wrote:
>
> Hi Mikkel!
> Here you are:
>
> 1- /etc/exports
> /home/carlos sempron(ro)
> /home/download sempron(ro)
>
> 2- /etc/hosts
> 127.0.0.1 localhost.localdomain localhost k6
> 127.0.0.1 k6 localhost.localdomain localhost
>
> 3- /etc/hosts.allow
> portmap: sempron
> lockd: sempron
> mountd: sempron
> rquotad: sempron
> statd: sempron
> cupsd: ALL
>
> 4- /etc/hosts.deny
> lockd: ALL
> mountd: ALL
> rquotad: ALL
> statd: ALL
>
> This setup worked fine in a peer-to-peer network.
> :(
Dumb question - can this machine resolve the host name sepron?
"nslookup sepron" or "dig sepron"
Also, are there any errors in the logs when you try to connect?
Mikkel
Here is the result of hte 2 commands...
[carlos@k6 ~]$ dig sempron
; <<>> DiG 9.3.2 <<>> sempron
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56004
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;sempron. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA A.ROOT-SERVERS.NET.
NSTLD.VERISIGN-GRS.COM. 2007043000 1800 900 604800 86400
;; Query time: 232 msec
;; SERVER: 200.218.176.7#53(200.218.176.7)
;; WHEN: Mon Apr 30 16:59:39 2007
;; MSG SIZE rcvd: 100
[carlos@k6 ~]$ nslookup sempron
Server: 200.218.176.7
Address: 200.218.176.7#53
** server can't find sempron: NXDOMAIN
There is no error messages when I try to connect to the Internet and
command "mount" returns nothing.
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
4:18 p.m.
The results show that you do not get an IP address for sempron. So
when sempron tries to mount the NFS share, it is an unknown machine,
and does not have permission to mount. I would try ether putting an
entry for sempron in /etc/hosts, or editing /etc/exports and
replacing sempron with the proper IP address.
What you may want to do, if you are using DHCP on the D-link router,
is to assign fixed IP addresses to the machines using the MAC
address of the machines. I have had good luck doing this in the
past. The other thing that works well if you have a Linux box
running 24/7 is to put the DHCP server on it, as well as a local
name server, and let all the machines on the network use its name
server. There are some nice packages like dnsmasq that combine a
caching name server and a DHCP server into one package, and update
the name server to reflect DHCP leases.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
6:45 a.m.
Mikkel L. Ellertson wrote:
The results show that you do not get an IP address for sempron. So
when sempron tries to mount the NFS share, it is an unknown machine,
and does not have permission to mount. I would try ether putting an
entry for sempron in /etc/hosts, or editing /etc/exports and
replacing sempron with the proper IP address.
What you may want to do, if you are using DHCP on the D-link router,
is to assign fixed IP addresses to the machines using the MAC
address of the machines. I have had good luck doing this in the
past. The other thing that works well if you have a Linux box
running 24/7 is to put the DHCP server on it, as well as a local
name server, and let all the machines on the network use its name
server. There are some nice packages like dnsmasq that combine a
caching name server and a DHCP server into one package, and update
the name server to reflect DHCP leases.
Mikkel
Hi Mikkel!
Your idea seems the best, but the router assigns the same address for
both machines (I do not know how). I will have to talk to the ISP that
owns the router and ask them to do it.
I will let you know their answer.
TIA,
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
10:37 a.m.
Carlos Alberto Alves wrote:
Hi Mikkel!
Your idea seems the best, but the router assigns the same address for
both machines (I do not know how). I will have to talk to the ISP that
owns the router and ask them to do it.
I will let you know their answer.
TIA,
Let me make sure I understand what you are saying. The router
assigns an IP address to machine A aaa.bbb.ccc.ddd, and then also
assigns machine B the sam aaa.bbb.ccc.ddd address? If that is the
case, then the two machines will never be able to talk to each
other. For that matter, your should be running into other network
problems.
Lets double check this. On the two machines, run:
/sbin/ifconfig
The "inet addr:" for lo should be 127.0.0.1 on both machines, but
should be different for eth0 (or what ever your interface to the
router is.) If they are the same, then take a look at
/etc/sysconfig/network-scripts/ifcfg-eth0. Make sure it is not set
up for a static IP address. It may have more or less lines, but it
should look something like this: (HWADDR and DHCP_HOSTNAME for your
system or missing.)
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:02:A5:F4:91:5E
ONBOOT=yes
DHCP_HOSTNAME=mikkel
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
6:01 p.m.
Mikkel L. Ellertson wrote:
Carlos Alberto Alves wrote:
> Hi Mikkel!
> Your idea seems the best, but the router assigns the same address for
> both machines (I do not know how). I will have to talk to the ISP that
> owns the router and ask them to do it.
> I will let you know their answer.
> TIA,
Let me make sure I understand what you are saying. The router
assigns an IP address to machine A aaa.bbb.ccc.ddd, and then also
assigns machine B the sam aaa.bbb.ccc.ddd address? If that is the
case, then the two machines will never be able to talk to each
other. For that matter, your should be running into other network
problems.
Lets double check this. On the two machines, run:
/sbin/ifconfig
The "inet addr:" for lo should be 127.0.0.1 on both machines, but
should be different for eth0 (or what ever your interface to the
router is.) If they are the same, then take a look at
/etc/sysconfig/network-scripts/ifcfg-eth0. Make sure it is not set
up for a static IP address. It may have more or less lines, but it
should look something like this: (HWADDR and DHCP_HOSTNAME for your
system or missing.)
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:02:A5:F4:91:5E
ONBOOT=yes
DHCP_HOSTNAME=mikkel
Mikkel
I took a look at /sbin/ifconfig and, in fact, it says exactly what you
siad it would (the addresses are not the same). I will try network
connection tomorrow and let you know the outcome.
:))))))))))))))))))))))))))))))))))))))))))))))))))))))))
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
11:43 a.m.
Carlos Alberto Alves wrote:
I took a look at /sbin/ifconfig and, in fact, it says exactly what you
said it would (the addresses are not the same). I will try network
connection tomorrow and let you know the outcome.
Looking at the DI-604 manual, you should have no problem assigning
static IP addresses to your machines using the router's DHCP setup.
If you go the the routers WEB setup page, and click on the DHCP
button, there is a section to assign static IP addresses based on
MAC address.
"Static DHCP is used to allow DHCP server to assign same IP address
to specific MAC address"
You should be able to grab the MAC address on that same page. They
should be listed in the "Dynamic DHCP Client List" section at the
bottom of the page for the currently connected computers. You can
then add the IP/host name information to /etc/hosts on both
machines, and be all set.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
2:11 p.m.
Mikkel L. Ellertson wrote:
Carlos Alberto Alves wrote:
>I took a look at /sbin/ifconfig and, in fact, it says exactly what you
>said it would (the addresses are not the same). I will try network
>connection tomorrow and let you know the outcome.
>
Looking at the DI-604 manual, you should have no problem assigning
static IP addresses to your machines using the router's DHCP setup.
I use a DI-604, and I simply disabled DHCP and set up static IP
on my machine. Why use DHCP in order not to use DHCP?
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
2:44 p.m.
Mike McCarty wrote:
Mikkel L. Ellertson wrote:
> Looking at the DI-604 manual, you should have no problem assigning
> static IP addresses to your machines using the router's DHCP setup.
I use a DI-604, and I simply disabled DHCP and set up static IP
on my machine. Why use DHCP in order not to use DHCP?
It works fine if all your machines are going to have static IP's.
But I have a few laptops that drift in and out of here that need
DHCP on the other networks they connect to, so it works out better
to let leave them set up for a dynamic IP address, and give them a
fixed address when here. (I could set up different network profiles
for different locations, but this works well for me.) I also
sometimes have "guest" machines on the local network, and I don't
have to reconfigure them. Now, I could set up all the servers with
static IP addresses outside the range of DHCP addresses and that
would work as well. I do this with a couple of print servers on the
network.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
4:08 p.m.
Mikkel L. Ellertson wrote:
Mike McCarty wrote:
> Mikkel L. Ellertson wrote:
>> Looking at the DI-604 manual, you should have no problem assigning
>> static IP addresses to your machines using the router's DHCP setup.
> I use a DI-604, and I simply disabled DHCP and set up static IP
> on my machine. Why use DHCP in order not to use DHCP?
>
It works fine if all your machines are going to have static IP's.
But I have a few laptops that drift in and out of here that need
DHCP on the other networks they connect to, so it works out better
to let leave them set up for a dynamic IP address, and give them a
fixed address when here. (I could set up different network profiles
for different locations, but this works well for me.) I also
sometimes have "guest" machines on the local network, and I don't
have to reconfigure them. Now, I could set up all the servers with
static IP addresses outside the range of DHCP addresses and that
would work as well. I do this with a couple of print servers on the
network.
Mikkel
Hi Mikkel!
Now my lan is working fine, following your instructions and IFCONFIG. I
have just to set up Guarddog to give permissions to lan.
Thanks very much, ;-)
--
**********************************************
* Carlos Alberto Alves *
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
4:55 p.m.
Mikkel L. Ellertson wrote:
Carlos Alberto Alves wrote:
> I took a look at /sbin/ifconfig and, in fact, it says exactly what you
> said it would (the addresses are not the same). I will try network
> connection tomorrow and let you know the outcome.
>
Looking at the DI-604 manual, you should have no problem assigning
static IP addresses to your machines using the router's DHCP setup.
If you go the the routers WEB setup page, and click on the DHCP
button, there is a section to assign static IP addresses based on
MAC address.
"Static DHCP is used to allow DHCP server to assign same IP address
to specific MAC address"
You should be able to grab the MAC address on that same page. They
should be listed in the "Dynamic DHCP Client List" section at the
bottom of the page for the currently connected computers. You can
then add the IP/host name information to /etc/hosts on both
machines, and be all set.
Mikkel
That's exactly what I was talking about. I will have to check with the
support people at radio wave ISP. They own the router and I am not
supposed to change its configuration.
:|
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
8:44 p.m.
On Sun, Apr 29, 2007 at 07:06:02PM -0300, Carlos Alberto Alves wrote:
Hi people!
I would like to see your opinion on this matter. I am running a home lan
with two computers, one ASUS MB K8-VX SE and another K8-VX, both onboard
lan, FC6 and a radio connection with a D-Link DI-604 broadband ethernet
router. Both computers can access internet at the same time smoothly,
but they cannot see each other's shared folders. NETFS, Network, NFS,
NFSLOCK and PORTMAP services are all up and running. Even if I disable
guarddog firewall on both computers, I still cannot see shared folders.
Any hints on how to setup NFS???
I am currently using a D-Link DI-604 at this moment on my home network of
five machines. (Mac G3 OSX 10.3; FC6; F7t4*2; XPpro) and have no problems
with any of the machines seeing any of the others.
The one thing I had to do to on the FC6 box was to add an IPTables rule to
let local LAN traffic be accepted.
iptables -I INPUT -s <10.11.12.0/24>* -j ACCEPT
the <ip>* should be replaced with your local LAN network number (no angle
brackets). This lets the NFS packets travel freely on the LAN and no exposure
on the Internet. Otherwise, on FC6, I found that there was no NFS access.
HTH
Wolfe
8:59 a.m.
G.Wolfe Woodbury wrote:
On Sun, Apr 29, 2007 at 07:06:02PM -0300, Carlos Alberto Alves
wrote:
> Hi people!
> I would like to see your opinion on this matter. I am running a home lan
> with two computers, one ASUS MB K8-VX SE and another K8-VX, both onboard
> lan, FC6 and a radio connection with a D-Link DI-604 broadband ethernet
> router. Both computers can access internet at the same time smoothly,
> but they cannot see each other's shared folders. NETFS, Network, NFS,
> NFSLOCK and PORTMAP services are all up and running. Even if I disable
> guarddog firewall on both computers, I still cannot see shared folders.
> Any hints on how to setup NFS???
I am currently using a D-Link DI-604 at this moment on my home network of
five machines. (Mac G3 OSX 10.3; FC6; F7t4*2; XPpro) and have no problems
with any of the machines seeing any of the others.
The one thing I had to do to on the FC6 box was to add an IPTables rule to
let local LAN traffic be accepted.
iptables -I INPUT -s <10.11.12.0/24>* -j ACCEPT
the <ip>* should be replaced with your local LAN network number (no angle
brackets). This lets the NFS packets travel freely on the LAN and no exposure
on the Internet. Otherwise, on FC6, I found that there was no NFS access.
HTH
Wolfe
Hi Wolfe!
Despite the fact that I can only set firewall rules in a graphical
interface, I disabled guarddog firewall rules and still could not see
shared folders. :(
--
**********************************************
* Carlos Alberto Alves *
* Child Neurologist *
* Systems Analyst/ASUS Certified Professional*
* Rio de Janeiro, Brazil *
* Skype: carlos-aa *
* mailto:drcaa@click21.com.br *
* mailto:drcaa@predialnet.com.br *
**********************************************
6210
days inactive
6215
days old
15 comments
4 participants
participants (4)
-
Carlos Alberto Alves -
G.Wolfe Woodbury -
Mike McCarty -
Mikkel