set your tunnel net to 192.168.0.(range not used by statics or dhcp).<div><br></div><div>by having 192.168.0. and 192.168.99.0, they end up on different subnets</div><div><br><div class="gmail_quote">On Tue, Feb 5, 2013 at 10:26 PM, Steve @ HCS <span dir="ltr"><<a href="mailto:steveg@branchadventures.org" target="_blank">steveg@branchadventures.org</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div>Thanks guys,<br>
      <br>
      PFSense tunnel "host" inside net is <a href="http://192.168.0.0/24" target="_blank">192.168.0.0/24</a><br>
      tunnel net is 192.168.99.*  issuing .6 on the connection 
      (pingable from host on only on LAN interface, and a 0. machine)<br>
      client outside: 108.79.220.88  (Pingable from 0. machine and host
      both interfaces)<br>
      <br>
      Turned of client side windows firewall, and antivirus.  No change<br>
      <br>
      Attempting to open a "network places" of \\192.168.0.n\example
      yields not accessible or no permission<br>
      <br>
      I added the windows/system32/etc/lmhost and can ping that machine
      name on the inside of the host from the client side.<br>
       <br>
      FYI: I have a IPSec tunnel to another site that hits these share
      with no problem.  (i understand that is a different animal)<br>
      <br>
      I feel like such a noob, as it's probably something really basic
      i'm overlooking...<div><div class="h5"><br>
      <br>
      On 2/5/2013 7:59 PM, Josh wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">192.168.0.* is your internal net
      <div><br>
      </div>
      <div>what is your vpn net?<br>
        <br>
        <div class="gmail_quote">On Tue, Feb 5, 2013 at 7:57 PM, Josh <span dir="ltr"><<a href="mailto:leapole@gmail.com" target="_blank">leapole@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">kinda
            sounds like you have a one way route situation, 
            <div><br>
            </div>
            <div>outside can ping and see everything but I am willing to
              bet inside can not see whats connected to the vpn.</div>
            <div><br>
            </div>
            <div>so ping with both machines and make sure that works<br>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <blockquote type="cite">
      <div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>
              <br>
              <div class="gmail_quote">
                <div>
                  <div>On Tue, Feb 5, 2013 at 7:46 PM, Mark
                    Farver <span dir="ltr"><<a href="mailto:mfarver@mindbent.org" target="_blank">mfarver@mindbent.org</a>></span>
                    wrote:<br>
                  </div>
                </div>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div>
                    <div>
                      <p dir="ltr">Not enough data on your setup but my
                        first guess would be windows or a third party
                        firewall.  By default most firewalls only allow
                        windows sharing connections from the same
                        subnet.</p>
                      <p dir="ltr">Second thing to try is put the
                        server's machine name and IP into the client
                        PC's lmhosts file and verify you can ping by
                        name..then retry sharing.</p>
                      <span><font color="#888888">
                          <p dir="ltr">Mark Farver<br>
                          </p>
                        </font></span><br>
                    </div>
                  </div>
                  _______________________________________________<br>
                  grlug mailing list<br>
                  <a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
                  <a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
                </blockquote>
              </div>
              <br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
grlug mailing list
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a></pre>
    </blockquote>
    <br>
    <br>
    </div></div><span class="HOEnZb"><font color="#888888"><div>-- <br>
      <font color="black">
        <h3>Healthy Computer Systems
        </h3>
        <h4>Steve Grody - Owner
        </h4>
        <h4><a href="tel:616-502-2454" value="+16165022454" target="_blank">616-502-2454</a></h4>
      </font></div>
  </font></span></div>

<br>_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br></blockquote></div><br></div>