asked on
Unable to Map a Network Drive
Hello Experts,
I have a Windows 2008 Server configured as domain control.
It has two ip addressess, 192.168.1.25 and 10.1.30.140.
I can map a network drive to 192.168.1.25, but I can't map a network drive to 10.1.30.140.
I'm certain it's a simple problem, but I can't figure out why I can't map a drive to 10.1.30.140.
Any thoughts will be greatly appreciated.
Cheers
I have a Windows 2008 Server configured as domain control.
It has two ip addressess, 192.168.1.25 and 10.1.30.140.
I can map a network drive to 192.168.1.25, but I can't map a network drive to 10.1.30.140.
I'm certain it's a simple problem, but I can't figure out why I can't map a drive to 10.1.30.140.
Any thoughts will be greatly appreciated.
Cheers
Windows OSNetworking
Last Comment
arnold
ASKER
Hi Lee,
As you can see from the image I can map a drive to 192.168.1.25 but I can't map a drive to 10.1.30.140
![access]()
As you can see from the image I can map a drive to 192.168.1.25 but I can't map a drive to 10.1.30.140
Do you want 10.1.30.140 as the main IP to map your drive ? or the 192 address ?
what is the reason for having 2 IP addresses ?
I think you may need to change the network connection nic binding order.
https://technet.microsoft.com/en-us/library/cc732472(v=ws.10).aspx
what is the reason for having 2 IP addresses ?
I think you may need to change the network connection nic binding order.
https://technet.microsoft.com/en-us/library/cc732472(v=ws.10).aspx
ASKER
Hi Zaheer,
Yes, I would like the 10.1.30.140 as the main ip to map to my drive.
The address 192.168.1.25 is just used to connect to the Server via RDP.
Cheers
Yes, I would like the 10.1.30.140 as the main ip to map to my drive.
The address 192.168.1.25 is just used to connect to the Server via RDP.
Cheers
ASKER
Hi Zaheer,
I have placed Local Connetion 2 - ip address 10.1.30.140 at the top, but still no luck. Do I need to reboot server?
![access]()
I have placed Local Connetion 2 - ip address 10.1.30.140 at the top, but still no luck. Do I need to reboot server?
Yes please restart.
ASKER
Restarted, but no luck :-(
ok sorry I missed that this is a DC. Which ip address was the first one to setup when you first joined it to the domain ?
What happens when you try hostname ?
What happens when you try hostname ?
ASKER
When I ping the host name n30-dc I get the response 10.1.30.140.
Which makes it even more puzzling why I can't map to 10.1.30.140
Which makes it even more puzzling why I can't map to 10.1.30.140
Is the windows firewall on ?
ASKER
Windows firewall is turned off
what happens if you try and map via \\hostname\ then ?
was the share created on which IP address ? when both ip addresses were configured.
was the share created on which IP address ? when both ip addresses were configured.
ASKER
I get same result as when I map IP address 10.1.30.140 - unable to map
can you map the drive on the domain controller itself ?
Can you try to do ipconfig /flushdns on client and test.
Can you try to do ipconfig /flushdns on client and test.
ASKER
Yes, I can map the drive on the controller itself - which makes this problem even more strange
ok another test can you enable disable the network cards, as in disable the 192.168 nic and see if that works?
ASKER
Zacheer
I tried disabling 192.168.1.25 before coming to EE, but no luck.
Interestingly, I can ping 10.1.30.140 and when I do nslookup I see 10.1.30.140
I tried disabling 192.168.1.25 before coming to EE, but no luck.
Interestingly, I can ping 10.1.30.140 and when I do nslookup I see 10.1.30.140
ok just had another thought under TCP/IP setting DNS tab do not allow 192.168 address to register to DNS.
What was the primary IP of the DC when you added it as a domain controller ?
What was the primary IP of the DC when you added it as a domain controller ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Do not allow 192.168 address to register to DNS.
How do I do that?
How do I do that?
The below MS article explains it
https://support.microsoft.com/en-us/help/2023004/steps-to-avoid-registering-unwanted-nic-s-in-dns-on-a-mulithomed-domain
.
https://support.microsoft.com/en-us/help/2023004/steps-to-avoid-registering-unwanted-nic-s-in-dns-on-a-mulithomed-domain
.
ASKER
That did it. Thanks
What was the fix ?
ASKER
My apologies,
Zaheer provided the correct answer with the following link:
https://support.microsoft.com/en-us/help/2023004/steps-to-avoid-registering-unwanted-nic-s-in-dns-on-a-mulithomed-domain
Thanks Zaheer
Zaheer provided the correct answer with the following link:
https://support.microsoft.com/en-us/help/2023004/steps-to-avoid-registering-unwanted-nic-s-in-dns-on-a-mulithomed-domain
Thanks Zaheer
Report your question, and request to have it reopened.
Check your firewall settings.
What errors are given by the client(s)? Are there errors in the event log? Why is the machine multi-homed?