Hersch

Cluberti, thanks yet again for your reply! And one more time I wish to get this understood that I want to add a proper route via the command line. I know that i can even setup the native Win XP Internet Connection Sharing and it will take care of my problem. But where is the joy in not being able to figure out manual routing when the OS actually supports it. All the same, I will keep your suggestion foremost in my mind. Because if nothing else works, sure there is AnalogX after all.

Cluberti thanks for your reply. But the question is about routing and not setting up a proxy or other 3rd party software.

To all the MSFN Guru's. Please take time to understand my problem and give the right answer in detail. Your help is much appreciated. Now to the actual question: I have 3 PCs at home in the following configuration and I do not want to use the Windows XP Internet Connection Sharing. I want to route my other home PCs manually so that I can continue to have my own private LAN (workgroup setup) and still be able to acces the internet from any PC. I have my home network on a completely wired setup (Gigabit Ethernet). PC1 - Windows XP SP2 - 2 Onboard Gigabit NICs - Kerio Personal Firewall - Workgroup Computer 1) NIC1 is connected to my ADSL Modem (Siemens SpeedStream 4200) and the IP is set to 10.0.0.1 with a class A default gateway (255.0.0.0). This is the internet interface and works fine. No issues here 2) NIC2 is connected to my private home network and has the IP 172.10.16.5 with a standard class B default gateway (255.255.0.0). This interface connects to my internal private LAN and I can browse my workgroup computers, printers, shares etc without any problems whatsoever. PC2 - Windows XP SP2 - 1 Onboard Gigabit NIC - Setup as a Workgroup computer 1) The NIC is connected to my private home network and has the IP 172.10.16.3 with a standard class B default gateway (255.255.0.0). This interface also connects to my internal private LAN and I can browse workgroup computers, printers, shares. No problems here too. 2) It is on this and another PC (with same IP / Subnet class 172.x.x.x, 255.255.0.0) that I want to be able access the Internet using PC1 as the Routing Machine. I believe this is possible but I am a bit lost on how to achieve this. My research has led me to believe that I should use / setup a Persistent Static Route on PC1, so that all my workgroup machines can access the internet. My only issue is that since the Route command is a set of commandline commands (hope this is making sense) and I seem to be hopeless at this stage in typing it correctly, can one of you kind souls spell out the command for me in detail so that I can type it and set the route? I will be forever grateful to you guys if you can help me with this! Oh and btw, please don't give the lowdown on the route syntax etc. If possible please give me a detailed example using the IPs that I have detailed above. Thanks in Anticipation!!!! Hersch

Problem solved! Thanks to nLite! What a wonderful tool it is. My grateful thanks to the Author of this fantastic program.

The Problem: 1) I have to install 10 Dell PowerEdge 2950 Servers with Windows 2003 SP1. 2) The 2950s do not have a floppy and the USB Floppy Emulation fails half way through the setup, leaving me to scratch my head. Even an attached USB Floppy fails to be detected properly, hence RAID Drivers cannot be loaded. 3) These servers also have the new SAS (Serial Attached SCSI) drives and the LSI Logic SAS 5i RAID Controller. Required Solution: 1) How to include the LSI Logic SAS PERC 5i RAID drivers on the W2K3 SP1 CD so that I can install these servers. I have the Original Installation Media 2) Since I am new to this, please explain in simple steps how to modify the Installation CD and the Folder Structure needed to install the RAID drivers automatically. I believe that I may have to create a $OEM$ folder, but I dont know at which directory level this must be done. 3) Any other related help that will ease this for me is also very welcome. Thanks in Advance to all the Learned Members of this Forum!

Your link on the first page does not work! Is there an alternate one?

Please read the whole post first - Thanks in anticipation! The Problem: I manage a medium size Windows 2003 AD LAN/WAN. All the IT Admin is centralized, staff strength is very thin on the ground and we have about 1000 XP Pro PCs and 400 Laptops across various sites. For ease of management all our PCs and Laptops are deployed using an SOE (Standard Operating Environment) image, which is fairly restrictive and offers just a few Multi-Media options. Users cannot install or modify the OS, Applications, Drivers etc. Now all of sudden the management wants all the PCs to have full blown Multi-media capabilites, which means that we now have to compile and deploy a number of popular codecs and a few media players across all the 1000 PCs. Now you will say "Well that's easy, just create an MSI package and use AD Group Policy for the rollout". So far so good and the concept at least on paper is sound enough. However, this is where help is sorely needed: How do I: 1) Create the Codec package to deploy via Group Policy. This will mean, decompressing and extracting all the needed codecs and players from a number of popular codec packages, then compiling my own package, probably in MSI format, and then deploying it to all the PCs. If there are other automated solutions then I would love to hear about them as well. 2) Specifically what tools or commands can I use to decompress and extract the needed codecs/players from popular codec packages? I need a lot of detail from you guys as I haven't done this before and hand-holding will be deeply appreciated. This is not a typical application rollout, I can handle those! 3) Assuming that I have amassed and documented all the required codecs/players. How do I create an MSI package. Meaning, what program can I use to create the MSI package and how (detailed instructions would be greatly appreciated)? To do this, I would prefer to use free software as much as possible. Please detail your experiences with stuff like WinInstall LE 2003, AutoIT etc and advise which is the best possible solution in my situation and why? 4) Lastly, I am sure that the problem I face is not unique and that someone has already encountered this dilemma before and has already solved it. And yes I have read Shark007's post in great detail and I am quite inspired by it. So Dear Shark007, if you happen to read this post, your intervention in solving my predicament will be appreciated to the nth degree! Finally, thanks to all of you for your patience and attention, this forum is the top dog in the Microsoft Desktop World! Hersch