Installing Sugar CRM on XP Pro

**bcampbell** · 2006-06-12, 06:25 PM

I have installed SugarCRM open source on my computer running XP Pro.

The installation guide stated to copy the Sugar files to: C:\Inetpub\wwwroot\
Then to unzip the files. When I did this, the program installed under C:\Program Files\sugarcrm-4.2.0c/

When I run the program it comes up fine from my machine, but how do i access it from other machines in our office network?

Here is what the installation Summary listed:

Installation Summary
------------------------

SugarCRM was installed with the following settings

Installation directory: C:\Program Files\sugarcrm-4.2.0c/
Apache HTTP port: 81
Apache HTTPS port: 444
MySQL port: 3306

On Linux and OSX systems:
To start SugarCRM: C:\Program Files\sugarcrm-4.2.0c/sugarctl.sh start
To stop SugarCRM: C:\Program Files\sugarcrm-4.2.0c/sugarctl.sh stop

To access SugarCRM, point your browser to:
http://127.0.0.1:81/sugarcrm/
To access SugarCRM with SSL, point your browser to:
https://127.0.0.1:444/sugarcrm/

Can anybody help point me in the right direction.

TIA

Bruce

**stevec** · 2006-06-13, 11:07 AM

Hi,

installing to "C:\Inetpub\wwwroot\" is if you are using Microsofts IIS web server.

You're using Apache (the open source webserver) - I guess from some kind of packaged installation (spike, bitrock etc) .

Sounds like all is OK though.

If you can see it from your machine - then it should be accessible from the rest of the network. If you're running it as 127.0.0.1 then that's a default IP address that always means 'this machine' - so you'll need to find your 'real' IP address.

To access SugarCRM, point your browser to:
http://127.0.0.1:81/sugarcrm/
To access SugarCRM with SSL, point your browser to:
https://127.0.0.1:444/sugarcrm/

This is just for local access. To find your 'real' IP address, open a command prompt and type ipconfig and substitute that for 127.0.0.1 on the other users machines.

You'll also need to be aware that if you have a firewall installed on your PC - that might stop people accessing it. if that happens, you'll need to configure your firewall to allow access to the webserver from the local network.