S
Steve Steinbeck
I have two issues:
1) I have a desktop that is a member of an AD domain that
cannot access shares on a new server added to the
domain. Others can access this share. This is the
second box to behave in this fashion. I have noted that
these PCs were both first in an NT domain and were
upgradded to W2K. When I try to access the resource I
get Network path not found, I see no obvious reason as to
why these PCs could not access the resource. I have
rebuilt one box from scratch and it is now able to access
the sahre.
2) I thought AD allowed one to map a share object in
active directory making it possible to move the resources
at will. I.E. I have created a share object and pointed
it at a share somewhere on my network. I am able to map
to this resource. I then go in and change the phycial
location of the resource in the share object and yet my
mapping remains the same after rebooting the PC, it still
appears to map to the server/share rather than a share
object. What have I missed or misunderstood??
1) I have a desktop that is a member of an AD domain that
cannot access shares on a new server added to the
domain. Others can access this share. This is the
second box to behave in this fashion. I have noted that
these PCs were both first in an NT domain and were
upgradded to W2K. When I try to access the resource I
get Network path not found, I see no obvious reason as to
why these PCs could not access the resource. I have
rebuilt one box from scratch and it is now able to access
the sahre.
2) I thought AD allowed one to map a share object in
active directory making it possible to move the resources
at will. I.E. I have created a share object and pointed
it at a share somewhere on my network. I am able to map
to this resource. I then go in and change the phycial
location of the resource in the share object and yet my
mapping remains the same after rebooting the PC, it still
appears to map to the server/share rather than a share
object. What have I missed or misunderstood??