d-link just sucks

[holyium]

I recently purchased a wireless D-link DI-624S its like one of the best offered by the company atm i think. well... i also have another router that uses wires from Dlink and use it to connect all my computers. the problem lies with the routers firstly i attempted to connect the wired router to my cable modem then connect my DI-624S to my wired router using the WAN port of course to connect to a ethernet network port. I contacted Dlink support and they gave me instructions to resolve the conflicting issue where i can connect to the internet but when i load a web browser or any other program there is no data transfering. i typed in yahoo.com and u know when the url changes... does that mean there is internet connection present... although the url does change the browser indicates that there may be something wrong with my connection... can anyone help me with this conflicting issue of having two routers and a cable modem? will it require the alteration of the TCP/IP of the network or will i need to buy a hub or switch watever that is? I seriously need help as i know for a fact that Dlink cant.

[Whyzman]

Welcome tohttp://www.pcguide.com/ubb/pcgubb.gif Forums!

Can dlink walk you through the setup until you have a web connection?

[jlreich]

There are several issues when using two routers.

First, you may or may not need to use a cross-over cable instead of a regular ethernet cable to connect them together.

Second, one of them needs to have DHCP turned off. They cannot both be trying to dish out IP addresses or you have problems, like the ones your are having.

If you don't have a need for more than four wired connections the easiest thing to do is remove the wired router and just use the new wireless router for everything. ;)

How many computers do you have on your LAN? How many wired and how many wireless?

What's the model# of the wired router?

[Variable]

Simple problem, routers route network traffic based on IP, if you add a router to a router you need to have a separate network for your wireless LAN side.

Assume you have the wired router working as it should and you plug a cable into one of the switch ports and then connect it to the wan side of the wireless router. The Wireless WAN side interface can get a IP address from DHCP running on the Wired router or you can hard code it. Either way will work. For the LAN side of the wireless router you need to configure a different network. So if the default LAN network for the wired router is something like 192.168.1.x with a 255.255.255.0 mask, you would configure the wireless LAN side to be 192.168.2.x with a 255.255.255.0 mask. Wireless clients would get the 192.168.2.x address from DHCP running on the LAN side of the wireless router. Since you have two devices from the same manufacturer both will likely give out the same LAN address and DHCP range. This would cause a problem, as a packet returning would get confused as to where it goes. Two computers could both have the same IP...

Connect a PC to the wireless router with a cable, get an IP address, Change the LAN side IP address as above (write it down) and this should update the DHCP lease range but check to make sure. Save the changes, open you LAN properties on your PC and disable and re-enable the LAN. This will drop the IP it received and try to get a new one from the new lease pool. Open a browser and type in the IP you changed the LAN side to. Change the WAN side to DHCP and save the settings, connect the wan port with a cable to a switch port on the wired router. Wait a minute and then try to ping google.com from your pc. If you get confused, reset the router and start over. Once you get it working and you feel more comfortable you can manually assign the WAN side of the wireless router. Best way to do this is get DHCP working and look at what networking information is given. Add 100 to the last octet and you should be safe. So if the WAN side of the wireless router gets a DHCP assigned address of 192.168.1.5 then you could safely change it to 192.168.1.105 manually assigned. All the other information will be the same, so write it down, and then change the last octet after taking off DHCP and manually assigning the settings. If it doesn't work set it back to DHCP and try again. It really depends on how interested you are in learning how it works or just making it work. That's up to you.