A few things you should know, is that an IP of 192.168.0.0 is not a usable IP (at least not with the default subnet mask), and the last IP in the range is not usable either (192.168.0.255), as this is reserved for broadcast on that subnet.
I didnt know about 0.0, but obvious realyl as they all seem to start at 1 dont they? so cool on that, but I did know about 255
I was merely only experimenting more than anything
One of the reasons changing the routers settings can cause problem is due to the default IPs being on different networks. If your pc has an ip of 192.168.1.1 assigned to you by one router, you wont be able to (or at least not easily) be able to access a device with a 192.168.0.x IP. And if you change the IP of the router you can access to 192.168.0.1 then you wont be able to access that either after you accept the changes because your PC will be on a different subnet.
Yes, I see that, which is why I have alos tried the NETGEAR router instead of the LINKSYS, because the Netgear defauly is the same as the DLINK
Linksys = 1.1 / Netgear = 0.1 / DLink = 0.1 - Naturally, at standard the DLINK and netgear will conflict, but if I try changing the DLINK to something like 0.2 although everything does seem to work, I cannot access internet or the LAN.
My advice, try set yout main router to 192.168.0.1, your 2nd router which you use as a switch to 192.168.0.2, and make sure DHCP is set on your main router to provide IPs in the 192.168.0.x range. Once all is done, check that all PCs are correctly assigned an IP in the 192.168.0.x range and that 192.168.0.1 is their main gateway. If that is all correct they should all be able to communicate.
BINGO THATS EXACTLY WHAT I HAVE DONE
However, while everything connected to the LINKSYS ( Or NETGEAR, BUT NOT BOTH AT THE SAME TIME OF COURSE ) works just fine, everything connected to the DLINK does not?
Even if they do get given IPs in the correct range ( 0,x for the NetGear or 1.x for the Linksys )
It still does not seem to want to work?
The only way I can see the above scenario working is if you've connected the WAN port of the second router to a LAN port on the first router.
Thats done.
You say the routers are disappearing after you change their IP addresses. Make sure you are changing the IP address of the PC your connecting from to one in the new range before trying to reconnect to the router or it will disappear.
AH, so you are saying to assing it statically instead of Dynamic?
Right, ok, I will give that a go!
If the router that you want to work as a switch has a gateway address set (and it's using it) then you'll get traffic disappearing into a black hole as it'll try to route traffic through the WAN port which shouldn't be connected to anything.
Well, when I check it, the gateway address is the IP for the Linksys ( The modem-router ). I thought this was correct?
The colour of network cables doesn't tell you anything about how they are wired.
HaHa, no I know that. All my cables are straight through... I have removed all crossover cables, although on my network, it does not matter whether I use straight or crossover, but I am only using coloured cables because there is so many of them behind the back of the switch ( or DLink if I get this sorted out )
If you want to retain access to the setup page of the dlink whilst you mess about with various dlink and router settings the usual solution is to set the dlink's IP to a higher IP range and then set the main router's subnet lower so you can see it
This gives you more room to move the IP addresses of various devices to known accessible locations guaranteed well away from possible IP conflicts.
Setting dlink first on its own, wire in from a PC to a LAN port, repair PC connection
from web config page turn off its dhcp server, set the router address IP to 192.168.2.1 (notice the 2.1)
Apply and reboot
Set up the router, wire in on its own from a pc suing a lan port, repair connection etc
If your router is on 192.168.1.1 sub net 255.255.255.0 and assigns from 192.168.1.64 upwards
then change its LAN subnet to 255.255.0.0, (notice the 0.0) apply and restart
Wire the pc to the router and the router to the dlink using lan ports only.
On restarting router, then pc then dlink you should be able to access the routers and dlinks set up pages on 192.168.1.1 and 192.168.2.1
You can try run>cmd then IPCONFIG /all on the varius PC's to check they have recieved IP's and valid gateways etc from the router via the dlink
You should see connections via the dlink getting IP's from the router in the range 192.168.1.64+ with gateway and dns being the routers address
The most likely error will be if the dlink does not pass on the routers DNS and gateway IP's correctly from the router to its switch and wireless access point.
Quick fix is to set on the PC a manual DNS and gateway thats the same as your router ie 195.168.1.1 . If you also dont get a valid Ip try setting a static ip for the pc say 192.168.1.65, repair or restart etc
OR
try to set gateway and dns on the dlink to the routers IP setting ie 192.168.1.1, (gateway of 0.0.0.0 sometimes works as well) and use automatic ip and dns etc on the PC's
Some routers make you re-enter several values even if want to just change one, if so just enter the known existing details manually
Ok, Im taking in about 50% of that so I will print it off...
255.255.0.0 ? Ok, right, as opposed to 255.255.255.0 I see.
DLINK above the Linksys then? - I see because as they are, the DLINK is 0.1 and the Linksys 1.1
But then when I tried the netgear, I set the DLINK to 0.2 ... or... ?
IPCONFIG did show the gateway of 192.168.1.1 the last time I looked but still would not go online?
What I need to do, to make sure that I am not missing anything out, ir print off all your replies and go through it all completely from scratch... I will do some adjustments that you are all giving me here, but then, I will reset the Linksys-modem/router, and the DLINK-Router.
Many thanks all... Its all confusing to me, but Im taking it in I promise.