| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 138935 | 2015-02-12 18:10:00 | VDSL modem/router suggestions please | Tony (4941) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1394249 | 2015-02-19 21:02:00 | Tony, easy fix: If your router is set to 192.168.1.1, set your network adapter to manually use 192.168.1.200, subnet mask of 255.255.255.0 and a gateway of 192.168.1.1 Set the DNS to 192.168.1.1 and 8.8.4.4 Promise the next time your routers DHCP daemon crashes, it'll affect the rest of the network *except* for your laptop then ;) Basically, your router gives out addresses, which it's supposed to, to tell all the PCs how to connect back to it. It's likely starting, as it should, at the lowest one, probably 192.168.1.2, then it gives 192.168.1.3 to the next and 192.168.1.4 to the next The issue here is that the DHCP service is crashing (as it happens, surprisingly a LOT on a large number of routers), and instead of it being clever (As it should be) and saying: "Well I gave Tonys laptop 192.168.1.4 last time, I recall that because it's the same network adapter, so here, your laptop can have 192.168.1.4 again" It says: "Well I gave Tonys laptop 192.168.1.4 last time, but it's come back first and asked me for an IP address so I'll give it 192.168.1.2", and meanwhile something else on your network is saying "Hey bugger off I'm 192.168.1.2, you go away and get your own IP address". Basically, from what I can see here, your router is being dumb. It shouldn't be. Use the DrayTek and your problem will likely go away ;) |
Chilling_Silence (9) | ||
| 1394250 | 2015-02-19 21:22:00 | I assume you already tried another one, but maybe it's the cable?I haven't tried a different cable, but it is brand new - came with the router. It doesn't "feel" like that sort of problem. | Tony (4941) | ||
| 1394251 | 2015-02-19 21:24:00 | Flippen Hell Chill:thumbs: :lol: Thats a comical way of putting it. Spot on of course as to how its meant to work :D | wainuitech (129) | ||
| 1394252 | 2015-02-19 21:31:00 | Tony, easy fix: If your router is set to 192.168.1.1, set your network adapter to manually use 192.168.1.200, subnet mask of 255.255.255.0 and a gateway of 192.168.1.1 Set the DNS to 192.168.1.1 and 8.8.4.4 So how do I set the adapter IP address? If I go Network connections/network card/properties/configure/advanced I can set the network address, but I can't see anything else. I did try changing that at some point, but it didn't seem to stick. If in the properties I select "Client for Microsoft Networks" the properties for that is greyed out. After the flushdns it has been up OK for about 40 minutes, of which about 30 were idle, so that is promising. |
Tony (4941) | ||
| 1394253 | 2015-02-19 22:06:00 | So how do I set the adapter IP address? If I go Network connections/network card/properties/configure/advanced I can set the network address, but I can't see anything else . I did try changing that at some point, but it didn't seem to stick . If in the properties I select "Client for Microsoft Networks" the properties for that is greyed out . After the flushdns it has been up OK for about 40 minutes, of which about 30 were idle, so that is promising . Close -- From Control Panel / Network & Sharing, top left Change adapter Settings/ Right click Local Area Connection ( or if its wireless the wireless connection) Properties / Scroll down TCP/IPV4/ Properties -- Enter details and save . |
wainuitech (129) | ||
| 1394254 | 2015-02-19 22:12:00 | I'm not a network expert by a long shot, but would increasing the lease time setting in the router stop that? Or should it already be long enough to prevent this and the router is playing silly buggers. (lease time is how long the router reserves an allocated IP address for a particular device as I understand it) My Asus router defaults to a fairly long lease time of several days and devices tend to keep the same address through modem resets, internet crashes, pc restarts, etc. In fact when I look at the network map it shows connected devices from months back as still being there unless I do a refresh. I used to manually set IP adresses for everything but I find using DHCP is easier when it's working right, saves having to reset everything if I connect to a different network or router or whatever. |
dugimodo (138) | ||
| 1394255 | 2015-02-19 22:14:00 | Close -- From Control Panel / Network & Sharing, top left Change adapter Settings/ Right click Local Area Connection ( or if its wireless the wireless connection) Properties / Scroll down TCP/IPV4/ Properties -- Enter details and save.Crikey, I knew that (d'oh!). It's so long since I last had to do it I'd forgotten. Thanks. | Tony (4941) | ||
| 1394256 | 2015-02-19 22:30:00 | I haven't tried a different cable, but it is brand new - came with the router. It doesn't "feel" like that sort of problem. Always rule out the basics first. Try another cable. |
Alex B (15479) | ||
| 1394257 | 2015-02-19 22:37:00 | Always rule out the basics first. Try another cable.You're right of course. Everything is working OK atm but if it dies again I'll try a different cable. | Tony (4941) | ||
| 1394258 | 2015-02-20 00:35:00 | Been up for about 3 hours now with no hiccups. Looks like the flushdns did the trick. Of course as soon as I click "post" it will probably die. Thanks everyone for the help and suggestions. |
Tony (4941) | ||
| 1 2 3 4 5 6 7 8 | |||||