DSM-G600, DNS-3xx and NSA-220 Hack Forum
Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Announcement
IRC Channel #funplug on irc.freenode.org
#1 2007-09-11 20:55:10
- Ragheb
- New member
- Registered: 2007-09-11
- Posts: 2
Connecting DNS-323 directly to a PC NIC
Hi Everyone and what a brilliant forum this is. I've been reading it till the early hours this morning and learnt a lot.
I bought myself a DNS-323 as I was getting low on storage and hooked it up via my router which properly assigned it an IP address and then I mapped the 2 drives on my PC. So far so good. What I would like to do is utilise my Gigabit Marvell Yukon 88E8001/8003/8010 socket in my PC which is sitting idle as my router is connected to the other built in 10/100 Nvidia Network controller. When I connect the DNS directly to it via either a regular patch lead or a crossed lead the EasySearch utility finds the DNS but without enabling me to access the configuration web page. The 192.168.0.32 is there in the utility but when I highlight the DNS in the Network Storage Device pane the Configuration button is greyed out..
I know I am missing a step here but I can't put my finger on it an I thought one of you geniuses might have attempted it & I would be grateful for any advise.
My setup is:
Opteron 2.6 Ghz
1 Gig RAM
DFI LanParty Nforce 4
mixed storage IDE & SATA drives
Pioneer DVD-RW 112D
Nvidia 6800 Ultra
DNS-323 with Hitachi 1TB and WD 250GB in STD mode
Offline
#2 2007-09-11 22:25:02
- erostiff
- Member
- Registered: 2007-07-14
- Posts: 30
Re: Connecting DNS-323 directly to a PC NIC
when you use a patch (cross) cable, your connection (dns and pc on that network controller) will be assigned a 169.xxx.xxx.xxx ip
When you use this ip (from dns), normally you should be in the configuration menu.
But it could also be that the configuration utility is looking at the wrong network controller.
Is everything installed properly (is your second network controller active - do you get a connection with limited connectivity).
Using the DNS to assign an ip to the connection (using dhcp from dns) could also be solution.
just some ideas (from the top of my head)
Last edited by erostiff (2007-09-11 22:30:30)
Offline
#3 2007-09-11 22:40:22
- Ragheb
- New member
- Registered: 2007-09-11
- Posts: 2
Re: Connecting DNS-323 directly to a PC NIC
Thx erostiff..You are right that it is getting a limited connection (i.e 169..)
All is installed properly and the modem/router is working fine on the other network port.
I will reconnect to the DNS via the router way / enable the DHCP on the DNS / save settings then restart the DNS but now connected directly to the Gig port of my PC and see what happens and will report back to you guys.
Cheers for the help.
Offline
#4 2007-09-12 10:33:16
- Diddycoon
- Member
- Registered: 2007-08-08
- Posts: 13
Re: Connecting DNS-323 directly to a PC NIC
I'm doing the same as you with a STP cat 6 crossover cable.
I found out if your using two NICs on the one PC your need to put them on two different network segements or they conflict.
Example
192.168.0.1 <--- PC NIC 10/100 #1
192.168.0.2 <--- Router
192.168.1.1 <--- PC NIC 10/100/1000 #2
192.168.1.2 <--- DNS-323
I'm guessing you may be able to do the same thing by just changing the subnet range for each NIC instead, but I have not tried that.
Offline
#5 2007-09-12 11:04:02
Re: Connecting DNS-323 directly to a PC NIC
Diddycoon wrote:
I found out if your using two NICs on the one PC your need to put them on two different network segements or they conflict.
Sorry but this is not really correct 
Your Solution is right, if you are using the same gateway on both devices(in your example this would be 192.168.0.2), but if you leave out the hole gateway-config (and probably also the DNS-Config) on your gbit-interface, it will be fully functional within the same ip-range. I'm using it in that way 
192.168.0.1 <--- PC NIC 10/100 #1 (Gateway 192.168.0.2)
192.168.0.2 <--- Router
192.168.0.3 <--- PC NIC 10/100/1000 #2 (No Gateway and probably no DNS-Config (i've left that out))
192.168.0.4 <--- DNS-323
Offline
#6 2007-09-12 15:20:15
- Diddycoon
- Member
- Registered: 2007-08-08
- Posts: 13
Re: Connecting DNS-323 directly to a PC NIC
Yer I tried it that way the first time but I couldn't access it.
Offline
#7 2007-09-12 15:44:38
- fordem
- Member
- Registered: 2007-01-26
- Posts: 1938
Re: Connecting DNS-323 directly to a PC NIC
DeLaCroix wrote:
Diddycoon wrote:
I found out if your using two NICs on the one PC your need to put them on two different network segements or they conflict.
Sorry but this is not really correct
Your Solution is right, if you are using the same gateway on both devices(in your example this would be 192.168.0.2), but if you leave out the hole gateway-config (and probably also the DNS-Config) on your gbit-interface, it will be fully functional within the same ip-range. I'm using it in that way
192.168.0.1 <--- PC NIC 10/100 #1 (Gateway 192.168.0.2)
192.168.0.2 <--- Router
192.168.0.3 <--- PC NIC 10/100/1000 #2 (No Gateway and probably no DNS-Config (i've left that out))
192.168.0.4 <--- DNS-323
Technically he IS correct - multiple network interfaces should always be on separate network segments unless they are being configured for some sort of load balancing or failover configuration. It should work if the default gateway information is not set, but as the say on TV, "actual results may differ", and you might have to manually edit the routing tables to make it work (BTW - feel free to tell me that there should be no routing involved if the network segments are the same, try telling that to the OS, which still needs to know which interface to send the packets out - it would also probably be better if static ip addresses were set on the two node "mini-network", rather than using DHCP.
Offline