Re: A newbie's adventures with AD - HAAAAAALP!!!

From: Laura E. Hunter \(MVP\) (hunter(nospamplease)_at_sfs.upenn.edu)
Date: 08/02/04


Date: Mon, 2 Aug 2004 14:40:12 -0400

It sounds as though you've verified connectivity from the server to the
client: have you verified that everything's working from the client to the
server? I'm specifically thinking of DNS, here. Can you access a server
share directly, rather than browsing through Network Places?
(Start-->Run-->\\servername\sharename)

If that doesn't work, then you may have a name resolution problem. See if
you can ping the DNS name of the server from the client, and make sure that
the client is pointing to the server for DNS resolution. You should also
open the DNS console and verify that all of your server records have been
created within DNS.

-- 
******************************
Laura E. Hunter - MCSE, MCT, MVP
Replies to newsgroup only
"Sam" <noluckschmuckNOSPAM@ev1.net> wrote in message 
news:hqssg09197clbpl338vkptgfm2dip7b7pa@4ax.com...
>
> Hi,
>
> I've gotten my network, DHCP (authorized), DNS, File Server,
> and active directory set up with Windows 2003 server
> (Enterprise Edition).
>
> My client (Windows 2000 Pro) is a part of my (only) domain,
> and I can see it from my server,
> and I can access all the shares on the client from the server.
>
> I have published shares on the server in active directory,
> but I cannot see any of them on the client.
>
>
> In system explorer on the client:
>
> My Network Places > Entire Network > Directory
>
> I can see the Domain Name ("DNS-Domain-01"),
> but there's nothing there - it's empty.
>
> Can anyone give this poor fool a clue as to what the problem is?
>
> It's probably something simple that I've overlooked.
>
>
> Someone from another group gave me a link to a page from the MS Knowledge 
> base,
> and that helped immensely:
>
>>Publishing a Shared Folder in Windows 2000 Active Directory
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;234582&Product=win2000
>
>
> I did as instructed ...
>
> 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 entirely.
>
> 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!!!
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
> Users can see this volume while browsing Active Directory. To browse 
> Active Directory:
>
> 1. On the desktop, double-click Network Neighborhood or My Network Places.
> 2. Double-click Entire Network.
> 3. Click Entire Contents.
> 4. Double-click Directory.
> 5. Double-click the domain name, and then double-click TestOU.
> 6. To view the files in the volume, either right-click the
>   Published TestShare volume and then click Open, or double-click 
> Published TestShare.
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
> To search Active Directory for published shares:
>
> 1. On the desktop, double-click Network Neighborhood or My Network Places.
> 2. Double-click Entire Network.
> 3. Click Entire Contents.
> 4. Double-click Directory.
> 5. Right-click the domain, and then click Find.
> 6. In the Find box, click Shared Folders.
> 7. In the Named box, type the name of the shared folder you want to find.
> 8. Click Find Now.
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
>
> 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?
>
> Do I need to do something on the server to tell it that the client
> is a part of the OU?
>
> What am I missing?
>
> Can any of you geniuses clue me in?
>
>
> *beats head against wall*
>
>
> - Sam 


Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)