Yea you are right, you should.  I have a PPTP server setup on my
router and it allows me to do that.  No netbios needed.

Casey




On 5/8/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I should be able to access them by entering \\10.1.1.x in an explorer
> address bar without netbios. This is what I can't do. Is this not right?
>
> Cameron
>
> > There are several things you can do to make network drives more acessable.
> >
> > Map the network drives so they reconnect themselves
> > You could put together a WINS server.
> > Setup the internal DNS server(s) to resolve hostnames
> > You can manage the file C:\WINDOWS\system32\drivers\etc\hosts on each
> > computer.
> >
> > I'm sure there are a couple other ways to do it, but here are a few.
> > I think what makes it a pain is that netbios is not passing the VPN
> > like expected.  It shouldn't be that hard to make a few firewall rules
> > to keep unwanted DHCP out.
> >
> > Casey
> >
> >
> >
> > On 5/8/08, ccrum <[EMAIL PROTECTED]> wrote:
> >> I've connected two remote offices using two MT's, one as a VPN server
> >> and one as a client. I've set up static routes in the routes table as
> >> outlined in the documentation so that each network can now ping ip's on
> >> the other side, and print to each other's TCP/IP printers. I am having
> >> difficulty seeing network drives from one side to the other. I set up
> >> eoip between the two, and it resolved the problem, but caused another
> >> problem in that the two DHCP servers were now fighting each other, so I
> >> disabled that. Is there something special I need to do to locate network
> >> drives by IP address from one side to the other? The VPN server side has
> >> internal network address range (DHCP ) of 10.1.1.0/24 and the client is
> >> running a 10.0.0.0/24 (DHCP). The routing table looks like this on the
> >> server:
> >>
> >> #      DST-ADDRESS        PREF-SRC        G GATEWAY         DISTANCE
> >> INTERFACE
> >> 0  A S 0.0.0.0/0                                              r
> >> 216.171.241.169              1        Wilcoat
> >> 1  A S 10.0.0.0/24                                            r
> >> 10.3.3.2                          1        pptp-in1
> >> 2  ADC 10.1.1.0/24        10.1.1.1
> >>                        0        bridge1
> >> 3  ADC 10.3.3.2/32        10.3.3.1
> >>                        0        pptp-in1
> >> 4  ADC 216.171.241.168/29 216.171.241.173
> >>          0        Wilcoat
> >>
> >> The routing table on the client looks like this:
> >>
> >> #      DST-ADDRESS        PREF-SRC        G GATEWAY         DIS
> >> INTERFACE
> >> 0  A S 0.0.0.0/0                                               r
> >> 99.158.201.230   1   DSL_IN
> >> 1  ADC 10.0.0.0/24            10.0.0.1
> >>            0   bridge1
> >> 2  A S 10.1.1.0/24                                            r
> >> 10.3.3.1              1   pptp-out1
> >> 3  ADC 10.3.3.1/32        10.3.3.2
> >>            0   pptp-out1
> >> 4  ADC 99.158.201.224/29  99.158.201.225
> >> 0   DSL_IN
> >>
> >>
> >> The 10.3.3.x address are the local and remote addresses of the VPN
> >> connection. During the eoip session I was able to get to network drives
> >> on either side, but DHCP went haywire. Any ideas on what I need to do to
> >> see network drives across this connection?
> >>
> >> Regards,
> >>
> >> Cameron
> >> _______________________________________________
> >> Mikrotik mailing list
> >> [email protected]
> >> http://www.butchevans.com/mailman/listinfo/mikrotik
> >>
> > _______________________________________________
> > Mikrotik mailing list
> > [email protected]
> > http://www.butchevans.com/mailman/listinfo/mikrotik
> >
>
>
> _______________________________________________
> Mikrotik mailing list
> [email protected]
> http://www.butchevans.com/mailman/listinfo/mikrotik
>

Reply via email to