This is a discussion on MOUNT failed to NFS within the Linux Networking forums, part of the Linux Forums category; Hi, I configed my XP as a router so that my development board talk to LINUX box, XP and LINUX ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi,
I configed my XP as a router so that my development board talk to LINUX box, XP and LINUX box are both hooked to company network. I can do nc through port 2049 and other ports. but when I tried to mount from the development board to LINUX box, it gave error: mount: RPC Timed out. I know my NFS server is correct, I tried to mount through NFS from other machines, they are correct. So, problem is from my development board or the router. But I can do nc to transfer files over the 2049 port. The problem is definitely from my board? any idea how to dig in? I even monitoed the traffic on my XP network card, it never received the traffic from my board though? Could it be possible my company's firewall are blocking NFS? how come the 2049 port is still OK in this case? thanks patrick |
|
|||
|
PZ wrote:
> Hi, > > I configed my XP as a router so that my development board talk to > LINUX box, XP and LINUX box are both hooked to company network. > > I can do nc through port 2049 and other ports. but when I tried to > mount from the development board to LINUX box, it gave error: mount: > RPC Timed out. I know my NFS server is correct, I tried to mount > through NFS from other machines, they are correct. > > So, problem is from my development board or the router. But I can do > nc to transfer files over the 2049 port. The problem is definitely > from my board? any idea how to dig in? > > I even monitoed the traffic on my XP network card, it never received > the traffic from my board though? Could it be possible my company's > firewall are blocking NFS? how come the 2049 port is still OK in this > case? The firewall may block just ports between 1 and 1024 (service ports). try to connect via `telnet <NFS-Host-IP> 111`. If your output is like Trying <Host-IP>... Connected to <hostname>. Escape character is '^]'. the connection is ok, otherwise there might be an access or firewall problem. Do you see the packages from your XP box arriving at the NFS box? tcpdump -vvv -i <external-interface> dst port 22 and src <XP-host-IP> i.E. tcpdump -vvv -i eth0 dst port 22 and src www.xxx.yyy.zzz If you get an output for port 22, it might be an access problem. Eric |
|
|||
|
Eric wrote:
> PZ wrote: >> Hi, >> >> I configed my XP as a router so that my development board talk to >> LINUX box, XP and LINUX box are both hooked to company network. >> >> I can do nc through port 2049 and other ports. but when I tried to >> mount from the development board to LINUX box, it gave error: mount: >> RPC Timed out. I know my NFS server is correct, I tried to mount >> through NFS from other machines, they are correct. >> >> So, problem is from my development board or the router. But I can do >> nc to transfer files over the 2049 port. The problem is definitely >> from my board? any idea how to dig in? >> >> I even monitoed the traffic on my XP network card, it never received >> the traffic from my board though? Could it be possible my company's >> firewall are blocking NFS? how come the 2049 port is still OK in this >> case? > > The firewall may block just ports between 1 and 1024 (service ports). > try to connect via `telnet <NFS-Host-IP> 111`. If your output is like > Trying <Host-IP>... > Connected to <hostname>. > Escape character is '^]'. > > the connection is ok, otherwise there might be an access or firewall > problem. Do you see the packages from your XP box arriving at the NFS box? > > tcpdump -vvv -i <external-interface> dst port 22 and src <XP-host-IP> > i.E. > tcpdump -vvv -i eth0 dst port 22 and src www.xxx.yyy.zzz > > If you get an output for port 22, it might be an access problem. It would also be interesting if any traffic from the firewall is received for that service at the SSHD server. tcpdump -vvv -i <device> dst port 22 and src <firewall-IP> Eric |
|
|||
|
Eric wrote:
> Eric wrote: >> PZ wrote: >>> Hi, >>> >>> I configed my XP as a router so that my development board talk to >>> LINUX box, XP and LINUX box are both hooked to company network. >>> >>> I can do nc through port 2049 and other ports. but when I tried to >>> mount from the development board to LINUX box, it gave error: mount: >>> RPC Timed out. I know my NFS server is correct, I tried to mount >>> through NFS from other machines, they are correct. >>> >>> So, problem is from my development board or the router. But I can do >>> nc to transfer files over the 2049 port. The problem is definitely >>> from my board? any idea how to dig in? >>> >>> I even monitoed the traffic on my XP network card, it never received >>> the traffic from my board though? Could it be possible my company's >>> firewall are blocking NFS? how come the 2049 port is still OK in this >>> case? >> The firewall may block just ports between 1 and 1024 (service ports). >> try to connect via `telnet <NFS-Host-IP> 111`. If your output is like >> Trying <Host-IP>... >> Connected to <hostname>. >> Escape character is '^]'. >> >> the connection is ok, otherwise there might be an access or firewall >> problem. Do you see the packages from your XP box arriving at the NFS box? >> >> tcpdump -vvv -i <external-interface> dst port 22 and src <XP-host-IP> >> i.E. >> tcpdump -vvv -i eth0 dst port 22 and src www.xxx.yyy.zzz >> >> If you get an output for port 22, it might be an access problem. > > It would also be interesting if any traffic from the firewall is > received for that service at the SSHD server. > > tcpdump -vvv -i <device> dst port 22 and src <firewall-IP> Sorry, of course i mean dst port 111 instead of 22. Eric |