• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hrp2171

  • Birthday 02/01/1971

Contact Methods

  • Website URL
  1. Here is some more information: Wireless Access Point/DSL router: IP = Directly attached to DSL router XP computer: IP = XP laptop with wireless and ethernet cards: Network Bridge IP = and IP Router Enabled in Registry 2003 Server computer: IP = Second XP computer: IP = All the computers have the Wireless AP setup as the default gateway. From the laptop, I can ping the separate LAN segment and I can ping the segment that's attached to the Wireless AP. Something weird happened though, for a few minutes the 2003 Server box was able to connect to the 'net. I took advantage of that and download the latest patches from MS and also updated AVG. After rebooting, the 2003 server is back to not being able to see beyond the laptop. Weird!
  2. Howdy, I have a small XP network. I'm using XP Professional for workstations and I have one 2003 Standard server. My Network: 1 Wireless Access Point 802.11b also has a built-in dsl router 3 workstations running XP Professional 1 2003 Server Standard Only one 2 of the XP workstations are currently able to surf and connect to the net: 1 is attached directly to the WiFi AP-DSL router 1 is a laptop using a wireless pcmcia card The other XP workstation and the server are on a separate network, connected to each other thru a hub, and I don't have a way of running a cat5 cable to the WiFi AP-DSL router. I can't afford to purchase any more equipment. Period! Now for the clincher. I have installed an ethernet(wired) PCMCIA card in the laptop. From the laptop, I can connect to the Internet through WiFi and also hook up to the separate network through the ethernet card. I created a network bridge on the laptop and assigned it a private ip address and the other needed information. I have also enabled IP routing in XP. On the server, I typed the laptop's network bridge IP address as the gateway. However, I bring up Internet Explorer and cannot surf the 'net. Nor can I see the other workstation attached to the dsl router. Before some includes instructions on how to create a network bridge in XP, please know that there are plenty of those on the Internet. I know this because that's all I get when I search for 'network bridge' in Google. With all I've done, how come the Server computer can't see pass the laptop and out to the 'net? Thanks for your help. Hopefully, I was detailed enough. If you feel more information is needed please let me know.
  3. Hmm, I've already tried using "Drivers\NIC" for my OEM drivers path. I'll try it again. It seems though, that it doesnt matter which path I use it ignores my OEM drivers path and it wants to use the one in the registry. Thanks for the links. I'll keep this thread updated.
  4. This is an FYI. Hopefully this information will be helpful to others. I posted the same question about sysprep 2.0 and XP at the Microsoft's OEM System Builders newgroup. I was told that sysprep 2.0 removes all network interfaces when it runs and you have to have Signed drivers for your network card if you want it to work after mini-setup is done. There is a workaround by adding the 3 lines mentioned on my previous post. However, it's still not working as prescribed and I'm always being prompted for the location of the unsigned drivers for my network card. I will master the process no matter what.
  5. I'm getting close to Windows XP mini-setup nirvana. The last 3 lines in the [unattended] section are part of the solution. I'm still running into another wall, but will soon find out how to get around it. Here is my newly modified sysprep.inf based on some tips found on the 'net: ;SetupMgrTag [unattended] InstallFilesPath=C:\sysprep\i386 OEMSkipEula=Yes DriverSigningPolicy=Ignore OEMPNPDriversPath=c:\sysprep\i386\$oem$\$1\drivers\nic UpdateInstalledDrivers=Yes [GuiUnattended] EncryptedAdminPassword=NO OEMSkipRegional=1 OEMSkipWelcome=1 TimeZone=4 AdminPassword="adminpasshere" [userData] ProductKey=product-key-here FullName="IT Dept" OrgName="IT Dept" [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=831 LongDistanceAccess="9" [identification] JoinDomain=domain [Networking] InstallDefaultComponents=Yes
  6. H E L P!!! S. M. S.!!! Save My Ship!!! Here it goes: Whenever we order new computer systems, I install the OS and all the apps we need from scratch. We also customize the settings and create a default user profile. After that's done, we run sysprep and use Norton Ghost to create an image to use on the rest of the systems. With Windows 2000 Professional, that process works great but I'm running into problems with Windows XP Professional. Mainly, Windows 2000 would just prompt for a computer name and the admin password because that's the way we setup the sysprep.inf file. After mini-setup, Windows 2000 would just come up ready for production. On the other hand, Windows XP keeps losing the network card drivers. It prompts me to install the network card drivers after mini-setup is done. It's so annoying to see that after a successful sysprep configuration. Windows 2000 does not change anything in the hardware configuration whatsoever. Why is Windows XP losing the network card configuration? Is it sysprep that's mucking up the network card configuration? Here is the line I use for sysprep 2.0 in XP: sysprep.exe -mini -reseal -quiet -reboot Here is the sysprep.inf: ;SetupMgrTag [unattended] InstallFilesPath=C:\sysprep\i386 OEMSkipEula=Yes [GuiUnattended] EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=4 [userData] ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx FullName="IT Department" OrgName="IT Department" [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=831 LongDistanceAccess="9" [setupMgr] DistFolder=C:\sysprep\i386 DistShare=windist [identification] JoinWorkgroup=workgroup [Networking] InstallDefaultComponents=Yes Thanks, Hector
  7. Thanks for your reply. After I started this topic, I created a Test OU, created a GPO attached to it, and added a workstation to the OU. I also created a Test User with plain vanilla rights, but in the OU's Restricted Groups setting, I made Authenticated Users part of the Power Users group. I logged onto the workstation and a few minutes later a prompt came up telling that the updates were ready to be installed. It worked without a problem. I also did a test to see if no one was signed on, would it just install the updates and restart the computer. It did! Now I have 2 options: Make all my users Power Users or Just tell everyone to leave their computers powered on overnight and let the GPO take care of installing and restarting the computers. This is some cool stuff when it works.
  8. Hi, I've been working with Microsoft's SUS Server software and Active Directory. It works great, except that if an Admin or Admin-like user is not logged on, the patches are not made available for installation. The patches are all being downloaded to the workstations just fine. I'd hate to give Everyone in my network Admin rights to their workstations when( and if ) I can do it with just Power Users rights. I'm still researching through Microsoft's web site and on the 'net, but if someone knows about this, I'd appreciate your input. Thanks, Hector
  9. Check out this article: And check out this Google search: Also, you might qualify for a free subscription to Network Computing magazine.
  10. Here is checklist you can work with: 1. All of the computers should be using the same Workgroup name 2. All of the computers need to have the same user accounts and passwords 3. All of the computers should be able to ping each other They all have to be on the same proverbial page, before you even start sharing files/folders out of the acting-server.
  11. Defective hardware. I have a stack of PCs, all the same make/models, and the NICs keep malfunctioning. I loaded the built-in drivers and the vendor provided drivers. It didn't help one bit. Then again, you could try the same NIC at another PC( if it's not integrated into the motherboard ) and see what happens. Keep us posted.
  12. If the hotfix is already installed, SP4 should bypass installing that hotfix again. But I could be wrong! After installing SP4, go to the Windows Update site and see if the hotfixes show up again as download options.
  13. Is this file on your hard drive? Most files with the squiggly are temporary files opened by some application/program while running. The program places a lock on the file to avoid accidental deletion. Since you're booting Windows 2000 on a FAT32 partition, you could use a DOS bootdisk and navigate your way to that folder and delete the file. The file in question could be hidden and read-only. Run attrib -s -h -r filename.ext to make the file visible and delete-able. Have you tried right-clicking the file in Explorer and looking at the properties? It should show if it's read-only, hidden, etc. Keep us posted.
  14. Hi, BigDaddy! I have a Norton Ghost image that even when the Screensaver is set to none, it will still lock the screen after 15 mins. In order for me to disable it, I have to pick a Screensaver then clear the password protection. Terminals Services as well as Remote Desktop Connection will always ask for a login and a password. But by looking at the screenshot, I can tell the prompt box is coming from the screensaver settings. Hope this helps.
  15. Hi, We have a Windows 2000 Active Directory network with 200+ workstations. We use a Norton Ghost Image with all of the apps our users would need. I would like to remove one of those apps using AD. However, the app was not installed using AD in the first place. Is there a way of uninstalling an app even though I didn't use AD to install it? For example, with Novell ZENWorks, I could take a snapshot of a machine before removing an app. Then remove the app and take another snapshot. Finally, using ZENWorks, I could remove the app by using the difference between the snapshots. For clarification, we're not using Novell servers with ZENWorks. I was using the example based on my previous job. I hope this makes sense. Heh! Thanks, Hector