Merv
Fri May 28 11:12:42 CDT 2004
When the remote users establish a VPN, are they assigned an IP address that
is in the same subnet as the SBS server (default would be 192.168.16.x) or
are they assigned from a static pool of IP addresses in a different subnet?
You should be able to check in RRAS to get this info.
--
Merv Porter [SBS MVP]
===================================
"Corey" <anonymous@discussions.microsoft.com> wrote in message
news:1433601c444c5$f73f8dc0$a601280a@phx.gbl...
> Merv,
>
> I did as you suggested and still had the same results.
> Is there anything I should look for on the server?
> RRAS? ISA?
>
> I can ping everything on the main SBS LAN by IP Address.
> I can ping everything on the main SBS LAN by FQDN. I can
> NOT ping by machine name. I can NOT access the internet.
>
> Thanks again for your suggestions.
>
> Corey
>
>
> >-----Original Message-----
> >Some references...
> >
> >Set up SBS 2000 for remote access
> >
http://www.smallbizserver.net/DesktopDefault.aspx?
> tabid=108
> >
> >Set up remote clients for VPN access to SBS 2000
> >
http://www.smallbizserver.net/DesktopDefault.aspx?
> tabid=109
> >
> >Also, for name resolution, in the VPN connectoid of the
> each remote
> >workstation, go into the TCP/IP properties and set the
> DNS to the IP address
> >of the SBS server (probably 192.168.16.2). It would
> also help if you could
> >set up the workgroup name for the remote workstations to
> be the same name as
> >the SBS domain (if SBS domain is: mycompany.local, set
> remote workgroup name
> >to mycompany).
> >
> >In addition, make sure that the private subnet at the
> remote location is
> >different from that on the SBS domain (if SBS domain is
> 192.168.16.x, make
> >the remote location something like 192.168.17.x; any
> private range will do,
> >just as long as it's not the same as the SBS domain IP
> range).
> >
> >As you probably know, a VPN using dial-up Internet
> access is going to be
> >painfully slow for your remote users; even more so if
> the remote Internet
> >connection is shared. One way to speed this up a little
> would be to set up
> >a cheap WinXP Pro workstation on the SBS LAN. Then have
> the remote users
> >VPN into the SBS LAN and fire up an RDC session to that
> WinXP Pro
> >workstation. Of course, only one remote workstation at
> a time could access
> >the SBS LAN WinXP Pro workstation.
> >
> >Another way to speed up there link would be to have the
> telephone company
> >install an ISDN line. Somewhat more expensive but your
> remote users would
> >have a better "experience".
> >
> >Not sure what "files" you're planning on shoving down
> the VPN tunnel, but
> >you may find that this is all but useless using a dial-
> up connection.
> >
> >Just my $.02
> >
> >--
> >Merv Porter [SBS MVP]
> >===================================
> >"Corey" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:12fa001c44363$a8cdcf20$a001280a@phx.gbl...
> >> Hello All.
> >>
> >> I have a remote office of 3 PCs that I was going set up
> >> as a workgroup. DSL is not available in the location,
> so
> >> each PC is going to dialup to the main office (SBS
> 2000)
> >> to get email and files.
> >>
> >> However, once the PC is connected, it does not seem to
> be
> >> receiving internal DNS information. I canNOT ping the
> >> server by name, only IP address. Also, no internet
> >> access, no email and no network browsing (accept by IP
> >> address).
> >>
> >> Another location uses VPN over DSL flawlessly.
> >>
> >> What am I missing? What should the remote local IP,
> >> subnet and gateway be? How might ISA server need to be
> >> configured?
> >>
> >> TIA,
> >>
> >> Corey
> >
> >
> >.
> >