It went straight in at work, with just the passcode. It connects to the network at home first time with just the passcode, but the difference is access to the internet is not working at home but is at work. Going to try today updating it at work today.

Is your router set to automatically assign an IP address and is not set to restrict access to certain machines? You should be abel to check this by logging in to your router.

It went straight in at work, with just the passcode. It connects to the network at home first time with just the passcode, but the difference is access to the internet is not working at home but is at work. Going to try today updating it at work today.

Did you try a different security protocol, note which one work uses and try that at home.

Tried all different ones.... Currently installing about 400+MB of windows updates from work now, and its already done loads of Vaio updates. Hoping that sorts it when I try it again at home tonight.

Think it's either going to be a wireless channel issue, or an issue the VAIO has with your type of wireless encryption on the home router.

But as you say; hopefully the updates might sort it out. Make sure you're running the latest driver for the wireless from the Sony website too.

Yeah, this morning it spent 4 hours downloading the Vaio stuff, and now its doing windows (installing update 44 of 122 now )

Well, its still not connecting to the internet. I've even managed to look at the skybox status (192.168.0.1) and it shows the machine as connected but "unknown". Tried renaming the computer name in case of a duplicated ID, but no avail. Think I might just take up a colleagues offer of putting Windows 7 on this thing....

Have you checked Windows firewall as daft as it sounds?

Just try disabling it for a few mins with possibly a reboot with it off and try again.

Turn off encryption on the home router entirely.

Then try again; that would at least answer whether it's the type of encryption that's causing the issue.

Is your router hidden? If so, unhide connect then rehide.

Check that you can ping the Sky router - 192.168.1.1

My router is 192.168.100.254 (so just imagine that is 192.168.1.1)

C:\Users\matthewa>ping 192.168.100.254

Pinging 192.168.100.254 with 32 bytes of data:

Reply from 192.168.100.254: bytes=32 time<1ms TTL=255

Reply from 192.168.100.254: bytes=32 time<1ms TTL=255

Reply from 192.168.100.254: bytes=32 time<1ms TTL=255

Reply from 192.168.100.254: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.100.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Try a tracert to the router, to should get there in one hop.

C:\Users\matthewa>tracert 192.168.100.254

Tracing route to vigor2820-gw.matthewames.co.uk [192.168.100.254]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vigor2820-gw.matthewames.co.uk [192.168.100.254]

Trace complete.

Check your machine is using the right gateway - it should be the IP of your Sky router

C:\Users\matthewa>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : matthewames.co.uk

Link-local IPv6 Address . . . . . : fe80::6034:e786:6f8f:4f22%11

IPv4 Address. . . . . . . . . . . : 192.168.100.101 <---- the IP address of your local machine

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.100.254 <---- the IP of your router ie. 192.168.1.1

C:\Users\matthewa>

Try tracing a route to 77.92.68.3 - this checks basic internet connectivity

C:\Users\matthewa>ping 77.92.68.3

Pinging 77.92.68.3 with 32 bytes of data:

Reply from 77.92.68.3: bytes=32 time=41ms TTL=58

Reply from 77.92.68.3: bytes=32 time=41ms TTL=58

Reply from 77.92.68.3: bytes=32 time=41ms TTL=58

Reply from 77.92.68.3: bytes=32 time=42ms TTL=58

Ping statistics for 77.92.68.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 41ms, Maximum = 42ms, Average = 41ms

C:\Users\matthewa>

Try a tracing a route to news.bbc.co.uk - this will check DNS will resolve addresses ok, and your routing is ok.

C:\Users\matthewa>tracert news.bbc.co.uk

Tracing route to newswww.bbc.net.uk [212.58.244.57]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vigor2820-gw.matthewames.co.uk [192.168.100.254]

2 39 ms 38 ms 39 ms dr0.hobir.isp.sky.com [89.200.128.38]

3 193 ms 200 ms 203 ms vl190.ar8.hobir.isp.sky.com [89.200.135.176]

4 42 ms 43 ms 43 ms 212.58.238.189

5 42 ms 42 ms 43 ms 212.58.238.153

6 43 ms 42 ms 43 ms 212.58.239.62

7 42 ms 43 ms 42 ms 212.58.251.44

8 43 ms 44 ms 43 ms bbc-vip102.telhc.bbc.co.uk [212.58.244.57]

Trace complete.

C:\Users\matthewa>

If might tempted to issue an "ipconfig /release" command followed by "ipconfig /renew" from a command prompt. This should cause the machine to ask for a new IP address from the router. It will release the address fine, but if connectivity to the router is wrong (ie. wrong passkey, encryption, etc) then it will fail and you will probably get a 169. address - this can be see in the screen after the /renew command has been issued, or by just typing ipconfig. If the machine has a new NICs in it, then you may need to scroll back up to see the entries specific to the Wifi adapter.

Edited 13 August, 201114 yr by mbames

Well, its still not connecting to the internet. I've even managed to look at the skybox status (192.168.0.1) and it shows the machine as connected but "unknown". Tried renaming the computer name in case of a duplicated ID, but no avail. Think I might just take up a colleagues offer of putting Windows 7 on this thing....

so you could log into the router from the new laptop? and it's not connected with a network cable? can you ping something like 8.8.8.8 from the new laptop?

Successful conclusion to this Got an IT techie at work to stick Windows 7 on it. Sometimes having an IT sister company at our accountants is damn good! All working very well indeed now.

Only just spotted this thread, My daughters Sony VIO wouldn't connect to our home router but did connect to her Univerity router either, when she bought it 2 years ago but did connect when updated with Win. 7. so the same proplem it seems.