Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[NAS newbie]

S0, I finally installed the DNS323 on my network.

Up till then I had 2 wireless laptops, 2 wireless desktops, 2 wired destops, a Wii, and a wireless printer all working in harmony for years without any issues.

Now there are IP conflict issues showing up and I don't know how to fix them.
The 802.11g wireless router is using DHCP for all connections, even the wired ones.
I've nevered used static IP assignments.

I did add  a 5 port ethernet switch to the 4 port wireless router, otherwise the DNS323 would have taken up my last ethernet port on the router without room for future expansion.

When the DNS323 was first installed it was assigned port 192.168.104 and I think what the problem is is that it will not move to another port. The router seems to be assinging that port to other devices and not recognizing the DNS323 being there. Don't know if the router is trying to assign a different port to the DNS323 as it has never appeared on the list of assigned IP address, even though the DNS323 can be accessed once it takes over port 104 and kicks the other device off. Sometimes the router will even show the other device on port 104, but in reality it's the DNS323 as I can access it onthat port and the other device is unable to connect. Every time I'm able to access the DNS323 it shows port 104 in the status tab.

Any ideas on what's going on and the best way to fix this, so once again everything on my network will live in harmony? Can't they all just get along?

Thanks

[D-Link Multimedia]

You could set a static IP address on the DNS-323. Do you know which other device it is having a conflict with? Simply turn that off (or disconnect it). Log in to the DNS-323 and configure the IP as static (to something other than the conflicting address, for example 192.168.0.99 since that is out of your dhcp range) and then save the settings. Turn on your other device (or reconnect) and you should be golden.

[NAS newbie]

I think that solved that problem.
Router's still confused based on what I'm seeing on the DHCP table (two different devices have the same name), but it looks like everything can connect now.

I actually tried to assign it a static IP before posting, but I would change the address in the field, click apply & it would revert back to the old value. Turns out the trick is to click on save and avoid apply all together.

Anyone know why the unit refuses to move from it's original assignment even when it's set up as an HDCP client? Or why it never shows up on the router's DHCP table?

[fordem]

Anyone know why the unit refuses to move from it's original assignment even when it's set up as an HDCP client?

This is how DHCP works - the DHCP client can (and frequently does) request the ip address it last had, and as long as it is available, the server will allow it, and most DHCP servers will offer the last ip address used by a given MAC address.

Or why it never shows up on the router's DHCP table?

The question that needs to be asked here is if what you're looking at is actually the router's DHCP table.  Different router manufacturers do different things, some display a listing of the DHCP server's active (and in some cases inactive) leases, other display a list of the router's arp table.

The basic idea is to show the user what is attached or connected to the router or using it - unfortunately none of the three provides an accurate list - the arp table is probably the most accurate, in that it shows what devices are actively communicating via the router, but, will not display devices that have been inactive for more than a few minutes - a NAS on a LAN, may be in use, but does not communicate via the router (the router & the integrated switch are actually seperate devices sharing a common cabinet and power supply) and so will not be displayed.

[NAS newbie]

This is how DHCP works - the DHCP client can (and frequently does) request the ip address it last had, and as long as it is available, the server will allow it, and most DHCP servers will offer the last ip address used by a given MAC address.

Interesting. This makes the process seem more human. Being creatures of habit, when we get on the train to commute to work we usually seek out the same seat every time. Also apparently just like when we can't get that old familiar seat, some of us will try to get the other person to move. They'll refuse, we'll keep asking, they'll refuse, we'll keep asking, etc. Until the conductor forces us to sit somewhere else. So I guess the question is why did the computer and NAS keep fighting for that one seat & where was the router during all this? 

The question that needs to be asked here is if what you're looking at is actually the router's DHCP table.  Different router manufacturers do different things, some display a listing of the DHCP server's active (and in some cases inactive) leases, other display a list of the router's arp table.

The basic idea is to show the user what is attached or connected to the router or using it - unfortunately none of the three provides an accurate list - the arp table is probably the most accurate, in that it shows what devices are actively communicating via the router, but, will not display devices that have been inactive for more than a few minutes - a NAS on a LAN, may be in use, but does not communicate via the router (the router & the integrated switch are actually seperate devices sharing a common cabinet and power supply) and so will not be displayed.

Based on what you stated I think I'm looking at a table that shows what devices have activity via the router. I've seen devices disappear from this table when they've been idle for an extended time or have been put to sleep. However other computers ethernet connected to the router/switch still show up on this list - except for the NAS. Though I'm starting to suspect it's showing up in disquise. I still have 2 different IP address with the same host name. That host name is the computer I first used to install the NAS. But the IP address is not the one I forced the NAS to, nor does the MAC address match what the NAS status screen claims is it's MAC address. So that mystery continues.

[fordem]

So I guess the question is why did the computer and NAS keep fighting for that one seat & where was the router during all this?

The probability is, that the NAS was in fact configured for a static ip address - if you select the static ip radio button, you'll find that whatever address the unit was at remains in the fields unless you change it - so I'm guessing that the NAS originally got the a.b.c.104 address from the router by DHCP, and that address was inadvertently set as a static address.

The router, completely unaware that the NAS is using that address, will offer it to any host that requests an address, and since it is the responsibility of the requesting host to verify that the address is not in use before accepting it, you would have seen the ip conflict message every time a new address was requested.

ip address conflicts are invariably the result of user error - either a static addressis configured within the lease pool of the DHCP server (the most common cause), or two active DHCP servers exist on the same network, issuing the same range of addresses.