... and its not working.
Well now,that certainly gives us a lot to go on... :mrgreen:
Please give us as many details as possible on your IP addressing scheme as a whole, what exact errors you've encountered, etc.
As far as the switch goes, the EZXS88W is nothing fancy, and there aren't any special configuration settings or the like involved with that device AFAIK. The only thing to keep in mind is that when using the uplink port on that switch, the normal/PC port directly adjacent to the uplink port becomes disabled; the two physical ports are shared internally, so the uplink and PC connections cannot both be used at the same time.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
... the lights on router's ethernet ports would flash quickly and never be able to hold solid...so I'm off to the store today and if it doesn't work with the second one, I'll be back...
Ok- hopefully it's just a duff switch, but if the new gives you problems too, we'll be here... :)
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Um... hang on here- just how many computers do you have on this LAN, and out of those, how many existed "pre-switch installation"?
The error messages you've posted are what you would expect on a network in which the computers are using a mix of dynamically assigned (DHCP) and statically assigned IP addresses, but where the scope of IP addresses handed out by the DHCP server (the router, in your case) overlaps the range of static IP addresses you've chosen.
As an example: You have a network (with or without a switch; the switch really is transparent here) in which the router is configured to assign computer IP addresses via DHCP from the private IP address range of 192.168.1.1 -> 192.168.1.50.
However, you also have 2 computers on that network which you have manually (statically) configured to use the IP addresses 192.168.1.7 and 192.168.1.8. In this scenario, the router has no way of knowing that the IPs 192.168.1.7 and 192.168.1.8 addresses are already in use, and, as those IPs are within its DHCP scope, it tries to assign those IPs to other computers on the network. Since each computer on the network needs a unique IP address, you can see where/why the conflicts occur.
Assuming I'm shooting somewhere close to the bull's eye here, you have two options:
1. Don't use DHCP at all; just configure all of the computers to use static IPs. For smallish networks this is the simpler way to go, although it gets too cumbersome if you have more than 20 or so computers.
2. Reconfigure the router's DHCP scope to use IP addresses which still fall within the same 192.168.1.x network range, but which fall either above or below the range of addresses you've currently used in your static assignments.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Thanks for the info- that explains a lot. Madness indeed; I feel for 'ya. :mrgreen:
With the network configuration you've outlined, it sounds like you'll want to retain the DHCP functionality if for nothing else than the ease of connecting the visiting/floating laptops to the LAN. If so, I'd suggest going the route (no pun intended, of course) of configuring the router's DHCP server settings to use a range (scope) of IP addresses that don't conflict with any IPs that you've manually assigned.
With a network range of 192.168.1.x and a subnet mask of 255.255.255.0, one common configuration is to set the starting address of the DHCP server's scope to 192.168.1.100, and to then assign all static IPs working from 192.168.1.1 (usually used/reserved for the router itself) up to 192.168.1.99.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Apparently the Vonage adapter has some DCHP Server functionality...
Correctomundo!
If you've got Linksys RT312Ps, those are full-blown routers in and of themselves (the "RT" in Linksys product lines indicates "router"), so they can definitely act as DHCP servers. As a matter of fact, DHCP is active by default on those devices, at least the ones I've installed.
Good troubleshooting; glad you got it sorted :)
Does everything appear to be happy in IP Land now? If so, I'll mark this topic as "solved".
I'll throw this link from Vonage's site in here just for reference; it contains info and instructions on connecting vonages devices in different network environments: http://www.vonage-forum.com/setup.html
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Cool- then marked as solved she be... :)
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
