I figured out my problem. It was the UniAdmin administration tool.
For some reason, this particular server was set up to use UD v7.2
instead of UD v7.1. Maybe some Windows update is now making this not
work (I know it worked before), or the version defined in UniAdmin got
changed at my end (possible).
Sorry about the useless bandwidth. :-)
Bill
------------------------------------------------------------------------
Bill Haskett said the following on 10/11/2010 10:29 AM:
David:
The service starts using the local service account and it allows the
service to interact with the desktop. This is true with the other UD
services on all the other dbms servers we have access to.
This particular dbms server runs UD v7.1.9 on a Windows 2K3 R2 system
with SP2 installed. This is a server on a domain, but does not have
any domain service responsibilities. This is true with most of the
dbms servers we have access to.
In the past, whenever I've wanted to test whether a service# is
allowed through firewalls I've always used telnet to access the
service#. This would always alert me to a blocking of the particular
service# (I simply get the "Connecting To xx.xx.xx.xx" message). When
the service is allowed telnet gets through, usually with no message,
and pressing [Enter] drops a line in the DOS window. Depending on the
service, one gets a timeout and disconnect or one simply has to close
the DOS window.
Thanks,
Bill
------------------------------------------------------------------------
David Jordan said the following on 10/10/2010 7:38 PM:
Bill
At one stage in UniVerse, in Service to tick the box to allow the
service to interact with the desktop. If it is a Win2008 server
there are issues with User access Control. Finally I have had a
problem with Win2008 with one of the rpc dlls going missing and had
to copy back that dll.
Regards
David Jordan
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Bill Haskett
Sent: Monday, 11 October 2010 11:19 AM
To: U2 Mail List
Subject: [U2] UniRPC Connection
I have access to multiple UniData servers and connect to these
servers via RDP on Windows. I use UniAdmin to administer the UniData
dbms. On one particular server I last used UniAdmin about four
months ago without any problem. However, now when I try to connect
via UniAdmin I get the message "No RPC Connection active."
Looking on the machine at netstat I see:
C:\Documents and Settings\myuser>netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
.
.
TCP 0.0.0.0:31438 0.0.0.0:0 LISTENING
.
TCP 192.168.20.141:139 0.0.0.0:0 LISTENING
TCP 192.168.20.141:1045 216.52.233.221:443 ESTABLISHED
TCP 192.168.20.141:9823 75.145.23.137:1914 ESTABLISHED
TCP 192.168.20.141:3389 192.168.20.140:56293 ESTABLISHED
TCP 192.168.20.141:31438 75.145.23.137:2739 TIME_WAIT
.
As can be seen, the service is running and my failed attempt to
connect has been noticed. I've rebooted the server and still cannot
connect. I've tried several variations of login credentials to no
avail and am logged in via telnet on port 9823. A look at services
shows that the UD RPC services, the UD Dbms, and the UD Telnet
service are all running.
I can open up a DOS window on my local machine and "telnet
theiraddress 31438" and connect, so I know the router is properly
routing port 31438 to the correct machine.
Does anyone know what I'm missing on my Sunday's sojourn in
troubleshooting hell?
Thanks,
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
