I understand how to use the IIS AppPool\website in assigning permissions to the website folder in a workgroup server. But when I make the web server a member of my domain, I'm not able to use the same AppPool Identity. I tried DomainName\IIS AppPool\website. So In the meantime, I made the server a workgroup member.
I want to experiment with the Hyper-V hypervisor and put 3 virtual servers on it, that feed off a special share from 1 of the hypervisor drives, and I'm having trouble with the permissions. I experimented with the NLB, but was missing a couple of things on the shared disk drive.
I still haven't figured out how to use domain permissions for the Application Pool using the ISS AppPool assigned to the Application Pool on a web server that is a domain member.
I've come to the conclusion that if your web server is a domain member, your probably only running one website, so you can just make a machine account for it, and assign it to the App Pool and then the folder.
If your hosting websites, then running the web server as a work group member is the way to go. I'm not going to make hundreds of special accounts for the app pool now.
So what about the SQL Server, make it a domain member or a work group member. Now I ponder that question, but I made it domain member using SQL credentials.
Now I have the 3 virtual machines running on the hyper visor, normally I would dedicate a physical server to database programs, and separate the 2, but I'm thinking that the 2 virtual machines constitute separation.
Well no awnsers here at the moment, still waiting for an expert to comment on it.
I did figure out how to setup the web server to run on a hypervisor server core, and the virtual machines are cores as well. Uses much less memory now, I think I bought way too much RAM now.
One thing funny is that I run FFMpeg and had to adjust the core to minimum GUI so I can get the shell and scrape it for data. Didn't think of that when I set the server up.
Hello friends! Please I need your advice over this issue. I designed a site with asp.net and sql server 2005, the site has about 20 pages. Now, I want to host the site. The question is; how can I host the site so that it can be accessible by everyone within the global world?
And also, I would like to be paid per click performed by visitors(how can I achieve the payment issues?). I have searched many articles but couldn't understand the flow. Any help is welcome!!!
The question is; how can I host the site so that it can be accessible by everyone within the global world?
How "everyone" does it need to be? One usually puts it on a public server (if you don't have a host yet, give it a free try with http://www.aspspider.com/[^]). Anyone with internet could then access it, in theory. In practice, you'll come across things like blacklists that might prevent your site from being shown.
Otekpo Emmanuel wrote:
And also, I would like to be paid per click performed by visitors(how can I achieve the payment issues?).
Paid by "whom"? The visitors of your site? Most people do not pay to access a public site.
The term is often used when talking about advertising on a website. In that case, payments will be made by the company that provides the advertisements. Google for "AdSense" for an example
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
Ok Eddy. What I meant by everyone is that, the site can be visible to everyone so that they can register as members of the chat site. When they are chatting, they will pay per click. For example facebook...
Hi.. When i upgrade any web application and when i click on report/application log i get the below error message. Can any one advise how to solve this problem. I tried by giving full access to "C:\Windows\Temp" folder for "NetWork Service. But its now working for me..
Access is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Access is denied. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I have a dedicated server with windows server 2008 R2. I have installed HyperV & created 1 VM & provided this VM a virtual adapter so it can use internet connectivity of my dedicated server. I am able to do Remote deskop to my VM from Host using Remote Desktop of Host & Remote Desktop in HyperV Host.
Now I want to connect this VM using Remote desktop client of my local laptop, which is outside this dedicated server network. I don't know how to do that. This VM has private lan ip of 192.168.137.130 under my dedicated server static ip. I can remote desktop my dedicated server from laptop using my dedicated server static IP.
What settings I need to do so i can access my VM using remote desktop client?
I see two possibilities:
- Change the network of the virtual machine to your "normal" network (that's what we usually do with our VMWare virtual machines).
- Add a route to the network of the virtual machine.
Change the network of the virtual machine to your "normal" network (that's what we usually do with our VMWare virtual machines).
This solution require each VM have static IP and I am limited to only 5 static IPs. I am going to have 20 Virtual Machine on my dedicated server. I can't afford each unique static ip assign to each vm. This is wrong way of doing it. Are there any way to use static ip of main server to port remote desktop to HyperV VM seprately, rather than assign each static ip to each VM?
Yes, I copy pasted your code, substitutuing the domain name, to he live server - but see my other post in reply to this...
While the certificate is installed on this server (of course) the domain's DNS is handled by a third-party, adn it *seems* as though what is happening is that when the original request comes in, the DNS server is requesting authorisation from the certificate before passing teh request on.... is that how it works? It would explain it, but leave me in a fix...
The DNS server shouldn't be requesting anything from your site. It's simply an address book which maps an entry like www.mydomain.com to an IP address.
From your other post, it sounds like the browser is making the request for https://mydomain.com, and then barfing when it gets a certificate for www.mydomain.com, since they might not be the same site.
Many certificate authorities will issue a certificate which is valid for both www.mydomain.com and mydomain.com, so it might be worth seeing if that's an option. Otherwise, you'll need a spare IP address and a second SSL cert to avoid this error. (You could probably get away with a free cert from StartSSL[^], since you're only securing a redirect to the real site.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Last Visit: 31-Dec-99 18:00 Last Update: 2-Oct-23 10:34