Re: Access Error

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.

-- 
Erik Lotspeich                          Lead Engineer
Tenon Intersystems                      erik@xxxxxxxxx
1123 Chapala Street Ste 200             805-963-6983
Santa Barbara, CA 93101-3142            http://www.tenon.com/

---------                                
---------
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.