Database over LAN difficulties
- From: Michael Soibelman <in-the@xxxxxxxxx>
- Date: Wed, 20 Feb 2008 00:14:57 GMT
LAN consist of 2 machines. Machine#1 'jupiter@localdomain' Eth1->192.168.0.1
Machine#2 'mercury@localdomain' Eth0->192.168.0.2
I can view an Apache index.html page running on mercury from jupiter by
entering 192.168.0.2 in my browser url box.
I can view an Apache index.html page running on jupiter from mercury by
entering 192.168.0.1 in my browser url box.
So I can see either way over the LAN while viewing a remote Apache web page.
This is good. Now comes the next step. I have an Oracle-XE install on the
internal machine (mercury) accessible from mercury @
http://localhost:8090 . As this machine is old and slow I am surprised I
even got it working. It takes about 65 seconds to load up the 'Database
Login' page ! But it does load. Obviously this is not optimal hardware
for the job but at least I can learn a few things. Also, once the login
page loads accessing Oracle through the web interface is a little more
responsive than the initial login page (~12 seconds). So it's usable for
my purpose. However, when I try to load the login page from jupiter throgh
the lan by entering http://192.168.0.2:8090 I eventually get:
An error occurred while loading http://192.168.0.2:8090:
Timeout on server
Connection was to 192.168.0.2 at port 8090
I'm thinking this is due to the long load time. If so how can I increase
the amount of time before I time out trying to load the page ??? Actually,
I just tried again in Firefox and the same thing happened. Firefox tries
for 120 seconds which should be more than enough time. So it probably
isn't a time issue after all. So I think that maybe I need tp open up this
specific port (8090) in the firewall as the default http port (80) is open
but not 8090, which is where oracle is running..
How do I do this with Yast ?? Do I need to open this port on both
machines ? I' looking at the Yast Firewall module and I am at the 'Custom
Rules' pop-up. There are four (4) things to fill in.
1. Source Network
2. Protocol (TCP, UDP, RDC)
3. Destination Port (Optional)
4. Source Port (Optional)
Is this where I add a special rule to allow port 8090 to pass packets ?? On
which machine or on both ??
Am I even correct as to how to enter the url on this machine (jupiter) to
access Oracle on port 8090 on mercury ??
In case you are wondering jupiter is the web facing machine and so yes there
is an eth0 on the external zone using DHCP to get its' address. Eth1, which
is the LAN interface is masquerading and forwarding packets to the internet
so mercury can get out to the web.
P.S. I suppose I can try Wireshark' on mercury to see what's happening with
the packets from jupiter. Probably will just confirm that I need to open
up a port........
.
- Follow-Ups:
- Re: Database over LAN difficulties
- From: Michael Soibelman
- Re: Database over LAN difficulties
- Prev by Date: Re: mouse SPEED this decade?
- Next by Date: Re: mouse SPEED this decade?
- Previous by thread: openSUSE 10.3 install problem
- Next by thread: Re: Database over LAN difficulties
- Index(es):
Relevant Pages
|