From: Tony Williams 

Firewall problem? Might be worth checking what port is the client machine
trying to use and taking a look at the logs on the server and 6509.

--
Tony

Ellen K. wrote:
> Hi all,
>
> We have standardized on Hyperion as our reporting tool.  So far I have
> only set up a couple of Access databases as data sources for it.  Now
> there is a request to report off our eOn (telephony management) SQL
> Server database using Hyperion.  The eOn SQL Server box is in a
> workgroup that is not part of the rest of our domain.  (We only have one
> domain because we don't have a "forest", whatever that means.)  It is
> behind a router owned by eOn along with a PBX and some other stuff.
>
> Setting up a data source for Hyperion requires creating a special data
> source file called an .oce on the box where the Hyperion fat client
> (required for most administrative tasks) resides, and also setting up a
> different special data source file called a .das on the server where the
> Hyperion services run.  (The analysts and end-users do not have the fat
> client, their access is web-based.)
>
> I have to register the eOn SQL Server by using the IP address and SQL
> Server authentication.  (I was told that I can't use Windows
> authentication because it is not in the domain.)   From the box on which
> the Hyperion fat client resides, I cannot register the eOn SQL Server.
> The error message is "timeout expired".  Tracerting
indicates there are
> no intermediate hops when attempting to connect from this VLAN.  From my
> desktop, which is on a different VLAN, I can connect to and register it.
> This trip includes one hop at our 6509.  From one of my servers which is
> on the same VLAN as the fat-client box, I am able to connect and
> register.   On the fat-client box I tried deleting and re-registering
> another SQL Server and there was no problem.
>
> The IP address I have to use to connect to the eOn SQL Server is *NOT*
> the actual IP address of the box it resides on, but rather the eOn
> router, which translates it to the address of the server.  We have no
> control over this, eOn creates this setup.  I'm not sure how it knows
> which of the devices behind it a given message is for.
>
> Ideas?
>
>

--- BBBS/NT v4.01 Flag-5