jueves, 09 de febrero de 2012 1:12
Hoping someone can help me. First, here's the architecture:
Subnet #1 = 192.168.20.x
Windows XP Pro 32-Bit SP3 (Not Domain Clients)
Subnet #2 = 192.168.5.x
Windows Server 2008 R2 (Domain Controller)
Windows XP 64-Bit SP2 and Windows 7 64-Bit (Domain Clients)
Point-to-Point firewalls between Subnet #1 and Subnet #2.
Windows Firewall has been disabled on all computers.
I am able to ping the computers from both subnets.
I am able to open a Remote Desktop session to the computers.
My problem is I would like to map the C:\ drive of a computer in Subnet #1 onto a computer in Subnet #2. I have tried the following from "Windows Explorer \ Tools \ Map Network Drive" ...
Unfortunately, this did not work. Can someone please assist me.
Todas las respuestas
jueves, 09 de febrero de 2012 21:27
Running net view \\<computer in subnet 1> returns something? Even if you have Access Denied it means the communication is flowing. The firewall ports are open?
MCP | Microsoft Certified Professional
MCTS 70-640 | Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
MCTS 70-642 | Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
lunes, 13 de febrero de 2012 6:42Moderador
Thanks for posting here.
> Unfortunately, this did not work. Can someone please assist me.
What was the error prompt when attempted to access this path by using Windows Explorer?
> My problem is I would like to map the C:\ drive of a computer in Subnet #1 onto a computer in Subnet #2. I have tried the following from "Windows Explorer \ Tools \ Map Network Drive" ...
Have we shared the petition C on that host with specifying share and NTFS permission in order to control the incoming accessing ?
Try to access via \\192.168.20.3\c$ with specifying the credential of the administrator account on host 192.168.20.3 in map network drive panel and see how is going.
TechNet Community Support
lunes, 20 de febrero de 2012 19:58
Thank you for your responses. I resolved the issue by selecting "Connect using different credentials" when mapping the network drive.