D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Nitehawke on January 06, 2009, 08:39:56 PM
-
Hello,
I have just set up a server that is able to provide the DHCP service on my network (see Amahi.org). It requires that I turn off this function (disable DHCP) in my router. However, once I did this I lost my connection to the router and the internet. Disabling DHCP in the server reduces much of the functionality.
I can access everything on the network (it's all connected through the router) but I cannot see the router in anyway (ping, devices list in Vista or XP, or through the web setup page).
Can this be accomplished?
The router (DIR-655) is connected to a DSL modem running in bridged mode. All the settings in the router are at the defaults with the exception of wireless, which is turned off.
Thanks,
Nitehawke
-
Is your new DHCP server assigning into the same subnet as the DIR-655 was using?
-
funchords,
That's very possible.
I just checked the server and there are two options for IP addresses. I can only select one of the two:
1. Automatically obtain IP address settings (this option is turned off)
2. Statically set IP addresses (turned on)
There are three entries for "Manual IP Address Settings"
Address: (server address) 192.168.1.10
Subnet mask: 255.255.255.0
Default gateway (router): 192.168.1.1
I can't check the settings in the router at the moment (it's off line). Do know what the default settings in the router are? I imagine that the default is 255.255.255.0.
If this is the case (same subnet mask), what is the solution? Should I leave the DHCP enabled and change the subnet mask in the router or change the subnet mask in the server?
Thanks for your help.
-
The default subnet for the router is 192.168.0.1
So unless you changed that in the router, you need to use the same subnet in your PC setup. So 192.168.1.10 needs to be 192.168.0.10
The subnet mask (255.255.255.0) tells you that only the fourth sequence is being watched (the '0'). So get on the same subnet and leave all other setting as they are.
-
Don't forget to tell the server's DHCP needs to point to the 655 as the gateway device, or make the 655 the gateway for the server and have the server act as a proxy for the networks gateway.
-
EddieZ/Lycan,
I guess that's where I'm getting confused. I have not changed any settings in the router other than turning off the wireless feature.
One thing I should state here is that the modem is actually at 192.168.0.1. I believe that, because the modem is running in bridge mode, the router is getting pushed to 192.168.1.1 automatically. Again, this is just a guess on my part because I have not modified any settings in the router. I will have to get the router back on-line to verify this.
??
I let the server set up everything on its own (again I left all settings at their default) and it is calling the router (gateway) 192.168.1.1 while it is set to a static address of 192.168.1.10.
I appreciate your help on this issue. I am currently at work but I will provide more insight once I get the router back on line (and the server off-line).
Keep in mind my inexperience with networking, but I am assuming that the server sees the router as the gateway at 192.168.1.1. I will be back with more details.
Thanks again....
-
Bridge the modem. Connect the modem to the routers wan port. Get the router to connect to the internet. Next step. Configure the routers DHCP to disable. Then configure your DHCP server on your Server machine to reference the IP address of the router as it's gateway. When you do that, the server will handout IPs with the router as the gateway address. Easy.
-
Easy? Easy for you, Mr. Technical Engineer, Global Moderator, uber Member, dude. I get a chill up my spine just thinking about all of this!
Regardless of the outcome, thanks to you, EddieZ, and funchords for helping out. I will use your suggestion exactly as you have stated and let you know the results.
Easy....
-
Easy? Easy for you, Mr. Technical Engineer, Global Moderator, uber Member, dude. I get a chill up my spine just thinking about all of this!
Regardless of the outcome, thanks to you, EddieZ, and funchords for helping out. I will use your suggestion exactly as you have stated and let you know the results.
Easy....
What purpose would life have if there were no challenges (even if you didn't pick 'em yourself) ;)
Let us know how it all went.
Don't forget to tell the server's DHCP needs to point to the 655 as the gateway device, or make the 655 the gateway for the server and have the server act as a proxy for the networks gateway.
Very good addition, Lycan. That's what you get if you want to squeeze the forum in while at work :-\
-
The forum IS my work lol.
-
It's not as hard as it sounds. Take my directions, go one step at a time. You'll understand it better when the interface is right in front of you. I'd wager you're going to have the most difficulty with the bridging of the modem. (dependent on the ISP and MFG of the modem.) I HATE having to bridge modems. It's the most frustrating thing. Well, at least bridging the Westell 6100 is, sheesh.
-
(NOTE: if you use the server as a gateway proxy, then you can run fun little apps and services to monitor and regulate the traffic coming out of your network. If the server is sitting on the LAN side of the router and just acting as the DHCP server, you can use it to monitor the LAN and create restrictions and other fun things like parental controls and bandwidth limiting via Raduis and whatnot. It's a little advanced for where your at, BUT advancing your network's complexity and over all ability is what drives you to learn.
Every time I think I know enough or have learned all the "cool" stuff, I find I don't know ANYTHING and get to learn something new.
-
The forum IS my work lol.
I'm just a Managing Consultant and Systems Integrator...lucky you ;)
-
Does anyone know if the DIR-655 actually moves to 192.168.1.1 if it detects an 192.168.0.1 device or subnet on the WAN side?
-
I'm just a Managing Consultant and Systems Integrator...lucky you ;)
It is not all skittles and beer for anyone. Forums quit being interesting in a hurry when you start lurking them professionally.
-
Don't think so. Default is displayed everywhere as 192.168.0.1, it also was set on this when I connected a PC but no WAN (which is on 192.168.1.x)
-
No, it'll just fail to pull a WAN address.
-
It is not all skittles and beer for anyone. Forums quit being interesting in a hurry when you start lurking them professionally.
Hmmm, was just about to consider a major career change...thanks for saving me ;D
-
funchords,
That's very possible.
I just checked the server and there are two options for IP addresses. I can only select one of the two:
1. Automatically obtain IP address settings (this option is turned off)
2. Statically set IP addresses (turned on)
There are three entries for "Manual IP Address Settings"
Address: (server address) 192.168.1.10
Subnet mask: 255.255.255.0
Default gateway (router): 192.168.1.1
I can't check the settings in the router at the moment (it's off line). Do know what the default settings in the router are? I imagine that the default is 255.255.255.0.
If this is the case (same subnet mask), what is the solution? Should I leave the DHCP enabled and change the subnet mask in the router or change the subnet mask in the server?
Thanks for your help.
Okay, since the DIR-655 default is 192.168.0.1 and that's also your network's gateway, then your server address should be 192.168.0.10, subnet mask 255.255.255.0, default gateway 192.168.0.1.
When you activate the DHCP server on the Amahi server, you'll need to deactivate the one on the DIR-655 Setup = Network Settings - (uncheck) enable DHCP server. Save and reboot.
After making this change and finish configuring your network, I suggest that you power-off, power-on or fully reboot your network devices, including the DIR-655. If you fail to do this, probably nothing bad will happen (maybe warnings in the logs) but your DHCP clients might continuously try to renew leases with 192.168.0.1 and wait until their leases are fully expired before broadcasting and finding the new DHCP server at 192.168.0.10.
-
It is not all skittles and beer for anyone. Forums quit being interesting in a hurry when you start lurking them professionally.
LOL no kidding, have you seen my post count? Sheesh.
-
LOL no kidding, have you seen my post count? Sheesh.
Maybe you could get paid by the post ;D
-
lol thats an awesome idea
-
Would not do that if I were you (unless you're making less now, but that would be child labour wages :) )
-
Would not do that if I were you (unless you're making less now, but that would be child labour wages :) )
100 posts per day here I come!
-
Turning a router into an AP. (http://forums.dlink.com/index.php?topic=40856.0)
-
100 posts per day here I come!
76 thusfar...keep dreaming ;D