Shared Areas Across a Domain

March 1, 2009 at 03:29:08
Specs: Windows XP, N/a
Hi all,

First off, thanks in advance for the help and advice.

I’m currently having issues with shared data areas across my domain. On my DC I have two shared areas that are located as follows,

File storage
C:\Data – share name is ‘data’ permissions are full for ‘everyone’ and the pc name.

Printer
Printers share name is called ‘hpprinter’ again permissions are set to full control for ‘everyone’

DC name is Tilsed
Netbios name is Tilsed0

The problem occurs when trying to connect to them, if I go to a workstation and tools – map network drive when expanding through the tree the data storage does not appear. If I try to put in \\tilsed\data\ or \\tilsed\c:\data$\ windows cannot find the location.

Same kind of story with the printer if I enter \\tilsed\hpprinter windows cannot find the location.

I have tested this the reverse way by installing the printer locally to a workstation and connecting to it which is fine.

The workstation is using the admin log on credentials.
The workstations shows up in AD
The DC can ping both the computer name and IP of the workstation.
The workstations can ping the IP of the server but not the server name?

If anyone has any ideas or needs more information please just ask and I will try them.

Thanks again,

Steve.


See More: Shared Areas Across a Domain

Report •


#1
March 1, 2009 at 06:09:47
Are the workstations using the same dns ip as the DC uses? Can you map the share by using the ip address of the dc instead of name??

Silence is golden but duct tape is silver


Report •

#2
March 1, 2009 at 06:12:28
C:\Data – share name is ‘data’ permissions are full for ‘everyone’ and the pc name.

Ok, that's on the 'sharing' tab. What have you done with NTFS shares....you know, the "Security" tab? What group/user accounts have you added? What permissions did you assign said groups/users?


If I try to put in \\tilsed\data\ or \\tilsed\c:\data$\ windows cannot find the location.

First, open a command prompt window and try the following:

ping tilsed

Do you get a proper reply? If not, then your issue is a DNS issue. You can of course check the DNS 'host' records for your DC and ensure they reflect the correct name and IP address.

In the meantime, you could connect to that share using the following:

\\server_IP_address\data

At least, you should be able to....if you can't, you have serious issues.

As for the printer....again, what users/groups and what perm's on the Security tab (NTFS permissions)?


Report •

#3
March 1, 2009 at 09:12:33
If the data folder is shared as data$, then you don't put in the full path. sharename would be \\tilsed\data$

As for the printer, you'd go to the workstation you want to print from, select Network Printer, and then enter the computer name. i.e \\tilsed\ as long as you've selected the option to list the Printer in the Directory, the sharename will come up automatically.

EEOC


Report •

Related Solutions

#4
March 1, 2009 at 11:07:57
Hi, thanks for the help you three i have manged to sort a short term problem by using IP.

I have the following,
D link route containing a 4port switch
[quote]IP Address: 192.168.1.1
DHCP: On
PrimaryDNS: 192.168.1.1
Netmask: 255.255.255.0
Default Gateway: 212.74.111.194
Host Name: TilsedR
Domain name: tilsed.com [/quote]
Server / DC
[quote] Host Name . . . . . . . . . . . . : tilsed
Primary Dns Suffix . . . . . . . : tilsed.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : tilsed.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1B-B9-A5-BE-46
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.4[/quote]

Workstation
[quote] Host Name . . . . . . . . . . . . : right
Primary Dns Suffix . . . . . . . : tilsed.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : tilsed.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1B-B9-A5-BE-46
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.4[/quote]

How would i go about resolving this issue in the long run?

Thanks again you have been great!


Report •

#5
March 1, 2009 at 12:40:59
Seems the DNS adress is the problem... The dns adress should be the IP adress of the server or at the ip adress of the dns server ,if your current server isnt running DNS ....


I would use your server to act as a DHCP server rather than having the router do the job... then you will be able to connect via the name of the PC rather than the IP adress..


Report •

#6
March 2, 2009 at 02:33:26
Thanks again,

So to sum up,

Leave the routers primary DNS pointing to itself or should it be pointing to the server? Turn DHCP on the router off, and enable on the server and all should be well?


Report •


Ask Question