>>>>>Thanks, IIS and ASP.NET are already installed. It's the actual creation of the client Web Site that I need help with. So far I've managed to muddle through by adding a virtual directory to the default web site and giving it th epath of where I've put my files. I then right clicked on the the virtual directory and chose convert to application.
>>>>>
>>>>>However, my default page will load up in the browser but not showing the image file that is on it and my login does not work. Is there any more configuration necessary?
>>>>>
>>>>>< later >
>>>>>
>>>>>I've got it to run. I had not given sufficient rights to the user to access the database. So far it seems OK.
>>>>
>>>>I usually remove the default Web site at first, so as its related application pools. I prefer to create something from scratch that I can control.
>>>>
>>>>Your message stated an issue with the image but you said you resolved it from provided related rights towards the database. So, I assume there was a few things to fix. Good to hear you made it work.
>>>
>>>It's weird. The first time I access the site from a browser, the image is not displayed. As soon as I log in the image is visible. If I log out and start again, the image is still visible.
>>
>>Sounds as if the image is not being loaded soon enough for display on the page (or that loading the image requires IIS authentication supplied by the login). Probably showing up subsequently since it has been cached by the browser.
>>
>>Best way to update the site now that you have it running might be to use the ASP.NET 'Publish' option - reduces hic-cups that can occur if you simple overwrite existing files.....
>
>Not sure if that can work as I do not have direct access to the server since it's on an internal network. I only access it by using TeamViewer. Is that option still possible in this scenario?

Don't think so. You'd need a url or an ip address for the server.