I am having an issue with my server switching from using the IP address to machine name.
Yesterday, I went into IIS 7 and created a new application under the Default Web Site. I gave it an alias (i.e. forschung) and gave it the Physical Path (a bin-debug file in the Adobe Flash Builder 4.6 folder). I did this as per suggestion on the GIS API documentation. Then, I changed the Flex project'S Output folder to bin-debug and Output folder to http:///forschung. I was able to successfully run the project in Google Chrome, but was experincing errors in Firefox. After changing the REST service paths to use the machine name (instead of the IP address), I no longer had issues in Firefox. However, now it appears that my REST services, and my other applications, need to be changed to use the machine name, but I want to keep using the IP address since changing the services and applications would take a lot of time. What do I need to do to use the IP address again?
I am using IIS 7 on a Windows Server Standard 2008 machine.
The issue was a previously created Website which was competeing with the Default Web Site. As soon as the competing website was removed, everything was fixed.
Related
How to open a published webform site from within visual studio code. opening and running the default.aspx in browser locally
The site is published by Visual Studio 2019 ( not Visual Studio Code ) to local folder, I want to open and run that published site from another computer having Visual Studio Code only.
Well, to run, show and display a web site, you need to have a web server installed, and then up and running on that computer.
You then need to configure the web server, and what folder or where the web site is published to. However, for reasons of security, often the folders that the web site can see (or use) is VERY restricted. I mean, do you want the whole world messing around in folders on that computer? (not!!!!).
You then need to open up the fire walls, and set rules to allow external use of that given computer.
Now, it turns out, that Visual Studio is able to "debug + launch" your web site during development. This works be having installed a light weight (stripped down) version of a Web server.
So, VS uses what is called IIS Express. It does have VERY high degree of compatibility with IIS
So full version = IIS (Internet Information Services)
Light version = IIS (Internet Information Services Express).
So then, the REAL question is can you setup + use IIS Express (that is ALREADY installed on your computer as a result of installing VS)?
The answer is yes, but it is REALLY but REALLY painfull.
And the reason why? Well, to run + launch IIS express for JUST you the developer, then things like security, rights policies, file access, is http and https etc. setup? Well that is a HUGE FAT BOOK of reading and a HUGE FAT BOOK of massive amounts of configuring required to setup + run a whole web server.
I mean, you do have web.config. But the sheer mass of options available is quite a challenge to setup.
And IIS express does NOT have the main setup and configuring screens included.
So, for hitting f5 to run from Visual Studio? great!!!
But, you need screens like this:
And from above, we have a LOT of stuff:
So, the problem is that IIS Express does NOT include the above management screens.
So, this means that YOU HAVE to edit web config and other config files that are required to run + setup IIS.
Now, to be fair, you could just run with the SAME defaults that VS uses when you hit F5 to run. But the configuring of the web site can be a hassile. (for example, did and do you know WHERE to set the IP address of the web site?
When you run local, then VS uses "localhost". But for anyone else on the network, they now have to use that computers IP address, and then YOU must setup the web server to accept requests to that IP address. And you don't even have to use + give the web server the same IP address as the computer hosting IIS.
So, you CAN use IIS Express, but it going to be panful beyond ANY thing but using IIS Express for debugging your web site on the SAME computer running VS. Remember when running IIS on the SAME developer computer, then you are the "owner" or what we call 'super user' of your OWN computer. But, I can't just start opening files and using YOUR computer right now, can I? (see the difference!!! - allowing OHTERS to use your computer is a really big deal.
But, yes, you can get IIS Express to work. it just that IIS Express is MISSING all the above management screens. (and that above screen shot shows that each one of those icons when chosen is a "big maze" of options.
To get this to work can be done.
I don't have a good reference, and you have to google it, and then with a pot of coffee, read away, since without the configing menus and systems above, you find this to be difficult.
Here is one such article on how to do this:
https://blogs.blackmarble.co.uk/rfennell/2011/03/22/how-to-expose-iis-express-to-external-network-connections-and-use-a-non-self-signed-certificate/#:~:text=%20How%20to%20expose%20IIS%20Express%20to%20external,You%20now%20need%20to%20just%20start...%20More%20
I need some help here. I have a website in asp.net and a database in my local machine, and I'm setting up a testing enviroment so that I can access the site and the database from outside the local network and make tests. I want to set up a server in my windows 10 using IIS to publish the site, and I already know how to publish a asp.net site through Visual Studio and IIS manager. My only issue now is to make it available outside my network. Is there a easier way of doing this than having to buy a domain and a hosting service?
You could create a free azure app:
https://azure.microsoft.com/en-gb/pricing/calculator/#app-service1
You can run a single website (asp.net) and not need to register a domain it will give you a link publicly available on the web.
Whoops, sorry, the database wouldn't be free however the basic version is not expensive. This is in fact what I run for my own test cases.
In order to host at home, you would need to ensure that you had a static IP address and that port 80 was opened to allow traffic in and out.
https://serverfault.com/questions/1058/how-do-i-set-up-a-web-server-out-of-my-home
I am currently trying to run my visual studio web project on a blackberry sim.
I can access my machine's IIS page from the IP address, (so when I type in 10.x.x.x, it takes me to a page for IIS).
My question is how do I access the localhost page that visual studio is running, so the page that would normally have the home Ip address in browser.
I am guessing is is (machine IP)/(something), but I dont know what the something is.
Thanks
Visual Studio often times runs testing server when you test your code from inside VS. When VS opens a new browser window and shows you the running application you should see something like:
localhost:####/WebProject
That is the location of your files on separate port (whatever is in the place of ####). However, most likely this testing server will be set to not allow remote access. What I would suggest is creating a virtual directory in iis so that you can go to 10.x.x.x/WebProject and have that point to the directory that your VS project is in.
Instructions on creating a virtual directory: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/5adfcce1-030d-45b8-997c-bdbfa08ea459.mspx?mfr=true
Webdeploy is an alternative to WebDav, FTP, and FrontPage extensions. It also acts as an alternative to DFS for replicating websites. I found instructions for configuring Windows 2008, but I'm unclear how to set up 2003 especially when multiple sites / IP Addresses are present.
It is possible to install Web Deploy Tool 1.1 on Windows 2003 for IIS6. Generally this tool is used for synchronization between remote/local sources. You can refer to the following article about how to use Web Deploy Tool 1.1 on Windows Server 2003:
Synchronize IIS 6.0 Web Sites
http://learn.iis.net/page.aspx/445/synchronize-iis-60-web-sites/
However, it's not possible to use this tool to enable publishing from Visual Studio 2010 to the webserver. The reason is that this method relies on ‘Web Management Service’, which is newly introduced in IIS 7. This service can be used when there are some users delegated to manage certain sites or applications on the server. However, this service does not exist on Windows Server 2003.
IIS Web Management Service (WMSvc):
http://technet.microsoft.com/en-us/library/cc735010(WS.10).aspx
I use WebDeploy (MSDeploy) on 2003 servers to ensure content, IP addresses, certificates, etc remain the same across a MS NLB cluster. I also created a batch file to automate most of the different functions based on what I want to do (Full Server replication, single website, content only). Here are my notes on using the tool that I posted on my company's internal blog:
MSDeploy (http://www.iis.net/download/webdeploy) is a tool developed by Microsoft to make migrating, deploying, copying, and backing up websites easier. It was developed for IIS 7, but most features work in IIS 6. It can also be used to move a website from IIS 6 to 7 although I have not tested this. Some things to keep in mind when using MSDeploy are:
MSDeploy must be installed on both source and destination servers
The “Web Deployment Agent Service” must be running on both source and destination servers
Application Pools for the website must be created on the destination server before using MSDeploy or it will fail. I think this is fixed in IIS 7, but I am not 100% sure
When deploying a website, MSDeploy will attempt to put the files in exactly the same path on the destination server. If the path doesn’t exist on the destination server (like if the source path is D:\website and the destination server doesn’t have a D: drive it will fail)
The migrated website will have the exact same configuration as it did on the source IIS server. Some settings you might want to change after the move/copy are the website IP address and home directory path. You will need to make those changes manually on the destination server.
The metabase keys will need to be edited on a per-server basis since they are unique for each server (unless you created the sites using MSDeploy, then it uses the same key string across servers). As more and more sites get deployed with MSDeploy, the key strings will become universal for all servers since the metabase keys will be the same on all servers.
I have an ASP.NET app that works fine on my windows XP dev machine but doesn't work when deployed to a Windows 2008 with IIS7. The app uses SmtpDeliveryMethod.PickupDirectoryFromIis and gives an error when I try to send an email from the app on IIS7 (an SmtpException with the message "cannot get iis pickup directory"). I use the same settings on both the dev machine and the server.
Any help would be really appreciated ...
It turned out to be a permissions problem but not with the pickup directory, actually with the metabase (SMTP settings are still saved in the metabase in IIS7)
I came across this forum thread, Cannot get IIS pickup directory. NEED HELP, on IIS.net forums website then followed what was mentioned in the posts, downloaded and installed the metabase explorer tool (you have to download IIS6 resource kit to get it) then gave read permissions to my custom user (as indicated in one of the posts) on the LS, SMTPSvc and SMTPSvc/1 keys and it worked. For some unknown reason if you only give permissions to the smptSvc key it doesn't work.
I think the problem could be with trust levels.
Because in medium trust you can only write to your application's directory (or any directory below that). And if the PickUp folder which you specified is not in your application's directory AND the application is running under medium trust (not full trust), then you can't write to the PickUp folder.
You may send directly to the SMTP server without using a pickup directory.
You need to specify the Pickup directory first. Here's a guide on how to do it.
Also it's not a good idea to compare your IIS 5.1 on an XP box against the one on your Windows Server 2008 (IIS 7), since besides the obvious version difference a lot of features have changed a lot. Specially the smtp server, for instance there's no such feature in Vista.