Hi! I'm assuming I don't have my member server configured correctly. I can
vpn in and connect to shared drives on the sbs box, but all files was moved
to the member server approx. 1 year ago. the member server is a file and
print server.

Playing around yesterday, I shared a sbs folder just to test with and the
vpn connection was happy. I unshared it as it isn't necessary--only used
for testing. I think this proved, thanks to Les Conner, that the sbs box
and vpn is configured correctly.

My problem is none of the shared folders on the member server is seen by the
vpn connection. All internal computers work fine. the folders on the
member server are "mapped" as drive letters for each workstation.

Any advice could be greatly appreciated. At first I thought maybe the
servers were confused because we were wrongfully using the same password on
each server. I changed that yesterday.

The sbs box shows up under domain controllers in AD. The member server is
seen under computers in AD.

At this point, you probably have to ask questions because I don't know what
other information may be necessary. Any advice/help would be greatly
appreciated.

MArcia

Re: Member server not seen by vpn connection by Merv

Merv
Sat Nov 29 13:11:02 CST 2003

Hi Marcia:

I assume your remote workstation is a Win2K Pro or WinXP Pro. On your
remote machine, if you can, change the name of the workgroup to match the
name of the SBS domain. In the VPN connectoid on the remote machine, under
TCP/IP properties...Advanced, add the SBS server's IP address under DNS.
Also make sure that "use default route" is checked in the VPN connectoid.
Now establish the VPN using a username/password combination that has
permissions to access files on the member server.

You may also need host/lmhost files on the remote computer, but see if the
above works first.

--
Merv Porter [SBS MVP]
===================================
"Marcia" <mporter@martechgroup.net> wrote in message
news:uhW#fqptDHA.1340@TK2MSFTNGP09.phx.gbl...
> Hi! I'm assuming I don't have my member server configured correctly. I
can
> vpn in and connect to shared drives on the sbs box, but all files was
moved
> to the member server approx. 1 year ago. the member server is a file and
> print server.
>
> Playing around yesterday, I shared a sbs folder just to test with and the
> vpn connection was happy. I unshared it as it isn't necessary--only used
> for testing. I think this proved, thanks to Les Conner, that the sbs box
> and vpn is configured correctly.
>
> My problem is none of the shared folders on the member server is seen by
the
> vpn connection. All internal computers work fine. the folders on the
> member server are "mapped" as drive letters for each workstation.
>
> Any advice could be greatly appreciated. At first I thought maybe the
> servers were confused because we were wrongfully using the same password
on
> each server. I changed that yesterday.
>
> The sbs box shows up under domain controllers in AD. The member server is
> seen under computers in AD.
>
> At this point, you probably have to ask questions because I don't know
what
> other information may be necessary. Any advice/help would be greatly
> appreciated.
>
> MArcia
>
>



Re: Member server not seen by vpn connection by Les

Les
Sat Nov 29 21:21:43 CST 2003

I would first check the member server first for ras or rras. It's not needed
and could get in the way. There may also be other unneeded and unwanted
servcies running on it.

When you create the vpn connection, can you run \\memberserver and see the
shares on it?

--
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !



"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:O10ryxqtDHA.3496@TK2MSFTNGP11.phx.gbl...
> Hi Marcia:
>
> I assume your remote workstation is a Win2K Pro or WinXP Pro. On your
> remote machine, if you can, change the name of the workgroup to match the
> name of the SBS domain. In the VPN connectoid on the remote machine,
under
> TCP/IP properties...Advanced, add the SBS server's IP address under DNS.
> Also make sure that "use default route" is checked in the VPN connectoid.
> Now establish the VPN using a username/password combination that has
> permissions to access files on the member server.
>
> You may also need host/lmhost files on the remote computer, but see if the
> above works first.
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "Marcia" <mporter@martechgroup.net> wrote in message
> news:uhW#fqptDHA.1340@TK2MSFTNGP09.phx.gbl...
> > Hi! I'm assuming I don't have my member server configured correctly. I
> can
> > vpn in and connect to shared drives on the sbs box, but all files was
> moved
> > to the member server approx. 1 year ago. the member server is a file
and
> > print server.
> >
> > Playing around yesterday, I shared a sbs folder just to test with and
the
> > vpn connection was happy. I unshared it as it isn't necessary--only
used
> > for testing. I think this proved, thanks to Les Conner, that the sbs
box
> > and vpn is configured correctly.
> >
> > My problem is none of the shared folders on the member server is seen by
> the
> > vpn connection. All internal computers work fine. the folders on the
> > member server are "mapped" as drive letters for each workstation.
> >
> > Any advice could be greatly appreciated. At first I thought maybe the
> > servers were confused because we were wrongfully using the same password
> on
> > each server. I changed that yesterday.
> >
> > The sbs box shows up under domain controllers in AD. The member server
is
> > seen under computers in AD.
> >
> > At this point, you probably have to ask questions because I don't know
> what
> > other information may be necessary. Any advice/help would be greatly
> > appreciated.
> >
> > MArcia
> >
> >
>
>



Re: Member server not seen by vpn connection by Marcia

Marcia
Sat Nov 29 21:32:58 CST 2003

Hi! Thanks for the reply. When I connect as administrator, it also can't
browse the network via vpn conection. When I connect via rdp as
administrator, it can.

I created the lmhosts file. When I do a "nbtstat -n", should the member
server be listed?

Marcia


"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:O10ryxqtDHA.3496@TK2MSFTNGP11.phx.gbl...
> Hi Marcia:
>
> I assume your remote workstation is a Win2K Pro or WinXP Pro. On your
> remote machine, if you can, change the name of the workgroup to match the
> name of the SBS domain. In the VPN connectoid on the remote machine,
under
> TCP/IP properties...Advanced, add the SBS server's IP address under DNS.
> Also make sure that "use default route" is checked in the VPN connectoid.
> Now establish the VPN using a username/password combination that has
> permissions to access files on the member server.
>
> You may also need host/lmhost files on the remote computer, but see if the
> above works first.
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "Marcia" <mporter@martechgroup.net> wrote in message
> news:uhW#fqptDHA.1340@TK2MSFTNGP09.phx.gbl...
> > Hi! I'm assuming I don't have my member server configured correctly. I
> can
> > vpn in and connect to shared drives on the sbs box, but all files was
> moved
> > to the member server approx. 1 year ago. the member server is a file
and
> > print server.
> >
> > Playing around yesterday, I shared a sbs folder just to test with and
the
> > vpn connection was happy. I unshared it as it isn't necessary--only
used
> > for testing. I think this proved, thanks to Les Conner, that the sbs
box
> > and vpn is configured correctly.
> >
> > My problem is none of the shared folders on the member server is seen by
> the
> > vpn connection. All internal computers work fine. the folders on the
> > member server are "mapped" as drive letters for each workstation.
> >
> > Any advice could be greatly appreciated. At first I thought maybe the
> > servers were confused because we were wrongfully using the same password
> on
> > each server. I changed that yesterday.
> >
> > The sbs box shows up under domain controllers in AD. The member server
is
> > seen under computers in AD.
> >
> > At this point, you probably have to ask questions because I don't know
> what
> > other information may be necessary. Any advice/help would be greatly
> > appreciated.
> >
> > MArcia
> >
> >
>
>



Re: Member server not seen by vpn connection by Merv

Merv
Sun Nov 30 11:23:24 CST 2003

I'm not sure how you're allowing your LAN users to access the shares on the
member server. Here is a fairly straightforward method:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=uX9Ws5j8CHA.548%40TK2MSFTNGP11.phx.gbl

Basically...

1. On the member server, go to the group called Administrators and add the
Domain Admins group from the domain. This should set up the member server
to allow total access to it when the user is a member of the Domain Admins
group.
2. On the SBS server, create a domain group called "Member Server Access"
and add the desired domain users to it.
3. On the member server, create a local group called "Member Server Users"
and add the "Member Server Access" domain group to it.
4. On the member server, share the resources and grant permissions based on
the "Member Server Users" local group.

Using this method, you can administer future member server access from the
SBS without having to play with the member server.

If this doesn't fix the VPN access problem, try using <domain>/user to
the VPN login username.

--
Merv Porter [SBS MVP]
===================================

"Marcia Porter" <mporter@acbfparentadvocates.org> wrote in message
news:##IQ7KvtDHA.560@TK2MSFTNGP11.phx.gbl...
> Hi! Thanks for the reply. When I connect as administrator, it also can't
> browse the network via vpn conection. When I connect via rdp as
> administrator, it can.
>
> I created the lmhosts file. When I do a "nbtstat -n", should the member
> server be listed?
>
> Marcia
>
>
> "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> news:O10ryxqtDHA.3496@TK2MSFTNGP11.phx.gbl...
> > Hi Marcia:
> >
> > I assume your remote workstation is a Win2K Pro or WinXP Pro. On your
> > remote machine, if you can, change the name of the workgroup to match
the
> > name of the SBS domain. In the VPN connectoid on the remote machine,
> under
> > TCP/IP properties...Advanced, add the SBS server's IP address under DNS.
> > Also make sure that "use default route" is checked in the VPN
connectoid.
> > Now establish the VPN using a username/password combination that has
> > permissions to access files on the member server.
> >
> > You may also need host/lmhost files on the remote computer, but see if
the
> > above works first.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "Marcia" <mporter@martechgroup.net> wrote in message
> > news:uhW#fqptDHA.1340@TK2MSFTNGP09.phx.gbl...
> > > Hi! I'm assuming I don't have my member server configured correctly.
I
> > can
> > > vpn in and connect to shared drives on the sbs box, but all files was
> > moved
> > > to the member server approx. 1 year ago. the member server is a file
> and
> > > print server.
> > >
> > > Playing around yesterday, I shared a sbs folder just to test with and
> the
> > > vpn connection was happy. I unshared it as it isn't necessary--only
> used
> > > for testing. I think this proved, thanks to Les Conner, that the sbs
> box
> > > and vpn is configured correctly.
> > >
> > > My problem is none of the shared folders on the member server is seen
by
> > the
> > > vpn connection. All internal computers work fine. the folders on the
> > > member server are "mapped" as drive letters for each workstation.
> > >
> > > Any advice could be greatly appreciated. At first I thought maybe the
> > > servers were confused because we were wrongfully using the same
password
> > on
> > > each server. I changed that yesterday.
> > >
> > > The sbs box shows up under domain controllers in AD. The member
server
> is
> > > seen under computers in AD.
> > >
> > > At this point, you probably have to ask questions because I don't know
> > what
> > > other information may be necessary. Any advice/help would be greatly
> > > appreciated.
> > >
> > > MArcia
> > >
> > >
> >
> >
>
>



Re: Member server not seen by vpn connection by Marcia

Marcia
Sun Nov 30 20:00:43 CST 2003

Thanks. I will try tomorrow or Tuesday.

Marcia

"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:OVBTUa2tDHA.1512@TK2MSFTNGP10.phx.gbl...
> I'm not sure how you're allowing your LAN users to access the shares on
the
> member server. Here is a fairly straightforward method:
>
>
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=uX9Ws5j8CHA.548%40TK2MSFTNGP11.phx.gbl
>
> Basically...
>
> 1. On the member server, go to the group called Administrators and add
the
> Domain Admins group from the domain. This should set up the member server
> to allow total access to it when the user is a member of the Domain Admins
> group.
> 2. On the SBS server, create a domain group called "Member Server Access"
> and add the desired domain users to it.
> 3. On the member server, create a local group called "Member Server
Users"
> and add the "Member Server Access" domain group to it.
> 4. On the member server, share the resources and grant permissions based
on
> the "Member Server Users" local group.
>
> Using this method, you can administer future member server access from the
> SBS without having to play with the member server.
>
> If this doesn't fix the VPN access problem, try using <domain>/user
to
> the VPN login username.
>
> --
> Merv Porter [SBS MVP]
> ===================================
>
> "Marcia Porter" <mporter@acbfparentadvocates.org> wrote in message
> news:##IQ7KvtDHA.560@TK2MSFTNGP11.phx.gbl...
> > Hi! Thanks for the reply. When I connect as administrator, it also
can't
> > browse the network via vpn conection. When I connect via rdp as
> > administrator, it can.
> >
> > I created the lmhosts file. When I do a "nbtstat -n", should the member
> > server be listed?
> >
> > Marcia
> >
> >
> > "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> > news:O10ryxqtDHA.3496@TK2MSFTNGP11.phx.gbl...
> > > Hi Marcia:
> > >
> > > I assume your remote workstation is a Win2K Pro or WinXP Pro. On your
> > > remote machine, if you can, change the name of the workgroup to match
> the
> > > name of the SBS domain. In the VPN connectoid on the remote machine,
> > under
> > > TCP/IP properties...Advanced, add the SBS server's IP address under
DNS.
> > > Also make sure that "use default route" is checked in the VPN
> connectoid.
> > > Now establish the VPN using a username/password combination that has
> > > permissions to access files on the member server.
> > >
> > > You may also need host/lmhost files on the remote computer, but see if
> the
> > > above works first.
> > >
> > > --
> > > Merv Porter [SBS MVP]
> > > ===================================
> > > "Marcia" <mporter@martechgroup.net> wrote in message
> > > news:uhW#fqptDHA.1340@TK2MSFTNGP09.phx.gbl...
> > > > Hi! I'm assuming I don't have my member server configured
correctly.
> I
> > > can
> > > > vpn in and connect to shared drives on the sbs box, but all files
was
> > > moved
> > > > to the member server approx. 1 year ago. the member server is a
file
> > and
> > > > print server.
> > > >
> > > > Playing around yesterday, I shared a sbs folder just to test with
and
> > the
> > > > vpn connection was happy. I unshared it as it isn't necessary--only
> > used
> > > > for testing. I think this proved, thanks to Les Conner, that the
sbs
> > box
> > > > and vpn is configured correctly.
> > > >
> > > > My problem is none of the shared folders on the member server is
seen
> by
> > > the
> > > > vpn connection. All internal computers work fine. the folders on
the
> > > > member server are "mapped" as drive letters for each workstation.
> > > >
> > > > Any advice could be greatly appreciated. At first I thought maybe
the
> > > > servers were confused because we were wrongfully using the same
> password
> > > on
> > > > each server. I changed that yesterday.
> > > >
> > > > The sbs box shows up under domain controllers in AD. The member
> server
> > is
> > > > seen under computers in AD.
> > > >
> > > > At this point, you probably have to ask questions because I don't
know
> > > what
> > > > other information may be necessary. Any advice/help would be
greatly
> > > > appreciated.
> > > >
> > > > MArcia
> > > >
> > > >
> > >
> > >
> >
> >
>
>