Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Remote connection to Oracle XE fails.
Thanks to some excellent help here, I've had no problem setting up Oracle XE
& working with it locally (on HP Pro). Now I am trying to connect to it
remotely.
I have installed Oracle Database XE Client on the remote (XP Home) computer
and followed the instructions on:
http://download-west.oracle.com/docs/cd/B25329_01/doc/install.102/b25143/toc.htm#BABFEDEI
and have a OracleDatabaseXEClientInstall.log file which looks ok, though I
didn't look through all 8400 lines of it!
I am then trying to configure the connection to Oracle Database XE Server, using the Oracle Database Express Edition 2 Day DBA: http://download-west.oracle.com/docs/cd/B25329_01/doc/admin.102/b25107/connecting.htm#CEGIGEIJ
I have confirmed that I can ping the Oracle1 server using either the IP address or server name:
>ping 192.168.101.45
Pinging 192.168.101.45 with 32 bytes of data:
Reply from 192.168.101.45: bytes=32 time<1ms TTL=128
>ping Oracle1
Pinging Oracle1 [192.168.101.45] with 32 bytes of data:
Reply from 192.168.101.45: bytes=32 time<1ms TTL=128
Now I am trying to do a remote connection, but having no luck at all:
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Mar 27 20:05:51 2006 Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect system/opswd_at_192.168.101.45
ERROR:
ORA-12170: TNS:Connect timeout occurred
SQL> connect system/opswd_at_Oracle1
ERROR:
ORA-12170: TNS:Connect timeout occurred
Looking through the documentation I see "On the Windows platform, environment variables are stored in the Windows registry, and are automatically set for you. You need not take any action involving environment variables before initiating a database connection.", so I don't see any problem there, nor can I see any more settings on the client side.
Trying to access the server remotely through the browser using the URL:
http://192.168.0.45:8080/apex
also doesn't work - comes up with "Cannot find server or DNS Error".
I have enabled the "Available from local server and remote clients" radio
button on the server side.
Are there any more checks that I can do to narrow down the problem? Do I have to set anything else up on the server such as IIS or something similar? I'm pretty sure I have followed all the steps.
Thanks,
Dave Received on Mon Mar 27 2006 - 06:41:04 CST