Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Todd Stephens on December 23, 2001, 12:21:03 PM
-
I have a server running version 4.1.2 as a server-gateway. From home, I can connect to the server via VPN and browse the Network Neighborhood. I can not connect to any shares except the ones on the e-smith gateway. I can see all the i-bays and my user dir, but can't access anything else in the workgroup.
After searching the forums, I tried Google and found this:
7.2.7. Can see machines from the local network in Network Neighborhood, but
get "\machinename is not accessible" errors when trying to
double-click on them.
Solution: This can be caused by 2 things:
1) The ipchains rules don't enable forwarding between the pptp connection
and the local network. You should have an ipchains rule like the following
(see section 4.1, above, for more information):
# Enable packet forwarding to/from the pptpd connection
# This is the critical rule to allow traffic from the local
# network to make it to the pptpd connection, and vice versa
ipchains -A forward -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
2) The ipchains rules are Masquerading before they are forwarding.
The 'ipchains -A forward -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT'
must be listed BEFORE any 'ipchains -A forward -j MASQ' rule.
3) The c:\windows\hosts and c:\windows\lmhosts don't list the proper
IP address/machine name connections. Check to see that all of your local
network machines are listed in BOTH of these files on the machine dialing
in to the network through Virtual Private Networking.
I apologize for the formatting if it looks terrible. Does this mean that I need to add or modify a chain to allow me to actually use network shares? If so, how do I go about doing this on the server? Do I need to implement port forwarding ?
By the way, the link to the above info is http://www.vibrationresearch.com/pptpd/pptpd-FAQ.txt
Thanks,
Todd