Re: Newbie having a problem with AD

From: ptwilliams (ptw2001_at_hotmail.com)
Date: 08/02/04 

Date: Mon, 2 Aug 2004 18:55:29 +0100

Firstly thanks for clearing up my misconception of whether or not you can
browse published shares through the directory portion of nethood!! It must
be only printers that you can't do this for...

Secondly, what happens if you look for shares in this way as an
administrator? Or what happens if you do this on one of the DCs? Before I
start troubleshooting directory problems like DNS, services, etc. with you I
want to rule out user rights...

You should verify that clients are pointing to an internal DNS server either
by checking your DHCP scope or by running ipconfig /all on a client and
comparing the results against your records...

All internal clients (servers, DCs, and PCs) have to point to the internal
DNS server when in an AD environment. 

-- 
Paul Williams
_________________________________________
 http://www.msresource.net
Join us in our new forums!
  http://forums.msresource.net
_________________________________________
"Sam" <noluckschmuckNOSPAM@ev1.net> wrote in message
news:n4qqg0lhu3grj6dsfae6nssgh2ik437dci@4ax.com...
To further elaborate ...
I've created an Organizational Unit on the server, then populated it with
a few shares - one for a folder on logical drive I, another for logical
drive K.
Both shares have been published in AD.
On the server (called "WSVR-2003E-01"), in Computer management, system
tools,
shared folders, shares ...
Under the share name column, I have 'Folder-on-drive-I-share'
[path - F:\server downloads],
with the number of client connections showing 0.
I right click on it, hit properties, the publish tab, and the path
to shared folder is:
\\WSVR-2003E-01\Folder-on-drive-I-share
Publish this share in Active Directory is checked, BTW.
Also under the share name column, I also have 'Drive-K-Share'
[path - K:\],
with the number of client connections also showing 0.
I right click on it, hit properties, the publish tab, and the path
to shared folder is:
\\WSVR-2003E-01\Drive-K-Share
Publish this share in Active Directory is also checked.
Now on to Active Directory Users and Computers ...
Under the Domain name ("DNS-Domain-01.com"), I have
(in the tree on the left pane)
"Organizational Object 01".
In the right pane, I have two entries for the OU:
Drive I share on WSVR-2003E-01     shared folder
Shared K drive on WSVR-2003E-01    shared folder
With the first one (the Drive I share), I right click on it,
hit properties, then the general tab, and under UNC name, it shows:
\\WSVR-2003E-01.DNS-Domain-01.com\Folder-on-drive-I-share
With the second one (the Drive K share), I right click on it,
hit properties, then the general tab, and under UNC name, it shows:
\\WSVR-2003E-01.DNS-Domain-01.com\Drive-K-Share
Does everything look OK so far?
The directory entry for the domain name ("DNS-Domain-01.com")
still turns up empty on the client for Directory under Entire Network.
GRRRRR!!!
I clicked on find, told it to search for published shares, and it found
nothing.
Do I need to do anything WRT "broadcasting" the presence of the OU to the
network?
What am I missing?
- Sam

Relevant Pages

  • RE: How to Grant Power Users rights to administrative shares.
    ... This is on windows server 2003. ... right click shares and select new file share ... The "Create A Shared Folder Wizard" opens click next. ... Please check the permission settings of the shared folders. ...
    (microsoft.public.windows.server.sbs)
  • Re: samba security
    ... > I scanned my Fedora server with NeWT and found this - should I be ... I've a feeling that this is the way Samba works. ... a null username and a null password, to see which shares are available. ... So, presumably, Samba exports this information to any client with any ...
    (Fedora)
  • Re: User Access Problem - SBS Server 2003
    ... The My Docs folder is likely set for off-line folders, so they could only be seeing the local copy and nothing at all on the server. ... As far as shares seen on the XP client the only one seen or accesible is ... It just seems odd that it was working, stopped for one XP client and then ...
    (microsoft.public.windows.server.sbs)
  • Re: File Shares Become Unavailable After 15-30 minutes
    ... BDC from NT (it's running Exchange 5.5 and will be removed as soon as ... The shared folder is located on a 2003 member server that ... server with the share is unavailable. ... The client machine is configured with both an INTERNAL ...
    (microsoft.public.windows.server.migration)
  • Migrating from LogonUser to SSPI
    ... The job executable resides on the server in a shared folder. ... the client would run under the LocalSystem account and we ... LOGON32_LOGON_NETWORK logon type. ...
    (microsoft.public.platformsdk.security)
Loading