*This message was transferred with a trial version of CommuniGate(tm) Pro*
Ok, I am stupid, and I'll admit it if it helps anyone else.
I have been looking for DNS or host misconfigurations until my eyes bled,
but the answer to the problem below was written in the FAQ.
The reason why itools did not run properly on my OS X server was that I had
not disabled performance cache in Apple's mail server's default host using
Apple's admin tools. I thought it was enouch to just stop Apple's Apache...
Now I just stopped Tenons Apache, started Apple's using Server Admin. Turned
off performance cache in my default host. Stopped Apple's Apache, and
restarted Tenon's.
/Peter
> Hi Eric,
>
> I am still having problems with itools Virtual hosts on my OS X Server.
>
> I installed itools on a computer running OS X 10.1.5 client and it works as I
> would expect. By default the server's name is 127.0.0.1 and there is also a
> virual host already created called 127.0.0.1.
> I can connect to the address 127.0.0.1 but that's all. Then I enter the
> server's ip address in the server alias field and I can also after that enter
> the ip number in the browsers address field and connect to the server. It
> works just as I am used to running Apache on my OS X server. I am only able to
> make connections to 127.0.0.1. The server's ip number does not work, neither
> do virtual hosts like www2.hampusmedia.com (which are properly pointed to the
> same server in my DNS settings).
>
> When I uninstall iTools I can connect to my machine using Explorer and the
> addresses 127.0.0.1 and 192.168.1.2 which is the servers ip. When I have
> iTools installed I can only access the server using the address 127.0.0.1
>
> Since that is the address for localhost I can only access the machine from the
> server itself, not fron any other computer (since the cilent connects to it
> self then).
>
> Remote http request to our domain name are directed by our router to the
> server, and it answers fine as long as iTools is not installed. After
> installing iTools the server is not answering on port 80. (Since it only
> accepts request to the localhost ip.
>
> I have turned off the web server in Apples Server admin as your FAQ suggests,
> and deselected the option to start the webserver at startup. The webserver is
> running, so does itools admin server.
>
> I use itools DNS services and they look fine. Nslookups and dig show ackurate
> information.
>
> I guess that there is a conflict in the server's old settings and those that
> itools use that causes this. I am not a command line guru, but I'll manage to
> edit the necessary files using Pico or Vi if you give me instruktions.
>
> Hope you have a solution to this since it is important for me to make this
> work.
>
> Best regards
>
> Peter Hampus
On 8/1/02 12:57 AM, "Erik Lotspeich" <erik@xxxxxxxxx> wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> On Thu, 1 Aug 2002, Peter Hampus wrote:
>
>> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>> Hi Eric and thanks for your reply.
>>
>> On 8/1/02 12:15 AM, "Erik Lotspeich" <erik@xxxxxxxxx> wrote:
>>
>>> Peter,
>>>
>>> Did when you say that your "server ... no longer accepts incoming
>>> connections from outside..." do you mean that it stops accepting
>>> connections from Timbuktu, ssh, or web service?
>>
>> I can ssh to the server, but I can no longer access it via Timbuktu or http
>> on port 80 (port 8010 for example works fine since it is what I use for
>> Communigate pro administration. (Is it possible that Communigate messes
>> something up, because I installed Communigate pro shortly after installing
>> iTools?
>
> Peter,
>
> I do not know what ports Timbuktu uses for is communications. It may be
> possible there is a port conflict with Communigate.
>
>>>
>>>> I have used iTools to set up Bind and it seems to work ok, but some times
>>>> the server does not recognize its own ip-number. Starting server admin
>>>> gives
>>>> me the following address to the server: 0.0.0.0, but after reboot the ip
>>>> number 192.168.1.2 is pre written in server admin.
>>>
>>> On your server running iTools (and doing DNS), is the DNS Server setting
>>> in the Network section of the control panel set to the IP address of your
>>> server?
>>
>> No I used 120.0.0.1 as the first DNS server. After that I listed those from
>> my ISP. When putting my servers ip number there it no longer works. (But
>> doing a reverse lookup for 192.168.1.2 which is my servers ip number shows
>> the server's domain name so it seems to work.)
>
> The correct configuration is for your computer's IP to be in the DNS
> Server field since you're trying to use iTools Bind for DNS. If you don't
> enter your server IP, you're not using iTools Bind.
>
>>>>
>>> Your use of the IP address 192.168.x.x scares me. These addresses are
>>> reserved for internal network use and will not work on the Internet. Your
>>> use of the loopback IP 127.0.0.1 in the above config file is also
>>> incorrect.
>>>
>>> I'm not sure what you're trying to do, but you would be more successful
>>> using "real" IP addresses that have an entry in your DNS server. To make
>>> sure that Apache (and the Admin Server) look for the most up-to-date DNS
>>> records, make sure that your computer is pointed to itself for DNS
>>> (explained above).
>>>
>>
>>
>> What I am trying to do is getting the server to accept http requests for the
>> domain name "mydomain.com" which points to our public ip where the router
>> points it to our server which has ip number 192.168.1.2, which in turn is
>> called mydomain.com in my DNS settings.
>
> What you're trying to do is set up an internal DNS server.
>
>>
>> The reason I tried to add 192.168.1.2 as a virtual domain is that I thought
>> that since it was called "mydomain.com2 in my DNS setup, it would work.
>> Adding a virtual domain called mydomain.com does not help either.
>
> Make sure that Bind is running by checking the Server Controls section of
> the Admin Server. Type "nslookup" on the command line to make sure that
> you can access the Bind that resides on the same server (this will take
> advantage of the DNS Server setting in your control panel, so make sure
> that's right first.
>
> Type "mydomain.com" at the prompt and make sure that it resolves.
>
> Erik.
---------
---------
Tenon Intersystems' iTools Mailing List
To unsubscribe: send
mailto://itools-request@xxxxxxxxxxxxxxx
with the subject: unsubscribe
Find searchable mailin list archives at:
http://itools.blackpepper.co.
|
