Windows 7: Unable to Map NAS on 2nd NIC in Win 7 Ultimate

newbie1234 · 12 Feb 2010

HI there,

I am having a problem with my Dlink DNS 323 on my Win 7 Ultimate. I have 2 nic on my system. 1st one is 100mbps built in on my motherboard, this nic is connected to my router for internet usage.

My 2nd NIC is a 1000mbps PCI card. I want to connect my DNS 323 on this nic. But i am having problems access it. I do not know why.

My DNS 323 works fine if i plug it into my router i can map it using its default IP 192.168.0.32

When I plug my DNS to my 2nd NIC card. I used a Static IP which is 192.168.1.1 with subnet mas 255.255.255.0 with no gateway.

Why am i unable to Map my Drives in Win 7. Im able to ping my NAS but just unable to Map it.. May i know how can i fix this problem?

newbie1234 · 12 Feb 2010

HI guys,

I have set the IP for my NIC to 192.168.1.1 and my NAS to ip 192.168.1.2. Im able to Ping and access my Configuration Page in my NAS. But im unable to Map my drive in Win 7. I getting and error mentioning that Network path not found..

aem · 12 Feb 2010

Are you wanting to connect from W7 directly to the NAS?

newbie1234 · 13 Feb 2010

Quote: Originally Posted by aem

Are you wanting to connect from W7 directly to the NAS?

Yes I want to Map my Network Drive from W7 directly...

I do not know why when i try to map \\192.168.1.2\Volume_1 i cant map

I can ping my NAS without any issues.. But why it just doesnt want to map..

aem · 13 Feb 2010

As someone has tried, if you just want to connect from A to B using basically a cross-over cable, you can put in almost any IP. But i would stick with what you have working on your other NIC

What is the ipconfig /all details of that?

newbie1234 · 13 Feb 2010

Quote: Originally Posted by aem

As someone has tried, if you just want to connect from A to B using basically a cross-over cable, you can put in almost any IP. But i would stick with what you have working on your other NIC

What is the ipconfig /all details of that?

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCI GBE Family Controller
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e838:7a22:b85e:ec51%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 318770734
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D2-10-0D-40-61-86-4A-FA-7E

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f532:8296:2976:9821%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.16(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, 11 February, 2010 11:38:15 AM
Lease Expires . . . . . . . . . . : Saturday, 13 February, 2010 1:39:29 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 255877510
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D2-10-0D-40-61-86-4A-FA-7E

aem · 13 Feb 2010

So your Ethernet adapter Local Area Connection 2: is what you want to link with to your NAS?

Edit tcp/ipv4 to be:

192.168.0.20
255.255.255.0
192.168.0.1

These are just numbers.

From your NAS (tcp/ipv4 configure):

192.168.0.21
255.255.255.0
192.168.0.1

Then try the ping test to see if you can ping your NAS.

newbie1234 · 13 Feb 2010

Quote: Originally Posted by aem

So your Ethernet adapter Local Area Connection 2: is what you want to link with to your NAS?

Edit tcp/ipv4 to be:

192.168.0.20
255.255.255.0
192.168.0.1

These are just numbers.

From your NAS (tcp/ipv4 configure):

192.168.0.21
255.255.255.0
192.168.0.1

Then try the ping test to see if you can ping your NAS.

Yes Local Lan 2 is my NIC thats linked to my NAS.. May I know why am i using the Gateway Ip that is the same for my router? Could you explain this pls? Thanks

newbie1234 · 13 Feb 2010

Quote: Originally Posted by aem

So your Ethernet adapter Local Area Connection 2: is what you want to link with to your NAS?

Edit tcp/ipv4 to be:

192.168.0.20
255.255.255.0
192.168.0.1

These are just numbers.

From your NAS (tcp/ipv4 configure):

192.168.0.21
255.255.255.0
192.168.0.1

Then try the ping test to see if you can ping your NAS.

I have set the IPs to wat you had mentioned on both sides. Pinged and able to receive reply perfectly. When i try to map from Win 7 it doesnt want to Map? Why does my Local Area Connection 2 shows Unidentified Network

aem · 13 Feb 2010

The default gateway theoretically should be your first machine of your immediate network. It should be assigned the first IP available which is, in your case 192.168.0.1. Your router, although is not a computer, still needs an IP address. From your ISP/modem, the router is the first device on the network.

Sometimes manually assign IP thru the NICs can take time to work. Just press F5 to refresh.