1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Trouble with NAT

Discussion in 'Sitebuilder 3.2 for Windows' started by askar, Feb 5, 2007.

  1. askar

    askar Guest

    Is any one using sitebuilder behind NAT?

    I am having problem as some of place it showitng internal ip to public like to view trail site etc.

    Can any one help how to fix it?

  2. askar

    askar Guest

    no one using it behind NAT?

    please help if any one using behind firwall.

  3. Alex Klimov

    Alex Klimov Guest

  4. askar

    askar Guest

    Thanks Alex,

    I am going to look for FTP but from site wizard I am having problem too. its working fine but on last step before publishing it searching internal IP and not finding it and failed to view the page and publishing trail site it also adding internal IP to view trail published site and again failed as internal IP.

    I found below KB on swsoft but really dont understand exactly what is binding and how to modify it.

    I will be very helpfull if you clear what is binding and how to chagne it.

    right now I have dadicated IP for site builder on port 80 and no header defined.

    I appriciate your help in this regard.

  5. Dmitry Frantsev

    Dmitry Frantsev Golden Pleskian

    Sep 19, 2005
    Likes Received:
    Did you find [Install dir]\Hosting Srevice\bin\HostingService.exe.config file on your server? If so please open it in some text editor (notepad or something like this) and find follwing section:

    <add key="PreconfiguredUrl" value="http://localhost/wsb/sbpreview"/>

    As you can see it is commented with <!--........--> symbols. Try to replace this section with following one:

    <add key="PreconfiguredUrl"
    value="http://yourserver.com:80/Sites" />

    http://yourserver.com - it can be your server name (which should be resolved correctly) or external IP address.
    After applying changes you need to restart Sitebuilder's services:

    net stop SBPreviewHost
    net stop SBUpdater
    net start SBPreviewHost
    net start SBUpdater
    Restart Sitebuilder site's application pool