Moved home folders - now problem accessing shares

For about 2 years we have had a Microsoft SBS 2000 server.
All data and shares have been located on this server.
We have also had a member server storing additional
accounts data. The member server is also used as the
Primary DNS server, WINS server and DHCP server.

Recently the member server's disk subsystem's capacity
was substantially increased.
We decided to move home folders from the SBS server to
the member server to alleviate some loading issues on the
SBS server and also to free up some disk space.
This change was made in two places; In Active Directory
Users and Computers, each users' accounts properties were
modified to point the home drive to the member server (H:
\\servername\sharename). Also, Group Policy was modified
to redirect 'My Documents' from the SBS server to the
member server.

After two weeks without problems, I removed the home
folder shares from the SBS server.

When users attempted to log on, some of their login
scripts did not run resulting in no network drives being
mapped. Some login scripts did run without error, but
when an attempt was made to expand a drive "Access is
denied" errors were received.

If I tried to manually map a drive using
\\servername\sharename, the resource was not found. If I
mapped using \\IP_Address\sharename, the resource was
found, but 'Access is denied' errors were returned when
trying to expand the share.

At a command prompt, net view \\servername returned no
shares. I even preloaded the netbios cache using LMHOSTS
but could not map drives using netbios names.

While testing, I configured a client with a static IP
address, and changed the DNS settings.

I eventually recreated empty home share on the SBS server
for each user, which restored functionality. However,
when clients connect via RAS I still get 'Access is
denied.' WINS, DNS, etc are configured via DHCP when the
client connects.
Question 1: Why does\did moving home shares to the member
server cause a problem once the shares were removed from
the SBS server?

Question 2: Why do I still get problems with RRAS clients?



Please help!

Dirk-Thomas
Thu Aug 21 11:33:51 CDT 2003

Hmmm.. I have always simply note the name and share name, stopped the share,
created the folders with the same name, share name, permissions and moved
the contents. WE are using UNC \\servername\shared folder name so where or
what partition isn't a concern

Dirk-Thomas

"gibbo" <gibbo@theoffice.com> wrote in message
news:049201c367dd$d772bc80$a001280a@phx.gbl...
> For about 2 years we have had a Microsoft SBS 2000 server.
> All data and shares have been located on this server.
> We have also had a member server storing additional
> accounts data. The member server is also used as the
> Primary DNS server, WINS server and DHCP server.
>
> Recently the member server's disk subsystem's capacity
> was substantially increased.
> We decided to move home folders from the SBS server to
> the member server to alleviate some loading issues on the
> SBS server and also to free up some disk space.
> This change was made in two places; In Active Directory
> Users and Computers, each users' accounts properties were
> modified to point the home drive to the member server (H:
> \\servername\sharename). Also, Group Policy was modified
> to redirect 'My Documents' from the SBS server to the
> member server.
>
> After two weeks without problems, I removed the home
> folder shares from the SBS server.
>
> When users attempted to log on, some of their login
> scripts did not run resulting in no network drives being
> mapped. Some login scripts did run without error, but
> when an attempt was made to expand a drive "Access is
> denied" errors were received.
>
> If I tried to manually map a drive using
> \\servername\sharename, the resource was not found. If I
> mapped using \\IP_Address\sharename, the resource was
> found, but 'Access is denied' errors were returned when
> trying to expand the share.
>
> At a command prompt, net view \\servername returned no
> shares. I even preloaded the netbios cache using LMHOSTS
> but could not map drives using netbios names.
>
> While testing, I configured a client with a static IP
> address, and changed the DNS settings.
>
> I eventually recreated empty home share on the SBS server
> for each user, which restored functionality. However,
> when clients connect via RAS I still get 'Access is
> denied.' WINS, DNS, etc are configured via DHCP when the
> client connects.
> Question 1: Why does\did moving home shares to the member
> server cause a problem once the shares were removed from
> the SBS server?
>
> Question 2: Why do I still get problems with RRAS clients?
>
>
>
> Please help!
>
>

Les
Thu Aug 21 12:00:13 CDT 2003

I think the add user wizard may barf if the share is not on the sbs box
itself. Or, it won't barf, but the share will not work.

But Dirk-Thomas has the correct method for moving to a different location on
the SBS.

--
Les Connor
------------------
[SBS MVP]



"Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in message
news:#EYHCIAaDHA.2404@TK2MSFTNGP10.phx.gbl...
> Hmmm.. I have always simply note the name and share name, stopped the
share,
> created the folders with the same name, share name, permissions and moved
> the contents. WE are using UNC \\servername\shared folder name so where
or
> what partition isn't a concern
>
> Dirk-Thomas
>
> "gibbo" <gibbo@theoffice.com> wrote in message
> news:049201c367dd$d772bc80$a001280a@phx.gbl...
> > For about 2 years we have had a Microsoft SBS 2000 server.
> > All data and shares have been located on this server.
> > We have also had a member server storing additional
> > accounts data. The member server is also used as the
> > Primary DNS server, WINS server and DHCP server.
> >
> > Recently the member server's disk subsystem's capacity
> > was substantially increased.
> > We decided to move home folders from the SBS server to
> > the member server to alleviate some loading issues on the
> > SBS server and also to free up some disk space.
> > This change was made in two places; In Active Directory
> > Users and Computers, each users' accounts properties were
> > modified to point the home drive to the member server (H:
> > \\servername\sharename). Also, Group Policy was modified
> > to redirect 'My Documents' from the SBS server to the
> > member server.
> >
> > After two weeks without problems, I removed the home
> > folder shares from the SBS server.
> >
> > When users attempted to log on, some of their login
> > scripts did not run resulting in no network drives being
> > mapped. Some login scripts did run without error, but
> > when an attempt was made to expand a drive "Access is
> > denied" errors were received.
> >
> > If I tried to manually map a drive using
> > \\servername\sharename, the resource was not found. If I
> > mapped using \\IP_Address\sharename, the resource was
> > found, but 'Access is denied' errors were returned when
> > trying to expand the share.
> >
> > At a command prompt, net view \\servername returned no
> > shares. I even preloaded the netbios cache using LMHOSTS
> > but could not map drives using netbios names.
> >
> > While testing, I configured a client with a static IP
> > address, and changed the DNS settings.
> >
> > I eventually recreated empty home share on the SBS server
> > for each user, which restored functionality. However,
> > when clients connect via RAS I still get 'Access is
> > denied.' WINS, DNS, etc are configured via DHCP when the
> > client connects.
> > Question 1: Why does\did moving home shares to the member
> > server cause a problem once the shares were removed from
> > the SBS server?
> >
> > Question 2: Why do I still get problems with RRAS clients?
> >
> >
> >
> > Please help!
> >
> >
>
>

Merv
Thu Aug 21 20:57:44 CDT 2003

Jeff M. posted along similar lines something back in February. Moving user
shared and company folders to another box apparently is gets SBS all
upset...

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=OTq9IsFzCHA.1580%40TK2MSFTNGP09&rnum=8&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26q%3Dmove%2Buser%2Bshared%2Bto%2Bmember%2Bserver%2Bmiddleton

--
Merv Porter [SBS MVP]
===================================
"Les Connor [SBS MVP]" <les.connor@cfiveDEL.ca> wrote in message
news:OnEqxWAaDHA.2648@TK2MSFTNGP09.phx.gbl...
> I think the add user wizard may barf if the share is not on the sbs box
> itself. Or, it won't barf, but the share will not work.
>
> But Dirk-Thomas has the correct method for moving to a different location
on
> the SBS.
>
> --
> Les Connor
> ------------------
> [SBS MVP]
>
>
>
> "Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in message
> news:#EYHCIAaDHA.2404@TK2MSFTNGP10.phx.gbl...
> > Hmmm.. I have always simply note the name and share name, stopped the
> share,
> > created the folders with the same name, share name, permissions and
moved
> > the contents. WE are using UNC \\servername\shared folder name so where
> or
> > what partition isn't a concern
> >
> > Dirk-Thomas
> >
> > "gibbo" <gibbo@theoffice.com> wrote in message
> > news:049201c367dd$d772bc80$a001280a@phx.gbl...
> > > For about 2 years we have had a Microsoft SBS 2000 server.
> > > All data and shares have been located on this server.
> > > We have also had a member server storing additional
> > > accounts data. The member server is also used as the
> > > Primary DNS server, WINS server and DHCP server.
> > >
> > > Recently the member server's disk subsystem's capacity
> > > was substantially increased.
> > > We decided to move home folders from the SBS server to
> > > the member server to alleviate some loading issues on the
> > > SBS server and also to free up some disk space.
> > > This change was made in two places; In Active Directory
> > > Users and Computers, each users' accounts properties were
> > > modified to point the home drive to the member server (H:
> > > \\servername\sharename). Also, Group Policy was modified
> > > to redirect 'My Documents' from the SBS server to the
> > > member server.
> > >
> > > After two weeks without problems, I removed the home
> > > folder shares from the SBS server.
> > >
> > > When users attempted to log on, some of their login
> > > scripts did not run resulting in no network drives being
> > > mapped. Some login scripts did run without error, but
> > > when an attempt was made to expand a drive "Access is
> > > denied" errors were received.
> > >
> > > If I tried to manually map a drive using
> > > \\servername\sharename, the resource was not found. If I
> > > mapped using \\IP_Address\sharename, the resource was
> > > found, but 'Access is denied' errors were returned when
> > > trying to expand the share.
> > >
> > > At a command prompt, net view \\servername returned no
> > > shares. I even preloaded the netbios cache using LMHOSTS
> > > but could not map drives using netbios names.
> > >
> > > While testing, I configured a client with a static IP
> > > address, and changed the DNS settings.
> > >
> > > I eventually recreated empty home share on the SBS server
> > > for each user, which restored functionality. However,
> > > when clients connect via RAS I still get 'Access is
> > > denied.' WINS, DNS, etc are configured via DHCP when the
> > > client connects.
> > > Question 1: Why does\did moving home shares to the member
> > > server cause a problem once the shares were removed from
> > > the SBS server?
> > >
> > > Question 2: Why do I still get problems with RRAS clients?
> > >
> > >
> > >
> > > Please help!
> > >
> > >
> >
> >
>
>

Gibbo
Wed Aug 27 06:10:04 CDT 2003

Me Again.
I have always just used Active Directory Users and
Computers for creating the accounts and shares. I have
never rolled out the SBS client at this site. And
everything you've said rings true. However, still having
problems.
I know that if the default shares thatSBS creates for
users' home folders is messed around with it causes
script failure, but these shares are still present.

I think the cl;ue is in the name resolution issues. There
were some technet articles talking about name resolution
issues, but their causes were not the same as the ones
that I am experiencing.

Gibbo

>-----Original Message-----
>I think the add user wizard may barf if the share is not
on the sbs box
>itself. Or, it won't barf, but the share will not work.
>
>But Dirk-Thomas has the correct method for moving to a
different location on
>the SBS.
>
>--
>Les Connor
>------------------
>[SBS MVP]
>
>
>
>"Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in
message
>news:#EYHCIAaDHA.2404@TK2MSFTNGP10.phx.gbl...
>> Hmmm.. I have always simply note the name and share
name, stopped the
>share,
>> created the folders with the same name, share name,
permissions and moved
>> the contents. WE are using UNC \\servername\shared
folder name so where
>or
>> what partition isn't a concern
>>
>> Dirk-Thomas
>>
>> "gibbo" <gibbo@theoffice.com> wrote in message
>> news:049201c367dd$d772bc80$a001280a@phx.gbl...
>> > For about 2 years we have had a Microsoft SBS 2000
server.
>> > All data and shares have been located on this server.
>> > We have also had a member server storing additional
>> > accounts data. The member server is also used as the
>> > Primary DNS server, WINS server and DHCP server.
>> >
>> > Recently the member server's disk subsystem's
capacity
>> > was substantially increased.
>> > We decided to move home folders from the SBS server
to
>> > the member server to alleviate some loading issues
on the
>> > SBS server and also to free up some disk space.
>> > This change was made in two places; In Active
Directory
>> > Users and Computers, each users' accounts properties
were
>> > modified to point the home drive to the member
server (H:
>> > \\servername\sharename). Also, Group Policy was
modified
>> > to redirect 'My Documents' from the SBS server to the
>> > member server.
>> >
>> > After two weeks without problems, I removed the home
>> > folder shares from the SBS server.
>> >
>> > When users attempted to log on, some of their login
>> > scripts did not run resulting in no network drives
being
>> > mapped. Some login scripts did run without error, but
>> > when an attempt was made to expand a drive "Access is
>> > denied" errors were received.
>> >
>> > If I tried to manually map a drive using
>> > \\servername\sharename, the resource was not found.
If I
>> > mapped using \\IP_Address\sharename, the resource was
>> > found, but 'Access is denied' errors were returned
when
>> > trying to expand the share.
>> >
>> > At a command prompt, net view \\servername returned
no
>> > shares. I even preloaded the netbios cache using
LMHOSTS
>> > but could not map drives using netbios names.
>> >
>> > While testing, I configured a client with a static IP
>> > address, and changed the DNS settings.
>> >
>> > I eventually recreated empty home share on the SBS
server
>> > for each user, which restored functionality. However,
>> > when clients connect via RAS I still get 'Access is
>> > denied.' WINS, DNS, etc are configured via DHCP when
the
>> > client connects.
>> > Question 1: Why does\did moving home shares to the
member
>> > server cause a problem once the shares were removed
from
>> > the SBS server?
>> >
>> > Question 2: Why do I still get problems with RRAS
clients?
>> >
>> >
>> >
>> > Please help!
>> >
>> >
>>
>>
>
>
>.
>

Les
Wed Aug 27 14:22:55 CDT 2003

Hi Gibbo,

There's a substantial difference in how the account permissions are
configured between creating a user or computer account with and without the
wizards.

For example, create two user accounts - one with the add user wizard, one
without - and explore the differences in detail. It is of course possible to
do what the wizards do manually (and more), but it does require a lot of
steps - i.e. possible misconfiguration steps.

I'm not sure what you mean by this:

>I have
> never rolled out the SBS client at this site.

--
Les Connor
------------------
[SBS MVP]



"Gibbo" <Gibbo@theoffice.com> wrote in message
news:0ab301c36c8b$c4564d30$a401280a@phx.gbl...
> Me Again.
> I have always just used Active Directory Users and
> Computers for creating the accounts and shares. I have
> never rolled out the SBS client at this site. And
> everything you've said rings true. However, still having
> problems.
> I know that if the default shares thatSBS creates for
> users' home folders is messed around with it causes
> script failure, but these shares are still present.
>
> I think the cl;ue is in the name resolution issues. There
> were some technet articles talking about name resolution
> issues, but their causes were not the same as the ones
> that I am experiencing.
>
> Gibbo
>
> >-----Original Message-----
> >I think the add user wizard may barf if the share is not
> on the sbs box
> >itself. Or, it won't barf, but the share will not work.
> >
> >But Dirk-Thomas has the correct method for moving to a
> different location on
> >the SBS.
> >
> >--
> >Les Connor
> >------------------
> >[SBS MVP]
> >
> >
> >
> >"Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in
> message
> >news:#EYHCIAaDHA.2404@TK2MSFTNGP10.phx.gbl...
> >> Hmmm.. I have always simply note the name and share
> name, stopped the
> >share,
> >> created the folders with the same name, share name,
> permissions and moved
> >> the contents. WE are using UNC \\servername\shared
> folder name so where
> >or
> >> what partition isn't a concern
> >>
> >> Dirk-Thomas
> >>
> >> "gibbo" <gibbo@theoffice.com> wrote in message
> >> news:049201c367dd$d772bc80$a001280a@phx.gbl...
> >> > For about 2 years we have had a Microsoft SBS 2000
> server.
> >> > All data and shares have been located on this server.
> >> > We have also had a member server storing additional
> >> > accounts data. The member server is also used as the
> >> > Primary DNS server, WINS server and DHCP server.
> >> >
> >> > Recently the member server's disk subsystem's
> capacity
> >> > was substantially increased.
> >> > We decided to move home folders from the SBS server
> to
> >> > the member server to alleviate some loading issues
> on the
> >> > SBS server and also to free up some disk space.
> >> > This change was made in two places; In Active
> Directory
> >> > Users and Computers, each users' accounts properties
> were
> >> > modified to point the home drive to the member
> server (H:
> >> > \\servername\sharename). Also, Group Policy was
> modified
> >> > to redirect 'My Documents' from the SBS server to the
> >> > member server.
> >> >
> >> > After two weeks without problems, I removed the home
> >> > folder shares from the SBS server.
> >> >
> >> > When users attempted to log on, some of their login
> >> > scripts did not run resulting in no network drives
> being
> >> > mapped. Some login scripts did run without error, but
> >> > when an attempt was made to expand a drive "Access is
> >> > denied" errors were received.
> >> >
> >> > If I tried to manually map a drive using
> >> > \\servername\sharename, the resource was not found.
> If I
> >> > mapped using \\IP_Address\sharename, the resource was
> >> > found, but 'Access is denied' errors were returned
> when
> >> > trying to expand the share.
> >> >
> >> > At a command prompt, net view \\servername returned
> no
> >> > shares. I even preloaded the netbios cache using
> LMHOSTS
> >> > but could not map drives using netbios names.
> >> >
> >> > While testing, I configured a client with a static IP
> >> > address, and changed the DNS settings.
> >> >
> >> > I eventually recreated empty home share on the SBS
> server
> >> > for each user, which restored functionality. However,
> >> > when clients connect via RAS I still get 'Access is
> >> > denied.' WINS, DNS, etc are configured via DHCP when
> the
> >> > client connects.
> >> > Question 1: Why does\did moving home shares to the
> member
> >> > server cause a problem once the shares were removed
> from
> >> > the SBS server?
> >> >
> >> > Question 2: Why do I still get problems with RRAS
> clients?
> >> >
> >> >
> >> >
> >> > Please help!
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >