Ultimate test...

Is it possible that there are other devices connecting into your network and that 'maybe' you've maxed out your DHCP lease pool?
I'd check the logs on the router to see if the IP for your tp-link adaptor is being released, or if it simply is a matter of signal drop.
Also, any other devices in the house that use or can interfere with RF technology, ie. wireless AV senders, wireless thermostats etc?

Have you confirmed that when you lose the internet your wifi signal is also lost?
If you still have signal try accessing google by IP rather than DNS
http://173.194.67.94, see what happens.

If you do the following in a cmd prompt:
ping 173.194.67.94 -t this will give you a continuous ping to google.co.uk. Keep it running in the background. When you lose connection check to see if you get any time-outs.
You could also run a simultaneous ping for dns in another cmd window
ping www.google.co.uk -t
See if that reports time-outs too. If one does and one doesn't then there may well be dns issues somewhere in your pc or router.
You could try ipconfig /flushdns on your pc.

Let us know...unless you think you've already solved it by having a dead zone of a room.
 
Banzai_Joe said:
Is it possible that there are other devices connecting into your network and that 'maybe' you've maxed out your DHCP lease pool?
I'd check the logs on the router to see if the IP for your tp-link adaptor is being released, or if it simply is a matter of signal drop.
Also, any other devices in the house that use or can interfere with RF technology, ie. wireless AV senders, wireless thermostats etc?

Have you confirmed that when you lose the internet your wifi signal is also lost?
If you still have signal try accessing google by IP rather than DNS
http://173.194.67.94, see what happens.

If you do the following in a cmd prompt:
ping 173.194.67.94 -t this will give you a continuous ping to google.co.uk. Keep it running in the background. When you lose connection check to see if you get any time-outs.
You could also run a simultaneous ping for dns in another cmd window
ping www.google.co.uk -t
See if that reports time-outs too. If one does and one doesn't then there may well be dns issues somewhere in your pc or router.
You could try ipconfig /flushdns on your pc.

Let us know...unless you think you've already solved it by having a dead zone of a room.
Click to expand...


I will try this tonight when i get home, i tried to ping google and my router page when i was on the o2 wireless box and both got a response but i dident have access to the net, most of the time its saying i have limited connectivity.

With the new virgin media router i'm getting a better signal but its still having issues 80% of the time, i was literally about to buy the powerline adaptors that are on offer and say f%&k it, as nothing beats an ethernet connection.

but with my track record with the internet i bet they still wouldent work.

edit: i have no other wireless items in the house , theres my desktop and my girlfirends laptop, but the laptop also loses connection in my room
 
Is that two active network connections I see there? I previously had issues when I had two active at once. Try disabling one and see if it works?
 
Both the TP-Link (Wireless) and Realtek (Cabled) show DHCP leases - do you have an Ethernet cable plugged as well?
 
google ping while working

C:\Users\Admin>ping 173.194.67.94

Pinging 173.194.67.94 with 32 bytes of data:
Reply from 173.194.67.94: bytes=32 time=30ms TTL=48
Reply from 173.194.67.94: bytes=32 time=26ms TTL=48
Reply from 173.194.67.94: bytes=32 time=41ms TTL=48
Reply from 173.194.67.94: bytes=32 time=28ms TTL=48

Ping statistics for 173.194.67.94:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 41ms, Average = 31ms
 
You really need to add the -t switch so it performs a continuous ping, then you'll be able to see the dropouts when you lose connection/signal.
 
Sorry i missed that out, i connected at around 6 pm last night and got a decent connection without dropout, i still might pick up the powerlines simply because i'll get more from it than the wireless connection and it will be more stable, i'll test it over the next few days, if i repeatedly get the issue, i'm going to buy them while there on offer
 
Bear in mind that some powerlines don'y work so well either. Some don't like crossing RCD's or going across separate ring mains. Some don't even like being plugged into cable extensions.

You'll certainly not get the throughput they claim on the box, but it may improve over your wifi.
 
This is 2 separate sets of ping test to Google when i dropped out, i was normally playing dayz, i had performed a broadband speed test before starting and got 25mbps on my wirelesss dongle, suddenly after an hour i dropped out started getting really poor connection so i ran these two tests and tried to browse.

C:\Users\Admin>ping google.co.uk -t

Pinging google.co.uk [74.125.132.94] with 32 bytes o
Reply from 74.125.132.94: bytes=32 time=680ms TTL=48
Reply from 74.125.132.94: bytes=32 time=866ms TTL=48
Request timed out.
Reply from 74.125.132.94: bytes=32 time=106ms TTL=46
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=36ms TTL=46
Reply from 74.125.132.94: bytes=32 time=30ms TTL=48
Reply from 74.125.132.94: bytes=32 time=315ms TTL=46
Reply from 74.125.132.94: bytes=32 time=173ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=48
Reply from 74.125.132.94: bytes=32 time=151ms TTL=48
Reply from 74.125.132.94: bytes=32 time=219ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=30ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=46
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=33ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=28ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=46
Reply from 74.125.132.94: bytes=32 time=182ms TTL=46
Reply from 74.125.132.94: bytes=32 time=25ms TTL=48
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Request timed out.
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=20ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=29ms TTL=48
Reply from 74.125.132.94: bytes=32 time=186ms TTL=48
Reply from 74.125.132.94: bytes=32 time=61ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=21ms TTL=46
Reply from 74.125.132.94: bytes=32 time=109ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=21ms TTL=46
Reply from 74.125.132.94: bytes=32 time=1178ms TTL=4
Reply from 74.125.132.94: bytes=32 time=2108ms TTL=4
Reply from 74.125.132.94: bytes=32 time=1597ms TTL=4
Reply from 74.125.132.94: bytes=32 time=779ms TTL=48
Reply from 74.125.132.94: bytes=32 time=663ms TTL=48
Reply from 74.125.132.94: bytes=32 time=220ms TTL=46
Reply from 74.125.132.94: bytes=32 time=136ms TTL=48
Reply from 74.125.132.94: bytes=32 time=911ms TTL=46
Reply from 74.125.132.94: bytes=32 time=91ms TTL=48
Reply from 74.125.132.94: bytes=32 time=38ms TTL=48
Reply from 74.125.132.94: bytes=32 time=225ms TTL=48
Reply from 74.125.132.94: bytes=32 time=443ms TTL=48
Reply from 74.125.132.94: bytes=32 time=201ms TTL=48
Reply from 74.125.132.94: bytes=32 time=471ms TTL=46
Reply from 74.125.132.94: bytes=32 time=144ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48
Reply from 74.125.132.94: bytes=32 time=507ms TTL=48
Reply from 74.125.132.94: bytes=32 time=303ms TTL=48
Reply from 74.125.132.94: bytes=32 time=236ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=1638ms TTL=4
Reply from 74.125.132.94: bytes=32 time=2197ms TTL=4
Reply from 74.125.132.94: bytes=32 time=2184ms TTL=4
Reply from 74.125.132.94: bytes=32 time=1350ms TTL=4
Reply from 74.125.132.94: bytes=32 time=367ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48
Reply from 74.125.132.94: bytes=32 time=28ms TTL=46
Reply from 74.125.132.94: bytes=32 time=32ms TTL=46
Reply from 74.125.132.94: bytes=32 time=71ms TTL=48
Reply from 74.125.132.94: bytes=32 time=1570ms TTL=4
Reply from 74.125.132.94: bytes=32 time=713ms TTL=46
Reply from 74.125.132.94: bytes=32 time=268ms TTL=46
Reply from 74.125.132.94: bytes=32 time=712ms TTL=48
Reply from 74.125.132.94: bytes=32 time=32ms TTL=48
Reply from 74.125.132.94: bytes=32 time=195ms TTL=48
Reply from 74.125.132.94: bytes=32 time=386ms TTL=46
Reply from 74.125.132.94: bytes=32 time=124ms TTL=46
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=46
Reply from 74.125.132.94: bytes=32 time=100ms TTL=48
Reply from 74.125.132.94: bytes=32 time=123ms TTL=48
Reply from 74.125.132.94: bytes=32 time=476ms TTL=46
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=237ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=261ms TTL=48
Reply from 74.125.132.94: bytes=32 time=505ms TTL=46
Reply from 74.125.132.94: bytes=32 time=1186ms TTL=4
Reply from 74.125.132.94: bytes=32 time=502ms TTL=48
Reply from 74.125.132.94: bytes=32 time=1120ms TTL=4
Reply from 74.125.132.94: bytes=32 time=1214ms TTL=4
Reply from 74.125.132.94: bytes=32 time=1386ms TTL=4
Reply from 74.125.132.94: bytes=32 time=120ms TTL=46
Reply from 74.125.132.94: bytes=32 time=722ms TTL=48
Reply from 74.125.132.94: bytes=32 time=806ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=46
Reply from 74.125.132.94: bytes=32 time=708ms TTL=48
Reply from 74.125.132.94: bytes=32 time=166ms TTL=46
Reply from 74.125.132.94: bytes=32 time=253ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=21ms TTL=48
Reply from 74.125.132.94: bytes=32 time=143ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=22ms TTL=46
Reply from 74.125.132.94: bytes=32 time=21ms TTL=46
Reply from 74.125.132.94: bytes=32 time=589ms TTL=46
Reply from 74.125.132.94: bytes=32 time=32ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=105ms TTL=48
Reply from 74.125.132.94: bytes=32 time=85ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=497ms TTL=48
Reply from 74.125.132.94: bytes=32 time=153ms TTL=46
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=72ms TTL=48
Reply from 74.125.132.94: bytes=32 time=243ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48
Reply from 74.125.132.94: bytes=32 time=186ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=46
Reply from 74.125.132.94: bytes=32 time=28ms TTL=48
Reply from 74.125.132.94: bytes=32 time=254ms TTL=46
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=199ms TTL=48
Reply from 74.125.132.94: bytes=32 time=122ms TTL=48
Reply from 74.125.132.94: bytes=32 time=144ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=30ms TTL=48
Reply from 74.125.132.94: bytes=32 time=31ms TTL=48
Reply from 74.125.132.94: bytes=32 time=235ms TTL=48
Reply from 74.125.132.94: bytes=32 time=76ms TTL=46
Reply from 74.125.132.94: bytes=32 time=22ms TTL=46
Request timed out.
Reply from 74.125.132.94: bytes=32 time=90ms TTL=46
Reply from 74.125.132.94: bytes=32 time=42ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=260ms TTL=48
Reply from 74.125.132.94: bytes=32 time=80ms TTL=48
Reply from 74.125.132.94: bytes=32 time=307ms TTL=48
Reply from 74.125.132.94: bytes=32 time=99ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=32ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=31ms TTL=48
Reply from 74.125.132.94: bytes=32 time=150ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=48
Reply from 74.125.132.94: bytes=32 time=83ms TTL=46
Reply from 74.125.132.94: bytes=32 time=38ms TTL=48
Reply from 74.125.132.94: bytes=32 time=153ms TTL=46
Reply from 74.125.132.94: bytes=32 time=151ms TTL=48
Reply from 74.125.132.94: bytes=32 time=851ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=26ms TTL=48
Reply from 74.125.132.94: bytes=32 time=35ms TTL=46
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=32ms TTL=48
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=30ms TTL=46
Reply from 74.125.132.94: bytes=32 time=69ms TTL=48
Reply from 74.125.132.94: bytes=32 time=39ms TTL=48
Reply from 74.125.132.94: bytes=32 time=22ms TTL=48
Reply from 74.125.132.94: bytes=32 time=24ms TTL=48
Reply from 74.125.132.94: bytes=32 time=23ms TTL=46
Reply from 74.125.132.94: bytes=32 time=25ms TTL=46
Reply from 74.125.132.94: bytes=32 time=153ms TTL=46
Reply from 74.125.132.94: bytes=32 time=285ms TTL=46
Reply from 74.125.132.94: bytes=32 time=27ms TTL=46
Reply from 74.125.132.94: bytes=32 time=120ms TTL=48
Reply from 74.125.132.94: bytes=32 time=27ms TTL=48


C:\Users\Admin>ping google.co.uk -t#

Pinging google.co.uk [173.194.67.94] with 32 bytes of d
Reply from 173.194.67.94: bytes=32 time=23ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=48
Reply from 173.194.67.94: bytes=32 time=22ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=48
Reply from 173.194.67.94: bytes=32 time=23ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=48
Reply from 173.194.67.94: bytes=32 time=21ms TTL=46
Reply from 173.194.67.94: bytes=32 time=20ms TTL=48
Reply from 173.194.67.94: bytes=32 time=25ms TTL=48
Reply from 173.194.67.94: bytes=32 time=34ms TTL=46
Reply from 173.194.67.94: bytes=32 time=22ms TTL=48
Reply from 173.194.67.94: bytes=32 time=23ms TTL=48
Reply from 173.194.67.94: bytes=32 time=31ms TTL=46
Reply from 173.194.67.94: bytes=32 time=25ms TTL=48
Reply from 173.194.67.94: bytes=32 time=773ms TTL=48
Reply from 173.194.67.94: bytes=32 time=116ms TTL=46
Reply from 173.194.67.94: bytes=32 time=32ms TTL=46
Reply from 173.194.67.94: bytes=32 time=118ms TTL=48
Reply from 173.194.67.94: bytes=32 time=72ms TTL=48
Reply from 173.194.67.94: bytes=32 time=23ms TTL=48
Reply from 173.194.67.94: bytes=32 time=276ms TTL=48
Reply from 173.194.67.94: bytes=32 time=379ms TTL=46
Reply from 173.194.67.94: bytes=32 time=22ms TTL=48
Reply from 173.194.67.94: bytes=32 time=143ms TTL=46
Reply from 173.194.67.94: bytes=32 time=25ms TTL=48
Reply from 173.194.67.94: bytes=32 time=25ms TTL=46
Reply from 173.194.67.94: bytes=32 time=22ms TTL=46
Reply from 173.194.67.94: bytes=32 time=131ms TTL=46
Reply from 173.194.67.94: bytes=32 time=357ms TTL=46
Reply from 173.194.67.94: bytes=32 time=379ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=48
Reply from 173.194.67.94: bytes=32 time=34ms TTL=46
Reply from 173.194.67.94: bytes=32 time=30ms TTL=48
Reply from 173.194.67.94: bytes=32 time=24ms TTL=46
Reply from 173.194.67.94: bytes=32 time=392ms TTL=48
Reply from 173.194.67.94: bytes=32 time=29ms TTL=48
Reply from 173.194.67.94: bytes=32 time=25ms TTL=48
Reply from 173.194.67.94: bytes=32 time=22ms TTL=46
Reply from 173.194.67.94: bytes=32 time=22ms TTL=48
Reply from 173.194.67.94: bytes=32 time=96ms TTL=46
Reply from 173.194.67.94: bytes=32 time=27ms TTL=48
Reply from 173.194.67.94: bytes=32 time=22ms TTL=48
Reply from 173.194.67.94: bytes=32 time=21ms TTL=46
 
Lol, you pinged google.co.uk both times ya dafty.
One ping should have been to google.co.uk the other should have been 173.194.67.94.
This is purely to try and see if there are any DNS issues.
If for example the ping to google.co.uk kept timing out, but the ping to 173.194.67.94 kept responding then it would point towards a DNS translation issue with (probably) your router, as i'm guessing it's what handles DNS requests initially.

However the ping timings are a little erratic on occasion, but probably expected for a wifi connection.

You can also paste 173.194.67.94 straight into a browser address bar and it should load up google homepage. Try that next time you lose the internet, see what happens.
 
I fixed this issue so i thought i'd give an update on what was causing the problem so that people with similar issue can fix it.

The issue was nothing to do with the pc or my connection, although my house seems to block the signal sometimes. The problem was my wireless headset causing interferance, and also my mobile phones wireless does this. If your contantly recieving a bad signal or its dropping out consistantly, look around for anything thats wireless and disconnect it and see if this is the culprit, i litterally never thought that my headset would interfere with my wireless internet. As an additional note this is a major issue for xbox 360 as the wireless device in the xbox is S>>t and any interferance messes with it.

Admin can lock this thread now, issue is solved.
 
So just to confirm.
You are not able to access any sites yet can plat games ok with no issues?
This does not sounds like packet loss as most games will go nuts for packet loss.

Ok with the cable use the connection until it drops,
At this point do not disconnect.

Run ipconfig,
Ping the router,
Ping a website,
Try to log in to the router,
Hover your mouse over the network icon and report back what is says
"Connected to blah" "Access limited" or what ever it say.

Also can you confirm what firewall/s you are using & what windows it is.
 
steven_belfast said:
So just to confirm.
You are not able to access any sites yet can plat games ok with no issues?
This does not sounds like packet loss as most games will go nuts for packet loss.

Ok with the cable use the connection until it drops,
At this point do not disconnect.

Run ipconfig,
Ping the router,
Ping a website,
Try to log in to the router,
Hover your mouse over the network icon and report back what is says
"Connected to blah" "Access limited" or what ever it say.

Also can you confirm what firewall/s you are using & what windows it is.
Click to expand...

Please read the post above yours.

This issue has been fixed for almost 3 months now, and it was most definatly the other wireless devices as i tested it without and with over and over to make sure and every single time i have the headset on, the internet would cut out but the game would continue to run, however i would experiance a drop in quality on the gameplay.

It is still apparent as i need to turn off my wireless on my phone otherwise i am constantly being disconnected from game and the wireless signal cuts out, this happens all the time but if i switch my wireless off on my phone everything clears up and i get no more issues.

I don't run any firewalls, i tried every single way that was offered to me to get my internet working, non of them worked. I had simply overlooked my wireless headset
 
You must log in or register to reply here.
Back
Top Bottom