r00ts
asked on
Accesing PHP Camel/Apache server
We have an php server running something called Camel server i think it is part of apache. When acessing via it's IP address it is ok, but we want to access it via it's computer name so it can be accessed on the lan and also via the internet as it seems ISA is blocking it.
Another issue is when it is not part of the domain and connected dirctly to the router it is viewable internally via its IP address, but when added to the domain and given a IP address via the dhcp it can neither be access from IP address or name..
I know this sounds confsing but i really need help with this..sharepoint can be accessed fine over the net via ISA, but the webviewer within sharepoint which points to the php server cannot be displayed...any ideas will be very welcome, or please let me know if you need more info...
Another issue is when it is not part of the domain and connected dirctly to the router it is viewable internally via its IP address, but when added to the domain and given a IP address via the dhcp it can neither be access from IP address or name..
I know this sounds confsing but i really need help with this..sharepoint can be accessed fine over the net via ISA, but the webviewer within sharepoint which points to the php server cannot be displayed...any ideas will be very welcome, or please let me know if you need more info...
Sharepoint has to link to it by name not by IP#. This is in the code of the Sharepoint page.
You have to have Split-DNS so that the same FQDN resolves tot he External IP of the ISa for external users while at the same time it resolves to the Private IP 192.168.1.23 for the Internal Users and the ISA itself. This is obvious when you think about the fact the a link with a Private IP# is meaningless to an External user.
Publishing the Sharepoint site with ISA and Publishing this other thing with t he ISA is two completely separate and independent processes.
You have to have Split-DNS so that the same FQDN resolves tot he External IP of the ISa for external users while at the same time it resolves to the Private IP 192.168.1.23 for the Internal Users and the ISA itself. This is obvious when you think about the fact the a link with a Private IP# is meaningless to an External user.
Publishing the Sharepoint site with ISA and Publishing this other thing with t he ISA is two completely separate and independent processes.
Use a FQDN based on DNS,...do not use a Netbios Name.
ASKER
Thanks pwindell.
So first i should publsih the apache server to ISA, correct? How do I go about implementing the split-DNS? Can you please help me with the steps to implement the above advice, thanks a million
So first i should publsih the apache server to ISA, correct? How do I go about implementing the split-DNS? Can you please help me with the steps to implement the above advice, thanks a million
Have to look at the Split DNS first. It is foundational,..without it nothing else works correctly,..eveything else depends on it..
1. Is you Public Domain Name and your internal Private AD Domain Name spelled the same or spell different?
2. Do these sites involved (sharepoint and the other) both have a Public Name that they are known by out on the Internet?
1. Is you Public Domain Name and your internal Private AD Domain Name spelled the same or spell different?
2. Do these sites involved (sharepoint and the other) both have a Public Name that they are known by out on the Internet?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
php1-1.jpg