Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site not working after changing Port-NumberSite not working after changing Port-Number
Previous
 
Next
New Post
9/1/2009 9:07 AM
 

Hi All.

I know (i found) similar posts but none of them are telling a solution.

Here is what i have and what i did

My 4.9.4. site is running on a WinServer 2003 and i want to setup a new 5.1.1 one. As version 5 cannot run at aanother port then 80 i wanted to change my old one to 82.

- In the IIS-Manager i changed the port number to 82 for this website
- in the web-config i set UsePortNumber to true
- i changed the entry in the portal-alias-table to xxx:82

But this might not be all, my site is not cumming up. What did i forget?

Thanks in advance

Kai

 
New Post
9/1/2009 10:22 AM
 

Is port Number82 open in the firewall?  Is the site started in IIS?  Are you adding the port on the URL, as in http://www.sample.com:82/?

And what exactly does not coming up mean?  Errors?  Log entries?

Jeff

 
New Post
9/1/2009 10:46 AM
 

No, even in my own LAN here at home it's not working. And in the LAN there is no FW and the Windows Firewall is not running on my server as i have one for any connections from / to outside.
Yes, the site shows as RUNNING
Yes, i add the port-no

And here is the result:

When accessing it from another PC in the LAN i get an SERVER ERROR IN '/' APPLICATION

When accessing it directly on the server via http://localhost:82 i get a REQUEST TIMED OUT.

When i switch the above named 3 points back to port 80 everything is running fine, smooth and fast.

So, what else could be the reason?

 
New Post
9/1/2009 1:53 PM
 

Have you tried a different port number, such as 8080?  What OS is this?  Anything else possibly using port 82?  Netstat can help you find ports being listened on:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netstat.mspx

I ask because there are a number of trojans that can use port 82.

Jeff

 
New Post
9/21/2009 4:07 PM
 

Sorry for being late, i had some other projects to close first.

However, i changed to port 8080 and got the same problems.

Then i added executionTimeout="36000" into the httpRuntimehttpRuntime section of the web.config and it is working.

Well, allthough it fixed my prob, i do not understand why the timeout must be higher when running something different then port 80.

Thanks anyway.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site not working after changing Port-NumberSite not working after changing Port-Number


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out