Marsden

Use Remote Desktop...

Nothing worth wasting your time over...

Do An Upgrade Inplace after booting from your XP CD-ROM. It is the 2nd Repair Option...

You don't need ICS with a hardware Router. Just configure each machine with a Gateway IP address which is the IP address of the Router. 192.168.0.215 All machines will then point to the Router as the Gateway...

Boot from your install CD-ROM and select the Recovery Console. Run FIXMBR from the command prompt...

XP will have all the drivers you need.

That is a feature... try it as Administrator...

MS recomends Windows XP Service Pack 2 Windows Media Player 10 works best with the latest software version of the Player and operating system. I think that means SP2!

VNC is NOT encrypted, Remote Desktop is... RDP is encapsulated and encrypted within TCP. VNC uses a random challenge-response system to provide the basic authentication that allows you to connect to a VNC server. This is reasonably secure; the password is not sent over the network. Once you are connected, however, traffic between the viewer and the server is unencrypted, and could be snooped by someone with access to the intervening network. We therefore recommend that if security is important to you, you 'tunnel' the VNC protocol through some more secure channel such as SSH. You have to add SSH to make it secure...

Look at Roaming Profile...

WMP10 will not install on anything less than SP2...

Your SP1 install is buggered... Fix it and then install SP2. You can do this by trying an Upgrade in Place. Look it up on Technet is you need step by step directions...

Who in hell wants DRY DEAD meat? I want it trying to crawl off the plate... then I know it is fresh. If you want well done, then just take your shoes off and eat them... cheaper too!

Both the local host and the remote client need port 3389 open to allow UDP traffic. Remote access has to be allowed on the remote client. Win2K3 can remote into an XP client but not Win2k and earlier. Any earlier client with the proper RDP client software can remote desktop into Win2K Server, XP and Win2K3 server.

NLB requires at least 2 machines, each with 2 NICs. Network Load Balancing (NLB) clusters dynamically distribute the flow of incoming TCP and UDP traffic among the cluster nodes according to a set of traffic-handling rules. NLB clusters provide a highly available and scalable platform for applications such as IIS, ISA server, etc. NLB is used for stateless applications; i.e. those that do not build any state as a result of a request. NLB and server clusters compliment each other in complex architectures: NLB is used for load balancing requests between front-end web servers while server clusters provide high availability for backend database access. Multiple NICs in cluster nodes Windows 2000: • If you have 2 NICs on different subnets then the NIC to which NLB is bound should have default gateway and the routing tables need to be reconfigured to make all traffic go thru the NLB NIC. Default gateway setting on the other NIC should be blank. • If you have 2 NICs on the same subnet you will need to configure the NIC to which NLB is bound with the default gateway. The other NIC should not have a default gateway configured. No need to hack routing tables. • Recommendation is to use one NIC in each node unless there is a business need for 2 NICs Windows Server 2003 • If you have 2 NICs different subnets you can choose to bind NLB to either or both NICs without any issues. All traffic will go thru the correct NIC (subnet) • If you have 2 NICs on the same subnet traffic will be routed accordingly.

Nope! You have been hijacked!

Some programs like HJT can give you an informative log report but are helpless in actually fixing your machine. You will need to kill rouge services, scour your Registry, delete suspect DLLs, EXEs, and DAT files in your C:\WINDOWS and C:\WINDOWS\SYSTEM32 folders from within the confines of Safe Mode. These hijack exploits are new and getting better at buggering your machine six ways to Sunday. Look for DLLs and EXEs with the same file size (different dates) and not signed by any well know software developer... MS signs all it's files...

Ulead VideoStudio 7.0 The file USIUDF.sys is causing your BSODs. Loose Ulead and your problem will disappear. Next ask Ulead for better drivers... Or it could be the following for STOP: 0X0000008E errors: "STOP 0x0000008e" Error Message During Windows XP Setup A "STOP 0x0000008E" Error Message Occurs in Wdmaud.sys A "STOP: 0x0000008E" Error Message Occurs When You Change the Hardware Acceleration Setting STOP 0x0000008E Error Message on a Blue Screen and Your Computer Does Not Enter Hibernation or Standby After You Remove an IEEE 1394 Storage Device STOP 0x0000008e Failed To Install Product Catalog

This mass-mailing worm drops copies of itself in the Windows system folder as SWCHOST.EXE and SVOHOST.EXE. It also drops a copy of itself in the Windows startup folder as SVCHOST.EXE. It creates the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\ CurrentVersion\Run load32 = "%System%\swchost.exe" (Note: %System% is the Windows system folder, which is usually C:\Windows\System on Windows 95, 98, and ME, C:\WINNT\System32 on Windows NT and 2000, or C:\Windows\System32 on Windows XP.) It also attempts to register itself as a service process. On Windows NT, 2000, and XP, it also adds the following registry entry: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\ CurrentVersion\Winlogon Shell = "explorer.exe %System%\svohost.exe"

DNS round robin... NLB (Network Load Balance) is much easier and more efficient than DNS RR.

XP SP2 does not require anymore memory that a clean install of XP! A better question is how many non-Microsoft services are running at startup sucking up memory? Please open 10 IE sessions, Photoshop CS with an Excel session and 2 Word sessions and then tell me 256 works... I'd say you don't have a clue what you are talking about...

You can have multiple domains or workgroups... You can also bind static and DHCP to a single NIC.

Does the client have permission to access both machines? Sounds like permission is only allowed on machine 1... The user has to be allowed on both...

The CD-ROM is damaged or dirty. The program files on the network share are corrupted, missing, or hidden. Another program that is running on your computer is interfering with the installation of Office. If your Office XP CD is damaged... copying it to your hard drive will not solve the problem. Use a clean boot to restart your computer, and then see if the issue persists. A clean boot is a method to create a clean environment. When you start your computer with a clean boot, Microsoft Windows starts and loads only the basic devices and services. To restart your computer with a clean boot for XP: Click Start, and then click Run. Type msconfig in the Open box, and then click OK. Click the General tab, and then click Selective Startup. Under Selective Startup, click to clear the following check boxes : Process System.ini file Process Win.ini file Load Startup Items Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All. Click OK, and then click Restart to restart the computer.

BTW, there is no tool currently available that will clean this pest off your machine. I know this because I tried them all...