PDA

View Full Version : Web Interface Issue


joshie4ever
May 5th, 2011, 06:15 PM
So here's what I am dealing with. I will try to explain this the best way possible and I apoligize if it sounds like ramble but I will do my best to clean it up after I am finished.


I am trying to get my web interface to work. I did work at one point but I have been unable to get it to work since then.

CRM Server -- 192.168.1.201
My WAN IP is DHCP so I was trying to use a dyndns service to give me a static name.
***.dyndns.org example

My CRM server is out in the DMZ past the router.

Current Settings :

[Pref]
ServerPort=4961
TimeOutAmount=60
ServerIP=192.168.1.201


Internally : If I point my browser to "http://192.168.1.201:4961" , I get "http://192.168.1.201:4961/files/cmtcustlogin.html" and I can access the web interface.

Externally: If I point my browser directly to my CURRENT dynamic IP address. 123.456.78.90:4961 I reach this "http://123.456.78.90:4961/EXEC/0/1by45161yyxrj110bz8a20kmgqxi" then " http://192.168.1.201:4961/files/cmtcustlogin.html" then "The page can not be displayed"


Ok I understand that it is trying to use the internal IP address for the server and that wont work so lets edit it to use my outside IP address and see what happens (will get to the DYNDNS in a second....)

Change to :
[Pref]
ServerPort=4961
TimeOutAmount=60
ServerIP=123.456.78.90

Server Restart...


Internal : http://192.168.1.201:4961 gets "http://192.168.1.201:4961/EXEC/0/0su1co00rc91jy1cql0gs1nciqof" then "http://123.456.78.90:4961/files/cmtcustlogin.html" then " Page can not be displayed.

External : http://123.456.78.90:4961 gets "http://123.456.78.90:4961/files/cmtcustlogin.html" then CommitCRM Web Server


----> Great so is the server designed to work only one way or do I need to change some forwarding settings inside my router ? I do necessarily need to reach the web interface internally but it would be nice to have it just because and if I need to help an employee figure out a problem....


If we change it to the dyndns address....

Change to:
[Pref]
ServerPort=4961
TimeOutAmount=60
ServerIP=***.dyndns.org:4961

Server Restart....


Internal: Page can not be reached

External: CommitCRM CRM login page.

So what gives? Can I not set this up to work both ways ?

lpopejoy
May 6th, 2011, 03:54 AM
If you have a server inside your network, set a DNS A record that is the same as the A record that you use to access Commit, then set that in your CommitCRM preferences. For example, use an A record called office.yourcompany.com - inside your network, that resolves to your private server IP address. Then go to your public dns server for your domain (wherever that is hosted) and set a CNAME for office.your domain.com that points to ***.dyndns.org. Then you should be able to use the same record to access the CommitCRM server from the inside and outside. Make sense?