Hi all,
I have just recently encountered a problem on two different dlink routers (DI-825) and (DI-635)
After a clean setup and install of the routers, setup with wireless and wired clients.
The wireless clients can attach, but the wired clients cannot. When I log off with one of the wireless clients and reconnect the router throws an address such as 192.168.100.13. w/ a default gateway of 192.168.100.1.. yes the dhcp range I have is 192.168.0.50 to 192.168.0.100.. with a normal gateway of 192.168.0.1 I cannot figure out how the router is assigning an address outside of this range when I set all clients to be managed by dhcp.
This is even more of an issue as of my 5 devices on the network only two get addresses with the dhcp range while the others do not.
The odd part is I have tried this with two new (different) routers and the same thing occurs.. The modem appears to be functioning fine and after a few ours with comcast trying to break this problem down further it appears (for now) to not be the modem.
Has anyone ever come across this before?
Thanks for the insight.
I have just recently encountered a problem on two different dlink routers (DI-825) and (DI-635)
After a clean setup and install of the routers, setup with wireless and wired clients.
The wireless clients can attach, but the wired clients cannot. When I log off with one of the wireless clients and reconnect the router throws an address such as 192.168.100.13. w/ a default gateway of 192.168.100.1.. yes the dhcp range I have is 192.168.0.50 to 192.168.0.100.. with a normal gateway of 192.168.0.1 I cannot figure out how the router is assigning an address outside of this range when I set all clients to be managed by dhcp.
This is even more of an issue as of my 5 devices on the network only two get addresses with the dhcp range while the others do not.
The odd part is I have tried this with two new (different) routers and the same thing occurs.. The modem appears to be functioning fine and after a few ours with comcast trying to break this problem down further it appears (for now) to not be the modem.
Has anyone ever come across this before?
Thanks for the insight.