A more granular look at security settings within DotNetNuke brings us to a discussion of security ports, the basic components of your website network connection. Read on for an overview. Common Computer Security Port Settings While a security port can refer to either a physical or virtual connection point, the most common use of the phrase “security port” refers to TCP/IP Networking for websites. It allows programs like DotNetNuke to share resources with other software applications without interference. Computers are automatically assigned an IP address for these purposes. Network firewalls can provide additional control over the traffic on a specific port, if necessary. Typical DotNetNuke UsePortNumber Settings In some cases, you may wish to run your website on an alternative port – for example, if you’re providing secure access to a certain group or integrating with another program where users can log in. DotNetNuke’s UserPortNumber settings can be changed from within the AppSettings section of the web.config file. Like all http websites, DotNetNuke runs on port 80 by default. Running on this port is what allows you to send a request to a web page, which will then answer your request and display. In some cases, you may wish to run your website on an alternative port – for example, if you’re providing secure access to a certain group or integrating with another program where users can log in. Instances When You May Use a Different Port Number If you need your DotNetNuke website to run on a different port, the fix is fairly simple. Within the UsePortNumber, select “True.” This will let DotNetNuke know that it should retain the port number and use it to determine the site request. You can follow up with a portal alias, usually in the form of a number tacked onto the end of your existing web address. Still have questions about security port settings for DotNetNuke? contact Clarity today! Find out more about Clarity VenturesSee our Enterprise Web portfolio