Netflix instant has become unwatchable. [Archive] - Glock Talk

PDA

View Full Version : Netflix instant has become unwatchable.


Blaster
06-24-2011, 19:04
Instant Netflix constantly pauses and is extremely annoying. I don't know if it is Netflix or my ISP.

Cable modem

Downstream Value
Frequency 855000000 Hz
Signal To Noise Ratio 28.8 dB
Power Level 0.9 dBmV

Upstream Value
Channel ID 1
Frequency 27000000 Hz
Power 36.7 dBmV

Pierre!
06-24-2011, 19:24
What's your bandwidth look like? Cable yes, but how much?

What else is using the internet???

Blaster
06-24-2011, 19:26
Been running speed tests and getting results where my upload speed is always greater than my download speed.

Download Speed: 5478 kbps (684.8 KB/sec transfer rate)
Upload Speed: 8308 kbps (1038.5 KB/sec transfer rate)

Looks wacky to me. Uploads always were slower than downloads.

Dalton Wayne
06-24-2011, 19:28
My netflix works fine watching as we type

Blaster
06-24-2011, 19:32
My netflix works fine watching as we type

My wife and kids are watching a Marx Brothers movie now and Netflix Instant is working fine now. Even with me running many speed tests.


Last Result:
Download Speed: 5055 kbps (631.9 KB/sec transfer rate)
Upload Speed: 8544 kbps (1068 KB/sec transfer rate)
Fri Jun 24 2011 21:35:17 GMT-0400 (Eastern Daylight Time)
http://speedtest.frontier.com/

Pierre!
06-24-2011, 19:40
My wife and kids are watching a Marx Brothers movie now and Netflix Instant is working fine now. Even with me running many speed tests.


Last Result:
Download Speed: 5055 kbps (631.9 KB/sec transfer rate)
Upload Speed: 8544 kbps (1068 KB/sec transfer rate)
Fri Jun 24 2011 21:35:17 GMT-0400 (Eastern Daylight Time)
http://speedtest.frontier.com/

Hmmm... Kinda backwards eh? How old is the modem? If it's rented you should swap it out once a year or so... if it's purchased, like my Cox modem is, then it's not so fun...

Possibly old modem, or get a Cable Guy out there...

Just be sure you 'Open Carry' if he comes to visit/work... :cool:

Blaster
06-24-2011, 19:47
Cox Communications here too.

Motorola Surfboard Modem. Owned I believe. Cox did swap it out once a while back due to some sort of upgrade.

barstoolguru
06-24-2011, 20:15
i allways run a quick virus scan before watching a movie to get rid of the tracking cookies makes the movie run smother

Blaster
06-24-2011, 20:36
i allways run a quick virus scan before watching a movie to get rid of the tracking cookies makes the movie run smother

Not applicable here. Watching via a Sony Blue-Ray player.

JK-linux
06-24-2011, 20:39
Comcrap cable internet here in MN. I've been streaming "Survivors" (BBC show) from Netflix for the last hour to my AppleTV2 without issue.

Straight_Shooter
06-24-2011, 22:43
It is strange that your upstream speeds are higher than your downstream speed, but that speed should be sufficient. I think that you're problem is more likely latency.
Ping www.google.com using the -t modifier, this will make the ping continuous. Look at your ping times, they should be relatively low (less than say 50ms) and there should be no drops.
If there are drops or high times then you should do a tracert to www.google.com, then ping each of the ip addresses that are listed to determine where the latency is in the network. The first IP will be your router, if the latency is there then you have network problems inside your network. If it is the next ip it is likely a problem with your modem or line coming into your house. If it is further down that list then it is likely a problem somewhere in your ISPs network.

Blaster
06-24-2011, 23:26
Pinged my router over the wireless. Doesn't look good!


Pinging 192.168.100.1 with 32 bytes of data:

Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=208ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=253ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=31ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1042ms TTL=63
Reply from 192.168.100.1: bytes=32 time=932ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3351ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2442ms TTL=63
Reply from 192.168.100.1: bytes=32 time=441ms TTL=63
Reply from 192.168.100.1: bytes=32 time=371ms TTL=63
Reply from 192.168.100.1: bytes=32 time=528ms TTL=63
Request timed out.
Reply from 192.168.100.1: bytes=32 time=1908ms TTL=63
Reply from 192.168.100.1: bytes=32 time=516ms TTL=63
Reply from 192.168.100.1: bytes=32 time=244ms TTL=63
Reply from 192.168.100.1: bytes=32 time=984ms TTL=63
Reply from 192.168.100.1: bytes=32 time=247ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1274ms TTL=63
Reply from 192.168.100.1: bytes=32 time=397ms TTL=63
Reply from 192.168.100.1: bytes=32 time=625ms TTL=63
Reply from 192.168.100.1: bytes=32 time=662ms TTL=63
Reply from 192.168.100.1: bytes=32 time=611ms TTL=63
Reply from 192.168.100.1: bytes=32 time=587ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1055ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2071ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1940ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1369ms TTL=63
Reply from 192.168.100.1: bytes=32 time=170ms TTL=63
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3232ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3068ms TTL=63
Reply from 192.168.100.1: bytes=32 time=684ms TTL=63
Reply from 192.168.100.1: bytes=32 time=157ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=917ms TTL=63
Reply from 192.168.100.1: bytes=32 time=758ms TTL=63
Reply from 192.168.100.1: bytes=32 time=329ms TTL=63
Reply from 192.168.100.1: bytes=32 time=316ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1156ms TTL=63
Reply from 192.168.100.1: bytes=32 time=354ms TTL=63
Reply from 192.168.100.1: bytes=32 time=504ms TTL=63
Reply from 192.168.100.1: bytes=32 time=627ms TTL=63
Reply from 192.168.100.1: bytes=32 time=459ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1070ms TTL=63
Reply from 192.168.100.1: bytes=32 time=630ms TTL=63
Reply from 192.168.100.1: bytes=32 time=716ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1019ms TTL=63
Reply from 192.168.100.1: bytes=32 time=806ms TTL=63
Reply from 192.168.100.1: bytes=32 time=55ms TTL=63
Reply from 192.168.100.1: bytes=32 time=146ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1677ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3252ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=118ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=30ms TTL=63
Reply from 192.168.100.1: bytes=32 time=231ms TTL=63
Request timed out.
Reply from 192.168.100.1: bytes=32 time=1732ms TTL=63
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3222ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2532ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1313ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1507ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2042ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1732ms TTL=63
Reply from 192.168.100.1: bytes=32 time=986ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1360ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1587ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1006ms TTL=63
Reply from 192.168.100.1: bytes=32 time=636ms TTL=63
Reply from 192.168.100.1: bytes=32 time=911ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1950ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1908ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1427ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1526ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1119ms TTL=63
Reply from 192.168.100.1: bytes=32 time=289ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1272ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2004ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=828ms TTL=63
Reply from 192.168.100.1: bytes=32 time=196ms TTL=63
Reply from 192.168.100.1: bytes=32 time=367ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1248ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2144ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1996ms TTL=63
Request timed out.
Reply from 192.168.100.1: bytes=32 time=4333ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1083ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1606ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1727ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1434ms TTL=63
Reply from 192.168.100.1: bytes=32 time=585ms TTL=63
Reply from 192.168.100.1: bytes=32 time=550ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63

gemeinschaft
06-25-2011, 00:50
Have you tried unplugging your router, waiting about 30 seconds and plugging it back in?

Then run the same Ping test and see what happens.

If you continue to get high latency, you may have a computer in the house that is broadcasting a DoS (Denial of Service) attack on your local network.

If there is more than one device, cycle them off one by one until you see the network go stable with <2ms latency.

How many connected devices are on your LAN right now?

Blaster
06-25-2011, 08:37
Those poor numbers (ping test) were from my laptop when I took it to the far end of my house. Far end meaning farthest away from my router. This morning I reran the test near the router and the numbers are 2-3 ms. I think the Belkin N+ wireless router has lost signal strength. However my Blue-Ray player is hard wired to the router.

I have tried multiple times to power off both the router and the cable modem with no significant results. Regarding the number of devices, there are three laptops, one hard wired PC, my Blackberry and the Blue Ray player connected to the router. Last night when I was running the ping test only my laptop and Blackberry were powered on.

eracer
06-25-2011, 08:49
In WinXP, go to <Control Panel><Administrative Tools><Services>

Stop and disable 'Wireless Zero Configuration>

Might help with your disconnect/latency issues. It fixed mine.

Blaster
06-25-2011, 09:22
In WinXP, go to <Control Panel><Administrative Tools><Services>

Stop and disable 'Wireless Zero Configuration>

Might help with your disconnect/latency issues. It fixed mine.

Gave it a try. However i think the problem is at the router. My daughter just told me that she has been having trouble connecting with her laptop from her room and never had trouble before.

Heck look at these numbers from a spot near the router.

Request timed out.
Reply from 192.168.100.1: bytes=32 time=1560ms TTL=63
Reply from 192.168.100.1: bytes=32 time=530ms TTL=63
Reply from 192.168.100.1: bytes=32 time=261ms TTL=63
Reply from 192.168.100.1: bytes=32 time=881ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3157ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1110ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3188ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2968ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4299ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=2346ms TTL=63
Reply from 192.168.100.1: bytes=32 time=428ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2820ms TTL=63
Reply from 192.168.100.1: bytes=32 time=933ms TTL=63
Reply from 192.168.100.1: bytes=32 time=760ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3167ms TTL=63
Reply from 192.168.100.1: bytes=32 time=614ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1249ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2354ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2148ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2046ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2055ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2755ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2250ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2667ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1293ms TTL=63
Reply from 192.168.100.1: bytes=32 time=920ms TTL=63
Reply from 192.168.100.1: bytes=32 time=131ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=16ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=368ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3670ms TTL=63
Request timed out.

Ping statistics for 192.168.100.1:
Packets: Sent = 125, Received = 56, Lost = 69 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4299ms, Average = 947ms
Control-C

Blaster
06-25-2011, 09:27
In WinXP, go to <Control Panel><Administrative Tools><Services>

Stop and disable 'Wireless Zero Configuration>

Might help with your disconnect/latency issues. It fixed mine.

Gave it a try. However i think the problem is at the router. My daughter just told me that she has been having trouble connecting with her laptop from her room and never had trouble before.

Heck look at these numbers from a spot near the router.

Request timed out.
Reply from 192.168.100.1: bytes=32 time=1560ms TTL=63
Reply from 192.168.100.1: bytes=32 time=530ms TTL=63
Reply from 192.168.100.1: bytes=32 time=261ms TTL=63
Reply from 192.168.100.1: bytes=32 time=881ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3157ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1110ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3188ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2968ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4299ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=2346ms TTL=63
Reply from 192.168.100.1: bytes=32 time=428ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2820ms TTL=63
Reply from 192.168.100.1: bytes=32 time=933ms TTL=63
Reply from 192.168.100.1: bytes=32 time=760ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3167ms TTL=63
Reply from 192.168.100.1: bytes=32 time=614ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1249ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2354ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2148ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2046ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2055ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2755ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2250ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2667ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1293ms TTL=63
Reply from 192.168.100.1: bytes=32 time=920ms TTL=63
Reply from 192.168.100.1: bytes=32 time=131ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=16ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=368ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
Request timed out.
Request timed out.
Reply from 192.168.100.1: bytes=32 time=3670ms TTL=63
Request timed out.

Ping statistics for 192.168.100.1:
Packets: Sent = 125, Received = 56, Lost = 69 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4299ms, Average = 947ms
Control-C

Blaster
06-25-2011, 09:29
Sorry about the duplicate. Now I am having so much trouble connecting I can't tell what is happening.

srhoades
06-25-2011, 09:46
i allways run a quick virus scan before watching a movie to get rid of the tracking cookies makes the movie run smother

That makes absolutely no sense.

gemeinschaft
06-25-2011, 10:03
Ok, since you have multiple computers, this is what I would suggest:

Hardwire 2 PCs to your router, turn off wireless on both of the computers that you are using for this test.

If one of the computers is named "BluePC" then you would run a ping test from another computer to "Blue PC"

I'd like to see what kind of metrics you are getting on the LAN without factoring in wifi at this point.

IndyGunFreak
06-25-2011, 11:30
That makes absolutely no sense.

Agree.. not really sure where he's coming from w/ that.

IGF

ptmccain
06-25-2011, 11:39
I dumped Netflix and use Amazon's streaming video, via my prime membership. Amazon is still building it out, but...they are definitely going to give Netflix some much needed competition.

Blaster
06-25-2011, 12:57
Ok, since you have multiple computers, this is what I would suggest:

Hardwire 2 PCs to your router, turn off wireless on both of the computers that you are using for this test.

If one of the computers is named "BluePC" then you would run a ping test from another computer to "Blue PC"

I'd like to see what kind of metrics you are getting on the LAN without factoring in wifi at this point.

I will try later. Running too many errands and projects today.

One thing I have been concerned about in this connectivity issue specifically with my laptop is the anti-virus software (Sophos) and any other corporate enterprise junk that is on there that could be causing a problem. The laptop is running Odyssey Access Client Manager to control its Dell 1501 Wireless-N WLAN Half-Mini card. This was a corporate upgrade that was pushed to us months ago. Also running one of those IT Client Managers for software delivery. Still running XP on a new laptop because IT hasn't validated all our applications on Windows 7.