FileSharing Probelm

  • Thread starter Thread starter Fred Hammond
  • Start date Start date
F

Fred Hammond

I have a home network setup with 1 Win2k3 server, 1 Win2k Professional
desktop, and 1 WinXP Professional desktop. The domain is called "test" and
both desktops are logged into the domain.

When I share a folder on the win2k desktop, I am able to select a domain
user "joe" to have permission to that folder and I am able to get to that
folder from the other desktop and the server.

However, when I go to share a folder which resides on the XP desktop, I do
not have the option to add any domain users. I am only allowed to add local
users.

Why could this be?
 
you sure its PRO and not home?

Also not sure if this has anything to do with it, did you turn off simple
file sharing?
 
Fred Hammond said:
I have a home network setup with 1 Win2k3 server, 1 Win2k Professional
desktop, and 1 WinXP Professional desktop. The domain is called "test" and
both desktops are logged into the domain.

When I share a folder on the win2k desktop, I am able to select a domain
user "joe" to have permission to that folder and I am able to get to that
folder from the other desktop and the server.

However, when I go to share a folder which resides on the XP desktop, I do
not have the option to add any domain users. I am only allowed to add
local
users.

Why could this be?
Do you see a locations button on the security tab?

Matt
MCT, MCSE
 
See the link below on how to configure dns for an Active Directory Domain.
It MUST be done correctly or problems like what you experience can happen.
In particular your domain controller must point ONLY to itself as it's
preferred dns server as shown by Ipconfig /all and the domain computers
must point ONLY to the domain controller and never an ISP dns server. Also
software firewalls or other "protection" software can cause problems on a
domain and often booting into safe mode with networking can isolate such
problems. I would also check Event Viewer on the XP Pro computer for any
pertinent errors and run the netdiag support tool on it looking for problems
with network connectivity and problems with dns, dclist, and secure channel.
The support tools are on the install disk of the operating system in the
support/tools folder. You should also run netdiag and dcdiag on your domain
controller. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
 
1) There is no "locations" button on the "security" tab.

2) I am logged on as a domain user and not as local admin.

3) I am sure that I am using XP Pro. XP Home can not join a domain.
 
Color me frustrated...both of my desktops are set to use DHCP. I manually
changed my XP Pro box to use the IP of my Win2k3 server (192.168.0.100) for
its DNS. Voila!! All worked fine.

Now, all of my machines are connected to a Netgear MR814v2 Wireless Router
(192.168.0.1) that is acting as a DHCP server. How can I get that router
(in its role as a DHCP server) to give out the IP of my Win2k3 server
(192.168.0.100) as the DNS server for my clients? Becuz as of now, the
wireless router is giving out the IP Address of itself (192.168.0.1). It
would be ideal to have each client be totally set to use DHCP instead of
having to obtain its IP automatically and have to put in the DNS server
manually.
 
Fred Hammond said:
Color me frustrated...both of my desktops are set to use DHCP. I manually
changed my XP Pro box to use the IP of my Win2k3 server (192.168.0.100)
for
its DNS. Voila!! All worked fine.

Now, all of my machines are connected to a Netgear MR814v2 Wireless Router
(192.168.0.1) that is acting as a DHCP server. How can I get that router
(in its role as a DHCP server) to give out the IP of my Win2k3 server
(192.168.0.100) as the DNS server for my clients? Becuz as of now, the
wireless router is giving out the IP Address of itself (192.168.0.1). It
would be ideal to have each client be totally set to use DHCP instead of
having to obtain its IP automatically and have to put in the DNS server
manually.
Your router probably has an HTTP admin interface. Go into the scope option
for DHCP and set the DNS server to your win2k3 box. http://192.168.0.1

Matt
 
The correct way to do it is to configure your domain controller to be the
DHCP server by configuring and activating the scope with the options
configured for the scope that the wizard would prompt you for and then
disabling DHCP on the router and is exactly what I do on my home Active
Directory domain network. Possibly you can configure your router via it's
web interface as in http://192.168.0.1 to dish out the IP address of the
domain controller as the dns server but that is less than ideal in a domain
as it will not have all the options that the DHCP scope would have on the
domain controller. --- Steve
 
Steve, you are absolutely correct and your timing is impeccable. Disabling
DHCP on the router is EXACTLY what I just finished doing. I then set the DC
up as a DHCP server. All is good now.

Thanks to all for your assistance!!!!!
 
Back
Top