sf_jeff
asked on
I need to mount a windows share behind a firewall over vpn to a linux box.
my original attempt is:
sudo smbmount //<windows-host>>/MountNam
This gives me "(No route to host)"
My network topology is:
I am outside the network on my windows box dialing in over VPN. I want to develop using local files on my windows box and yet execute the same files on Linux via a mount.
It looks like with my VPN setup there are three ports that are associated with my windows hostname. One is associated with the vpn network adapter that I see in dos (Say, IP1). The next is the one that resolves when I ping the box (IP2). The third is the ip associated with the return packets. (IP3).
I am using a Red Hat distribution, kernel 2.4.21, and so am trying to use smbfs instead of CIFS.
tantalizingly, when I use IP3, the error changes to "No such share". I am starting to think that this is a response directly from a firewall box and that my Windows host never sees the mount requests.
If it makes a difference, I am doing all of this in putty sessions on my windows box.
sudo smbmount //<windows-host>>/MountNam
This gives me "(No route to host)"
My network topology is:
I am outside the network on my windows box dialing in over VPN. I want to develop using local files on my windows box and yet execute the same files on Linux via a mount.
It looks like with my VPN setup there are three ports that are associated with my windows hostname. One is associated with the vpn network adapter that I see in dos (Say, IP1). The next is the one that resolves when I ping the box (IP2). The third is the ip associated with the return packets. (IP3).
I am using a Red Hat distribution, kernel 2.4.21, and so am trying to use smbfs instead of CIFS.
tantalizingly, when I use IP3, the error changes to "No such share". I am starting to think that this is a response directly from a firewall box and that my Windows host never sees the mount requests.
If it makes a difference, I am doing all of this in putty sessions on my windows box.
ASKER
Apologies. I am not used to text in this forum and my original command got truncated.
I suspect that the problem here is the VPN communication, rather than the actual SMB command.
In reference to your question.
I see 3 different actual IP addresses. I see one when I run 'ipconfig /all' from my windows box and look in the section for VPN. The other two I see when I ping this box by DNS name. At the top of the command, it says something like "pinging address ip2". With each packet that comes back, I see "Response from ip3".
It looks like given my current firewall settings, it will be impossible to use the standard technique of ssh'ing from the netshare client to the netshare server and tunnelling over that.
I just tried to ssh without the VPN in place and couldn't create an interactive session due to blocked port 22. It seems a pretty good bet that if ssh doesn't work without "-L" it probably won't work with "-L". :)
I SSH the other way all the time, from Windows to Linux, using putty. Is it possible to get it working that way?
I suspect that the problem here is the VPN communication, rather than the actual SMB command.
In reference to your question.
I see 3 different actual IP addresses. I see one when I run 'ipconfig /all' from my windows box and look in the section for VPN. The other two I see when I ping this box by DNS name. At the top of the command, it says something like "pinging address ip2". With each packet that comes back, I see "Response from ip3".
It looks like given my current firewall settings, it will be impossible to use the standard technique of ssh'ing from the netshare client to the netshare server and tunnelling over that.
I just tried to ssh without the VPN in place and couldn't create an interactive session due to blocked port 22. It seems a pretty good bet that if ssh doesn't work without "-L" it probably won't work with "-L". :)
I SSH the other way all the time, from Windows to Linux, using putty. Is it possible to get it working that way?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is still in my court. Sorry for the delay.
Not sure what you mean by:
"The third is the ip associated with the return packets. (IP3)."
Full command needed will be something like:
Open in new window