Sharing problem w2k3 dc and a member server

September 28, 2011 at 18:07:44
Specs: Windows 2003 Enterprise , QuadCore/6gb
Dear friends,

I am a support technician and a new customer had a problem in add a new PC to its domain.

He has one W2K3 Enterprise DC server box with few users which began with a problem related to add a new machine in domain. I fixed that, forcing the DHCP to provide the DNS address for each machine primarilly pointing to the DC IP (192.168.0.8), and as soon it was fixed, the original problem finished.
But there is a secondary server in LAN, which is a SQL Server (192.168.0.3). And due to software restriction, a mapped drive must be set to S: pointing to \\192.168.0.3\sharsec ou \\serversql\sharsec.

The problem:
Login as a normal user, we can map a W drive to \\192.168.0.8\departamental or \\dcprimsrv\departamental without any problem.
Also we can map a S drive to \\192.168.0.3\sharsec ou \\serversql\sharsec, using the clause /user:username "passwd" ...

But when we try to access W or S, just one of them could be explored.

I could not map shares from different Server.
What do you suggest.

Jose Claudio Claudelino - Brazil - www.smartunion.com.br


See More: Sharing problem w2k3 dc and a member server

Report •

#1
September 28, 2011 at 18:31:05
Was there an error message? What was it?

How do you know when a politician is lying? His mouth is moving.


Report •

#2
September 29, 2011 at 08:37:44
all AD user accounts must exist on the member server. That is step one.

hopefully this was just a mistype
\\192.168.0.3\sharsec ou \\serversql\sharsec.

Is should only be \\192.168.0.3\sharesec
you don't map to a OU and you would never allow user file level access to serversql is that is the folder that houses sql database

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#3
September 29, 2011 at 10:33:41
I'm sure he meant or & not ou.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
September 29, 2011 at 11:23:05
that makes sense :-)

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
September 29, 2011 at 12:04:31
Sorry, the word "OR" in portuguese is "OU" .. I meant OR..


I knew about the problem yesterday, as the customer called my company to analyze and try to fix.

About the share in SQLSERVER server, was a demanding from the Developer in order to store executables to everybody and, following what IT people told me, must have be there, as is.

As I understood, I must have the database-user-for-ODBC also created in the domain.

Basically everybody in such LAN must logon, and see at least the mapped drives below:
S: pointing to \\192.168.0.3\sharsec
W: pointing to \\192.168.0.8\departamental


I will appreciate any sugestion to help me in fix that problem, as I had never seen it although I am studying all books I have.

Also, I thanks for both of us in spending a little time to my problem, and I hope be useful to you in the future (my main area is Linux/UNIX, and I support MS Servers).

Regards,


Report •

#6
September 29, 2011 at 16:32:57

Is there more than one network interface card (NIC) in each server?

Since everything is on the same subnet, I assume there is only one router. Is that correct?

Does the everyone group have permissions to the S & W drives?

How do you know when a politician is lying? His mouth is moving.


Report •

Ask Question