In reply to a post by Bongohonky:

from 1400 1500

Does that mean from 1400 to 1500? If so, 1400 was far too low.

Did you change MTU in router?

Yes, 1400 TO 1500. And, yes, I changed the router settings via the 192.168.0.1 default address set up thingy.
Someone, on another site, recommended "flushing the DNS cache" via ipconfig. The only problem with this is; the instructions begin: "Click "start" and then click "RUN".....". I'm not sure what version of Vista that person is running but, I'm damned if I can find a "RUN" in the start menu of my version. Tell me if I'm being thick - I can take it - but am I missing something obvious here? It is becoming increasingly frustrating - I'm going out to find a dog to kick - in the meantime, thanks for your time chaps, it is greatly appreciated.

Run should be there under Vista. However, look instead for 'Command Prompt' within your Programs. I doubt "flushing the DNS cache" will assist as you do not have a DNS issue.

Indeed, I don't think this is a DNS issue, and /flushcache isn't going to do much here.

The run box isn't there by default, but it can be typed into the start menu search in it's absense anyway.

Or, good old Windows Key + R.

Hi, I would flush the DNS because it may have been corrupted.

DNS Cache Flush, Clear, or Reset in Vista and Windows 7

1. Click the Microsoft Vista Start logo in the bottom left corner of the screen
2. Click All Programs
3. Click Accessories
4. RIGHT-click on Command Prompt
5. Select Run As Administrator
6. In the command window type the following and then hit enter: ipconfig /flushdns
7. You will see the following confirmation:
Windows IP Configuration Successfully flushed the DNS Resolver Cache.

Any time you restart the computer the DNS resolver cache is cleared so this is clearly not the problem...

The command is there really for system administrators and people who know when a DNS record has just changed and don't want to wait the length of the TTL.

Edited by Pipexer (Sun 06-May-12 23:01:28)

My thoughts exactly

OP chasing DNS is a red herring

Ok, so. It's not the DNS (which I thought it might be because I had seen posts in another forum where people were having much the same trouble and that was the advise given); It's not the MTU and we're ruling out the NAT..... So, what is it? Bearing in mind that it only happens on this Orange Wifi and not just on this laptop.... I tried my sons as well.
I am using a 2ghz Core2 Duo Dell Vostro 1700 with a Nvidia GeForce 8400 graphics card running Windows Vista Business. Second Life has always and still does (anywhere else) work perfectly - actually, to a high graphical standard. I can log into Second Life fine but it seems to be when the graphics has resolved themselves (rezzed) properly that it crashes. It is an official crash; i.e. I get the message saying I have been logged off and given the option to read IMs or quit. I use the Phoenix Viewer but have tried Firestorm and the official Linden Labs Wiewer.
I don't know how much of this would make sense to anyone who has never been inworld and I looked to post something on the SL forums but, surprisingly (or not), they are very user unfriendly and hard to navigate.
So, any ideas?

btw, apparently the aged relative blames me for having Orange. I installed Freeserve onto her first comp and she has stuck with it through Wanadoo etc. So, it's kinda come back to bite my bum.

How have you ruled out NAT problems, there are two types

1. Port forwarding
2. The NAT table filling up and crashing router due to large number of connections by a software application

Have you also ruled out WiFi issues, by connecting using an Ethernet cable.

You brought your PCs from your old place. Did you manage to bring your router too? Try connecting that, or another router, if you think it is the Wi-Fi.

Are all the wireless connected at time of fault to the same standard (N?)? Router slows to slowest. Better to run wired.

Are those stats given earlier at the time of the fault?