I honestly don't see how you can apply those assumptions to this thread. Just because "you don't think" that changing to wired might make a difference, why don't you just let the troubleshooting progress and then you could chime in with "I could have told you that"; however, if you read this thread thoroughly, you would have been able to understand that the OP did not have a problem running Windows 7 but now does have a problem running Windows 8 (both wireless). Now, there is a distinct possibility that their router may need a firmware update and/or there is something not right with the drivers for her Win 7/8 compatible hardware AND I'm trying to get there by taking one troubleshooting step at a time. However, because of you advanced knowledge of the network in question, I am inviting you to take over because I am bowing out due to the confusion your posts have introduced into this troubleshooting process. Please understand that I am not trying to be mean but the problem was made very clear from the onset (works on Win 7 but not on Win 8) and all of your assumptions are basically ignoring that possibility.
Ok, I let you troubleshoot with her.
PS:
I had this under Windows-7 as well. Should have mentioned it.
PPS:
Windows-8 has a better driver support straight out of the box then Windows-7.
PPPS:
She still didn't mention that her Internet is playing up in general, so you are guessing as well. Her speed-test looks good to me, but it doesn't tell us if there are fluctuating pings to Facebook / Zynga or even to the DNS-Servers etc. We also don't know something about the Signal-Strenght between PC and Router. To run some ping and tracery test and switching the wlan channels at the PCs and Router could help as well.
PPPPS:
Only as a side-note:
Yesterday's ping to
www.facebook.com = 31.13.70.7
Today's ping to
www.facebook.com = 173.252.110.27
If you do a whois-look-up, you will see that this IP's belong to Facebook.
Here are the IP-Ranges of Zynga:
Click
Here are some Ping-Test's and Tracert-Test's from my System, which will be completely different on the Thread-Starter's machine:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping www.facebook.com
Pinging www.facebook.com [173.252.110.27] with 32 bytes of data:
Reply from 173.252.110.27: bytes=32 time=318ms TTL=237
Reply from 173.252.110.27: bytes=32 time=318ms TTL=237
Reply from 173.252.110.27: bytes=32 time=316ms TTL=237
Reply from 173.252.110.27: bytes=32 time=318ms TTL=237
Ping statistics for 173.252.110.27:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 316ms, Maximum = 318ms, Average = 317ms
C:\Windows\system32>ping www.zynga.com
Pinging zynga.com [184.75.160.52] with 32 bytes of data:
Reply from 184.75.160.52: bytes=32 time=271ms TTL=241
Reply from 184.75.160.52: bytes=32 time=271ms TTL=241
Reply from 184.75.160.52: bytes=32 time=273ms TTL=241
Reply from 184.75.160.52: bytes=32 time=273ms TTL=241
Ping statistics for 184.75.160.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 271ms, Maximum = 273ms, Average = 272ms
C:\Windows\system32>tracert www.facebook.com
Tracing route to www.facebook.com [173.252.110.27]
over a maximum of 30 hops:
1 5 ms 5 ms 4 ms RTA1046VW.home [192.168.1.1]
2 28 ms 27 ms 27 ms 10.20.21.72
3 30 ms 29 ms 27 ms bri-sot-wic-csw2-tengi-4-4.tpgi.com.au [202.7.17
3.249]
4 28 ms 29 ms 29 ms bri-sot-wic-crt2-gi-1-0-0.tpgi.com.au [203.29.13
5.5]
5 46 ms 45 ms 57 ms syd-sot-ken-crt4-TG-10-2.tpgi.com.au [202.7.173.
225]
6 46 ms 45 ms 45 ms syd-sot-ken-crt2-ge-5-0-0.tpgi.com.au [203.29.13
5.213]
7 * 249 ms * Vlan516.icore1.SQN-SanJose.as6453.net [66.198.97
.33]
8 251 ms 249 ms 249 ms Vlan559.icore1.SQN-SanJose.as6453.net [209.58.11
6.110]
9 300 ms 299 ms 299 ms vlan80.csw3.SanJose1.Level3.net [4.69.152.190]
10 300 ms 299 ms 299 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9]
11 304 ms * 310 ms ae-5-5.ebr1.SanJose5.Level3.net [4.69.148.137]
12 300 ms 299 ms 299 ms ae-1-100.ebr2.SanJose5.Level3.net [4.69.148.110]
13 300 ms 299 ms 299 ms ae-6-6.ebr2.LosAngeles1.Level3.net [4.69.148.201
]
14 300 ms 299 ms 299 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
15 300 ms 299 ms 299 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 302 ms 299 ms 299 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]
17 300 ms 299 ms 299 ms ae-2-52.edge5.Atlanta2.Level3.net [4.69.150.78]
18 300 ms 299 ms 299 ms FACEBOOK-IN.edge5.Atlanta2.Level3.net [4.28.26.4
6]
19 300 ms 329 ms 299 ms ae2.bb02.atl1.tfbnw.net [204.15.23.210]
20 316 ms 305 ms 337 ms ae11.bb03.frc1.tfbnw.net [31.13.27.120]
21 314 ms 313 ms 313 ms ae3.dr04.frc1.tfbnw.net [31.13.27.61]
22 * * * Request timed out.
23 316 ms 317 ms 313 ms www.facebook.com [173.252.110.27]
Trace complete.
C:\Windows\system32>tracert 184.75.160.52
Tracing route to 184.75.160.52 over a maximum of 30 hops
1 4 ms 2 ms 3 ms RTA1046VW.home [192.168.1.1]
2 28 ms 27 ms 25 ms 10.20.21.72
3 28 ms 27 ms 27 ms bri-sot-wic-csw1-tengi-4-4.tpgi.com.au [202.7.17
3.245]
4 26 ms 25 ms 25 ms bri-sot-wic-crt1-gi-2-1-0.tpgi.com.au [202.7.171
.217]
5 28 ms 27 ms 27 ms bri-nxg-alf-crt1-POS-7-2.tpgi.com.au [202.7.171.
253]
6 86 ms 43 ms 45 ms syd-sot-ken-crt3-te-13-1.tgpi.com.au [202.7.171.
125]
7 44 ms 43 ms 43 ms syd-sot-ken-crt1-ge-0-0-0.tpgi.com.au [203.29.13
5.145]
8 224 ms 221 ms 221 ms ge5-0-5d0.cir1.seattle7-wa.us.xo.net [216.156.10
0.37]
9 224 ms 225 ms 277 ms 4.59.232.53
10 272 ms 291 ms 273 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]
11 275 ms 275 ms 273 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
12 274 ms 273 ms 275 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
13 271 ms 271 ms 271 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
14 272 ms 273 ms 271 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.14
5]
15 272 ms 271 ms 271 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221
]
16 273 ms 273 ms 273 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
17 273 ms 271 ms 275 ms ae-2-70.edge3.Washington4.Level3.net [4.69.149.8
2]
18 271 ms 273 ms 271 ms ZYNGA-INC.edge3.Washington4.Level3.net [4.53.116
.94]
19 * * * Request timed out.
20 * * * Request timed out.
21 274 ms 273 ms 271 ms 184.75.160.52
Trace complete.
C:\Windows\system32>
If you use for an example "ping
www.facebook.com -t" or "ping
Zynga | Play free online games with friends -t" or "ping 184.75.160.52 -t" or whatever IP you are connected to, then you are able to see if there are large up's and down's or even time-out's.
If you get somewhere on your Tracert-Route strange Ping-Times or time-out's, then just ping this hop via "ping IP-Address -t" for awhile and see if the Ping-Times stay similar or if they go up and down all the time in large numbers or even time-out.
You could try out another IP-Address from Facebook / Zynga out of their IP-Range, to see if it improve things. Therefore just type the IP-Address into your Browser-Field, where you would normally put the "www.blabla.com".
You could do a Ping-Test via
Pingtest.net as well, to see how your connection in general performs.
Some User's have / had Problems with their I-Net under Windows-8, which was mainly driver-related as @norepli already mentioned, but in most cases there was a problem with the I-Net-Speed in general, which seems not to apply to your problem, as ~7 MBit/s are more then enough speed to play Facebook / Zynga-Games, if there is not somewhere a QoS-Setting applied to prefer your partner's computer, when you are both connected at the same time.