|
Hi!
I have a stand-alone home PC running Windows 2000 Professional. I've installed IIS service but it can't start.
I got the next message in Event log:
The World Wide Web Publishing Service service terminated with the following error:
The authentication service is unknown.
The same error is appeared when I try to start FTP or SMTP service. What's wrong? Please, help me to start IIS service on my home PC!
Yours sincerely,
Alex Bash
|
|
|
|
|
Mhhh...Hard to tell you, i need to it.Well, uninstall IIS, then install IIS if this not help you, maybe you bad configured IIS.For more information look at http://www.iisanswers.com/Top10FAQ/t10-installiis.htm 
Zhymantas Vechorskis
|
|
|
|
|
we have 2 computer network.we made 2 new user on 2 computer with same
name and passwords on both computers.we first kill the simple file
sharing and uncheck the "use simple file sharing" in window explorer.
we succeeded to get right to access the network computer service on
one computer.but other computer was not showing the services of other computer.
we made some changes and then try to access the service.
in doing so break our network connection and now network path is not establishing.please give the bettter way to solve our problem
how to establish network path
how to access the right to accees the network services
and how to make a domain on 2 computers
|
|
|
|
|
Hi!
When I try to export my messages in Outlook Express, the process abnormally closes with the message
'An error occured initialising MAPI'.
I am using Windows XP Professional. Previously in NT, this happened and I installed 'Windows Messaging' Setup from Control Panel -> Add/Remove Programs -> Windows Update. But in Windows XP, there is no 'Windows Messaging' setup available.
Please suggest me a solution for the abovesaid problem(s)!!!
Deepak Kumar Vasudevan
http://deepak.portland.co.uk/
|
|
|
|
|
Any time I try to create a new website, or a new ftp site, the wizard pops up and all goes smoothly until I try to start it. When I attempt to start the new site, I receive the error message "A duplicate name exists on the server." It does not. And there are no clues other than this message. I've searched Technet for this exact message, but there is nothing in the Knowledge Base that matches this phrase, and any looser search returns only totally irrelevant articles. Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2? There are no duplicate names anywhere on the machine; not sites, folders, or files. Clues would be most welcome...
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
Roger Wright wrote:
Is there an unmentioned limitation to one website and one ftp site in Win2K Server SP2?
If there was, I don't think you would be the first person to find it.
I aint ever used 2k server apart from telnetin and pure Ftp.
But is it a duplicate name or a duplicate name space.
Talking about spaces, I hate the idea of using them in names.
I remember this use to screw an old DOS version bad.
Regardz
Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining.
Said by Roger Wright about me.
|
|
|
|
|
Yes,when I try to create a new ftp site other than default ftp site in IIS,everything is ok,
But when I want to start it,errors pop up.
Are there any veteran web administrators who can give us some advices?
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
Each web-site in IIS must have a unique "address", which is a combination of:
- The IP address it listens to;
- The port it listens to - normally 80 for HTTP and 443 for HTTPS;
- (For HTTP sites only) The Host Header name;
Assuming you are just setting up standard HTTP sites, you can host multiple sites on the same machine by changing one of these three parts.
Since you will probably be using a single IP address, and you don't want to change the port, this leaves the Host Header name. Set this to the domain part of your site's URL - for example, www.site1.com. Assuming the DNS for www.site1.com is pointing to your server, you will then be able to open http://www.site1.com in your browser and see the pages for Site 1.
If one site serves multiple URLs, you can add other entries by clicking the "Advanced" button in the properties of the site.
NB: If someone requests a URL which is pointing to your server, but the domain is not set up as a Host Header name, the request will be passed to the default site, which has no Host Header name set. The simplest way to deal with this is to create an "Under Construction" page as the only page in your default site.
FTP does not have the Host Header name, so if you need to host multiple FTP sites, you will either need to change the port, or configure multiple IP addresses on your machine.
|
|
|
|
|
Wow! You're a treasure trove of IIS information, Richard! Thanks! I'll give that a try. Not knowing what to do with the header name box, I just left it blank...
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. That seems to be what Zhoujun is trying to accomplish.
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
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 encounter problems when seting up ftp services and web services with my newly installed win2000 server.
what I want to do is:I have many users who want to publish their web applications,so I should create a respective directory for them,and each one get a user account to access their directory which others cannot access,in other words,they and only themselves can manage or control a server path,including upload,delete,mkdir etc. via ftp.
That is one aspect,another aspect is when they are ready finish preparing their web applications,their web access is open to everyone using browsers through visual path in default website or a new website.
I want your help.My english is not very good yet,but I really want your or others' help.
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
That's an entirely new and different problem than before... Very well stated, Zhoujun, and I'm having similar trouble myself. I can't find a thing in the documentation about how to do this. If you find out first, tell me, please!
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
Thanks,you finally understand me.
If I get the answer,I will tell you right away.
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
zhoujun wrote:
If I get the answer,I will tell you right away.
Thanks, buddy! This is not a trivial problem, and the documentation is really bad. There's lots of it, but the content lacks any value.
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
I'm going back many years in old Network theory to the time of G-net. And I wonder if the same theory holds.
Make a User Directory, with a subdirectory. The individual users should only have the full permissions you want to give to their subdirectory.
Next give each of the users view/read permissions to their own user directory.
I always found mastering network stuff was easiset with several machines side by side, and a good swivel chair. Ouch !!!
Regardz
Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining.
Said by Roger Wright about me.
|
|
|
|
|
Been there, done that. It doesn't work, so I burned the t-shirt.
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
- First, prepare the default FTP site.
- Apply all security patches
- Install IISLockdown.
- Make sure that write access is disabled.
- If possible, turn off annonymous access, otherwise make sure the anonymous account is not the IUSR_MachineName account.
- Create a user account with "Log on locally" priveleges, which will be used to upload the site.
- Create a directory for the web application. Preferably, nowhere near the wwwroot, ftproot or inetpub directories. Set the following NTFS permissions:
- The Administrators group and the upload account should have full control
- The IUSR_MachineName account should have read access.
- Nobody else should have any permissions. Specifically, if anonymous FTP access is allowed, the anonymous FTP account should not be able to read this directory.
- In the default FTP site, create a virtual directory pointing to the web application directory. Give it the same name as the upload user, and enable write access.
- Once the site is ready, create a new web-site pointing to the web application directory.
When the upload user logs in, IIS will automatically move them to the virtual directory with the same name as their user name.
Since the directory is a virtual directory, anonymous FTP users will not be able to see it.
The NTFS permissions won't allow anyone other than the upload user to access the directory, so other users won't be able to read or change the contents, even if they could guess the name.
By granting read access to the IUSR_MachineName account, anonymous users will be able to view the web site.
Hope this helps!
|
|
|
|
|
Thanks,Richard,
I follow the directions you give,
everything seems working well,
and finally,the ftp part works as I want to,
but when browsing to that website,I got error messages in IE browsers that said "access to directory is denied"?
by the way,I did not install IISLockdown since I thought it's an option,
and when setting the directory's NTFS permissions,I do like this:mouse right-click that directory,select the last item properties(R)(I don't know if I am right in translating the item name because what I am seeing is in chinese) from the pop-up menu,then select the security tab,then set permissions as you said,original it has everyone access rights,and I delete it.
I want your further help.
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
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! 
|
|
|
|
|
i dont have the rightes to see service on other computer of my network.
i have a simple network of two computer and the operating
system is XP on both computers.
i am able to share dives,internet fasilities on other network computer.
but problem is that
i dont have the rightes to see service on other computer of my network.
how to get rightes to see services? the answer did not solve my problem please give a better suggesation to solve the problem
r00d0034@yahoo.com
r00d0034@yahoo.com
|
|
|
|
|
the account that u use to logon can be made part of the 'Administrator' group. I am not too sure. Perhaps from a domain part of you, that should work like making the domain user account part of Local Administrator and logging on with that, as we do. But since you do not have a domain controller in between, the account used to login to the other system must be part of 'Administrator' group.
Deepak Kumar Vasudevan
http://deepak.portland.co.uk/
|
|
|
|
|
who to make domain on xp_professional ?
r00d0034@yahoo.com
|
|
|
|
|
I installed my windows 2000 server with IIS 5.0.
Now I want to allow users to ftp to server and transfer files between users' client pc and server,
But How can I setup the server to achieve that one user can only access to a specified directory on the server and can not access to other users' directory.(ideally,the directory may just be the user name)?
And in that user-specified directory,everyone can access that directory(the directory is setup as a web visual path and the specified user can upload website files) via browsers but not ftp?
What I have done is: I create a user and according to username a directory on the server harddisk,and setup the path as a visual ftp directory in IIS manager interface,but everyone can visit that path,and if I setup the path's access rights to specified user,then browser to that path is prompt user to provide user and password?
Roger's reply:
I just went through this hassle - the solution is non-obvious on Win2K Server. Check my thread on the Operating Systems forum; the response from Richard D solved my access problem nicely. Quicklink[^]
I couldn't give access to users who had perfectly valid user accounts on my domain. It turned out that local logon rights are denied by default on the Server edition. The link Richard provided gave detailed instructions on how to enable this. Once you enable it, your users should be able to get into the computer and the FTP area. Limiting access to specific shares for each user can probably be done using NTFS rights on each folder. I don't know that for sure because I haven't tried it. Only one user beside myself has access, and I trust that one - I haven't tried limiting access yet. If this doesn't work, move this discussion to the Operating Systems forum and we'll continue it.
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
Yes,using NTFS rights on each folder can solve limiting access to specific shares for each user.
But another problem occur,since I have setup the user directory as a visual path of default website in IIS manager,when client browse to that web path,he will be prompted a popup windows to provide user name and passord because I have delete that directory's everyone rights.
this is my signature for forums quoted from shog*9:
I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.
|
|
|
|
|
Forgive me if I sound dense - It's very late and I'm having some trouble understanding your English. You're doing great, but I'm tired... You should not be using the default website in IIS; put the shared folder in the default FTP site. When your users connect they should use 'ftp://zhoujunsdomain.com' to establish a FTP connection. A logon dialog box should then appear, and they should type in the proper username and password. The next screen they should see is a collection of folders stored in the Default FTP Site location. From there it should be no trouble to open any folder for which that user has permissions to use. Removing the Everyone Group is a good idea, by the way, but you have to be sure to create permissions for each user that you want to have access. I created a group called FTPUsers for just that purpose, and it's working well so far.
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
