System Admin

Couldn't use your Windows 2000 install disk and boot the repair console and do it from there? Why waste time learning when ignorance in instantaneous -Hobbes

Thanks! -Sean ---- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Albert Einstein. I saw a woman wearing a sweatshirt with 'Guess' on it. I said, "Thyroid problem?" -- Emo Philips. Love is two minutes, 52 seconds of squishing noises. -- Johnny Rotten.

Open Control Panel Double-Click on 'Administrative Tools' Double-Click on 'Local Security Policy' Local Policies\Security Options Set the appropriate option under 'Interactive logon: Do not require CTRL+ALT+DEL' -Sean ---- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Albert Einstein. I saw a woman wearing a sweatshirt with 'Guess' on it. I said, "Thyroid problem?" -- Emo Philips. Love is two minutes, 52 seconds of squishing noises. -- Johnny Rotten.

Start->Run gpedit.msc Click OK. -Sean ---- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Albert Einstein. I saw a woman wearing a sweatshirt with 'Guess' on it. I said, "Thyroid problem?" -- Emo Philips. Love is two minutes, 52 seconds of squishing noises. -- Johnny Rotten.

Chris Hansson wrote: Has ANYONE run into this irritating problem? And if so, has anyone a solution. I am rather close to doing a fresh install of Windows 2000 Professional, but then I would have thrown away the $200 I paid for XP Professional, and that irks me. It is not just WXP, I use WXP and ASP.NET works just fine. What does happen though (and it happens on W2K as well) is that the file associations in IIS for ASP.NET disapear. I have not found the cause, but it has happened to me once before. To check go into IIS and then: Right Click the Default Web, select Properties. Then click the Home Directory tab and click the Configuration button. Now in the list displayed in front of you look for the ASPX file. If it is not there or the Executable Path does not point to aspnet_isapi.dll then you need to run the following command which re-associates ASP.NET files in IIS. C:\WINNT\Microsoft.NET\Framework\v1.0.3705\aspnet_regiis.exe -i Obviously replace WINNT with whatever your Windows path is. Hope that helps :) Paul Watson Bluegrass Cape Town, South Africa Ray Cassick wrote: Well I am not female, not gay and I am not Paul Watson

From Windows Help: To add an alias (CNAME) resource record to a zone Open DNS. In the console tree, click the applicable forward lookup zone. DNS applicable DNS server Forward Lookup Zones applicable zone On the Action menu, click New Alias. In the Alias name text box, type the alias name. In the Fully qualified name for target host text box, type the fully qualified domain name of the DNS host computer for which this alias is to be used. As an option, you can click Browse to search the DNS namespace for hosts in this domain that have host (A) records already defined. Click OK to add the new record to the zone. Note: To open DNS, click Start, point to Programs, point to Administrative Tools, and then click DNS Not much help, is it? A CNAME record in DNS creates an alias for the host other than the base name contained in an A record. If this isn't helpful, perhaps a bit more detailed information about what you're trying to accomplish would be in order... "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long

You need at least a Win2k server to create a domain, otherwise just put the computers in the same workgroup. "The greatest danger to humanity is humanity without an open mind."   - Ian Mariano - http://www.ian-space.com/

zhoujun wrote: "access to directory is denied" That usually means that the IUSR_MachineName account doesn't have enough permissions on the directory. Try giving it "Read", "Read & Execute" and "List Folder Contents" permissions. Also, click on the "Advanced" button on the security tab, and tick the box, "Replace permission entries on all child objects...". IISLockdown isn't required, but I like to put it on every IIS server connected to the Internet as an extra security measure. Anything that helps keep hackers and viruses out can't be bad! :-D

who to make domain on xp_professional ? r00d0034@yahoo.com

Roger Wright wrote: In the event that a company wants to set up multiple sites on an intranet, I assume then that the DNS entries would only have to be on the local DNS server, not on the public DNS system. Yep. You can even add entries to the "Hosts" file [C:\WinNT\System32\drivers\etc\hosts] to change the settings on a single machine, which is very handy if you need to test a site on your server before transferring the DNS. :)

I tried to see error messages. But of no use. And still have the problem... Still confused...

Each user will need a local account on your server, and will have to enter a username and password when the login box appears. The shares you want them to be able to access will also have to have permissions set for each user to allow it. Did you follow the instructions in Richard's response to my question? They worked perfectly on my machine. "When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long

You should really check out the IIS Performance Counters Reference[^] and Logging Properties Reference[^] "The greatest danger to humanity is humanity without an open mind."   - Ian Mariano http://www.ian-space.com/

Buy the Pro version, Megan - it's cheap, and so much nicer! "Another day done; all targets met; all systems fully operational; all customers satisfied; all staff keen and well motivated; all pigs fed and ready to fly." - Jennie Agard, McGuckin Hardware Systems Manager

I recently set up my first XP network, and it was a major hassle! At least you have the Pro version; the Home edition is a lot like Windows 95 on saltpetre! First off, create an Administrator account for yourself on both machines, and assign yourself a password. Then kill the Simple File Sharing - it sucks, and prevents you from using any of the traditional networking functions you're used to. When SFS is enabled (the default), all access to remote computers is done using the Guest account. The Guest account is disabled by default on all new installations, so nothing works. Once you change this setting, things will look a lot more familiar. I believe you do this from Windows Explorer, in the Folder Options function on the View tab. Uncheck the Use Simple File Sharing box. This is supposed to restore the classic Windows security system and allow you to view and manage shares and services from any PC on your network. After you make these changes to both systems, reboot them both. All users will now have to have passwords, just like previous versions, and you should have a lot better success with your project. Try it, and post your results here. If it doesn't help, we'll try some other options!:-D "Another day done; all targets met; all systems fully operational; all customers satisfied; all staff keen and well motivated; all pigs fed and ready to fly." - Jennie Agard, McGuckin Hardware Systems Manager