Could you explain this a bit more? This doesn't really make sense to me from a technical standpointIm not sure if this classifies as "Tech Discussion" but i needed to get this out.
So if you are on wifi and you randomly time out, the solution is changing to a static IP, if anyone needs help with that subject just comment below.
Yeah my thoughts too.Uhm... what?
Could you explain this a bit more? This doesn't really make sense to me from a technical standpoint
Yeah my thoughts too.
Ok, so pretty much if you live in an apartment building or in a place with a couple wifi connections then this will happen:Uhm... what?
No sorry that still doesnt make any sense from a networking standpoint. A dynamic IP doesnt change as it's in use. It has a lease expiry time that is generally a few days. You can't just 'cross' on to another network, even if it's open with no encryption unless they both had the same SSID, part of same subnet etc. You cant just 'walk' into another wireless network, that's absurd really. It defeats the whole concept of wireless networking and security.Ok, so pretty much if you live in an apartment building or in a place with a couple wifi connections then this will happen:
Because you dont have a static IP then the ip changes the last few numbers up and down and up and down, and since theres another network it can change to the same IP which leads to a timeout.
To prevent that just lookup how to set a static IP, if it doesnt work then the issue is different.
(This worked for me and only times i get out of the game is getting kicked for ping but thats rare too)
well if i personally go to cmd and write "ipconfig /all" i can see my ip... if i do the same command 10minutes later the last 3-4 numbers of the ip will change...(until i put a static IP)No sorry that still doesnt make any sense from a networking standpoint. A dynamic IP doesnt change as it's in use. It has a lease expiry time that is generally a few days. You can't just 'cross' on to another network, even if it's open with no encryption unless they both had the same SSID, part of same subnet etc. You cant just 'walk' into another wireless network, that's absurd really. It defeats the whole concept of wireless networking and security.
I think you might find that when you set your static IP, you're resetting your network connection and any fix for a timeout is coincidental. You might find either you have an IP clash on your network, or your router is terrible/buggy firmware/overloaded and cant keep up with the sessions.
If your IP is changing that rapidly, then you must have a crazy small DHCP lease time set on your router, you should increase that to several days or yes you could in theory have problems with Dynamic IPs, but they shouldn't be re-assigned until your machine makes a new request for one - usually when it re-connects to the network after a shutdown or sleep event.well if i personally go to cmd and write "ipconfig /all" i can see my ip... if i do the same command 10minutes later the last 3-4 numbers of the ip will change...(until i put a static IP)
and i dont just "walk" into another network, i live in israel and internet connections overall are built diffrently and if 2 people have the same internet provider "walking" on other networks is very possible... and it kept happening to me until i fixed it with a static IP, i tried reseting my network several times and it didnt work so what you are assuming isnt possible.
For example im on "Bezek" Internet provider and my neighbor is using "Bezek" as well, than since we use same IP family for example: 192.168.0.xxx then only difference between us is the last 4 numbers, and since sometimes it changes (for me every 5 minutes) we can accidentally use the same IP.
I cant asses the situation because i dont understand the subject that well, im just here explaining what worked for me personally, and still does for 4 days now.
@ZeitoThanks for the insight anyway, I see you have knowledge in the subject.
I have tried using dhcp relay but my internet down speed went to 0.5 so i couldnt stay with that so seems like static IP is only solution...If your IP is changing that rapidly, then you must have a crazy small DHCP lease time set on your router, you should increase that to several days or yes you could in theory have problems with Dynamic IPs, but they shouldn't be re-assigned until your machine makes a new request for one - usually when it re-connects to the network after a shutdown or sleep event.
Cross-Talk is possible if there are a lot of networks in the same area on the same RF channel, but even with the most basic of WEP security, there wont be any exchange of data and you wouldn't suddenly find yourself on your neighbours wireless network.
192.168.0.0 is a private address space, traffic on that network wont route to another 192.168 network unless they are actually linked and openly exchanging traffic, otherwsie they wouldnt work as private address spaces. For example - I'm on PlusNet here in the UK, and if my neighbours are on PlusNet, I dont just have access to their network because that'd be insane.
Like I said, your assignment of a static IP to yourself is most likely coincidental if your router has extremely low DHCP lease times of only a few minutes, your WiFI RF channel is massively over-crowded, or your Router is messed up or just not up to the task of serving a wireless network.
As far as i'm aware IL doesn't use carrier-grade NAT where the State would control all internet access and effectively the whole country is on a big LAN. This happens in some places like Qatar or Saudi Arabia i think.
Don't get me wrong though - I'm not having a go at you or anything, but your understanding of networking and wireless infrastructure isn't good as you say. I suggest you have a poke through the settings of your router and check out the DHCP settings, see what your leas time etc. is, you might find that adjust a few parameters will better your internet connectivity.
I'd be interested to see a few screenshots over the space of say 30 minutes doing an ipconfig /all to see just how often that address is changing. Here's a snip of my computer here at work, you can see the highlighted lines are the DHCP lease time. This is how often my machine would possibly change dynamic address. In smaller networks like a home network, it wouldnt be uncommon for one machine to get the same dynamic address at lease renewal. One thing you should be aware of though when setting a dynamic IP yourself - is to set it outside your DHCP pool, this is a range of addresses say from 192.168.0.1 - 192.168.0.128 that your router hands out from, if you set a static ip within that range, it's POSSIBLE ( though unlikely) that your router can hand out the same address as a dynamic one, though a lot of routers should be able to pick up on this pre-assigned address
https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol if you want to read up on DHCP in networking further
What do you mean by DHCP relay? You shouldnt be relaying dhcp traffic anywhere - it should just be between your computer and your router.I have tried using dhcp relay but my internet down speed went to 0.5 so i couldnt stay with that so seems like static IP is only solution...
Thanks anyway, this conversation is awesome because it can benefit to people who just came here...
@ZeitoHow come you have extensive knowledge in computers?
In the settings you can use a DHCP relay to change the ip family for exmaple instead of ip starting at 192.168.0.0 it will start at 192.168.0.200 and go up.What do you mean by DHCP relay? You shouldnt be relaying dhcp traffic anywhere - it should just be between your computer and your router.
I work in IT and have been building, and playing around with computers pretty much my whole life. I started with breaking them, then i quickly learned how to fix them and mess about with them.
Can you show me a screenshot? Ideally the only setting you want to look at is DHCP Lease time.In the settings you can use a DHCP relay to change the ip family for exmaple instead of ip starting at 192.168.0.0 it will start at 192.168.0.200 and go up.
We use essential cookies to make this site work, and optional cookies to enhance your experience.