LinkedIn tanks at log in w/ Windows Vista, fine with prior operating systems

means lack of compatibility here is why..Criticism of upgrade licenses pertaining to Windows Vista Starter through Home Premium was expressed by Ars Technica's Ken Fisher, who noted that the new requirement of having a prior operating system already installed was going to cause irritation for users who reinstall Windows on a regular basis.[154] It has been revealed that an Upgrade copy of Windows Vista can be installed clean without first installing a previous version of Windows. On the first install, Windows will refuse to activate. The user must then reinstall that same copy of Vista. Vista will then activate on the reinstall, thus allowing a user to install an Upgrade of Windows Vista without owning a previous operating system.[155] As with Windows XP, separate rules still apply to OEM versions of Vista installed on new PCs: Microsoft asserts that these versions are not legally transferable (although whether this conflicts with the right of first sale has yet to be clearly decided legally).[156]

Yes, I've heard and even experienced it. The only guarantee solution I can give to you is that you should reinstall your Operating System.

You've put a networking problem in as a WinXP issue without describing the network topology.  Perhaps the WinXP systems are set up to use the original connection, and the new router eventually tires of that behavior and cuts those systems off; you can look in the router's logs around the time the WinXP systems drop off for clues.  Look things up, read the manuals, and you will have a better network for your understanding of its operation.

this has happened to me once or twice the only things I did was to run disk cleanup then reboot the computer. It worked for me.

When you try to use Windows Vista, Windows Vista may not behave as expected. For example, some Windows Vista functions may not work, or Windows Vista may stop responding. This issue may occur if a Windows Resource Protection (WRP) file is missing or is corrupted. To resolve this issue, use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: 1 Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. 2 Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect or corrupt versions with correct Microsoft versions.

change the user account to administrator, to unlock privileges.
That should solve your problem, remember to restart the pc so changes are made in the registry

kind regards and please don't forget to rate us

vista doesnt alloow users to intall operating systems prior to it. thats the problem.
but theres a software named 'Vista boot pro' it can help u booting it.

I found a solution for *my* problem, by shrinking the MTU in my router.

I have two Vista PCs at home that can't access LinkedIn's sign-in page.

I was suspicious that several browsers seemed to be having a problem, which made me think it was either a virus middleman in the network code, or a router problem. I eliminated the virus possibility by replicating the problem on another PC.

By changing the MTU on my home router from Auto to 1452, I got the signup page to appear.

It appears that Windows Vista's new TCP stack does some advanced segment and window sizing and that didn't work with my Linksys RV042 router's Auto MTU setting. I'm not 100% sure what it is about LinkedIn that caused a packet of just the wrong size, but this is the second time I had to tweak this router to work with Vista. First I needed a firmware upgrade to get some traffic flows to work at all, and now this MTU change.

I do know I've had to change MTU settings in the past to work with encapsulation protocols like PPPoE, but I haven't had to change the MTU setting for quite some time...

Maybe this clue will help someone else...

TCP/IP stack repair options for use with Windows XP with SP2 & Vista.

For XP, Start, Run, CMD to open a command prompt.

For Vista, Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

Reboot the machine.

if the Issue presist then you need to try System restore
If Windows XP starts loadTOCNode(3, 'moreinformation'); 1. Log on to Windows as Administrator. 2. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click System Restore. System Restore starts. 3. On the Welcome to System Restore page, click Restore my computer to an earlier time (if it is not already selected), and then click Next. 4. On the Select a Restore Point page(try the date 2 dats prior it was working or the First Bolded Date of that month), click the most recent system checkpoint in the On this list, click a restore point list, and then click Next. A System Restore message may appear that lists configuration changes that System Restore will make. Click OK. 5. On the Confirm Restore Point Selection page, click Next. System Restore restores the previous Windows XP configuration, and then restarts the computer. 6. Log on to the computer as Administrator. The System Restore Restoration Complete page appears. 7. Click OK.