Conference orarep::nomahs::odbc_rdb_driver

    Bad Winsock.dll? Ping and telnet don't use winsock. Is the port created
    in UCX? 
    
    The real connect error should be in the client log. This would be a
    real short log so it should be easy to find. I would guess it will tell
    you about the -2003. Hopefully, it will give you a subcode as well...
    
    John

    
    He seems to be having lots of problems installing things and I
    know they have some Novell stuff.  After what you suggested
    and what Renee said in 1301.1 maybe he is installing some
    package with a WINSOCK that is allergic to the MS TCP/IP stack.
    I'm also having him run the SQL/Services IVP to make sure his
    server is cool.  The CLIENT.LOG follows (you were right John,
    it is quite short):
    
    Log file generated by C:\WINDOWS\SYSTEM\SQSAPI32.DLL
    Oracle Sql/Services Version 7.00
    
    WINSOCK ERROR ENTRY
      Connect Ret 0 Err#10061 WSAECONNREFUSED Connection refused
    SQLERRD[0]: 10061
    SQLERRD[1]: 0
    
    ASSOCIATE LEVEL LOG
    ----SQLSRV_RELEASE
    --------SQLSRV_ASSOCIATE ID: 7f0078
    
    Regards,
    rcs
    

>      Connect Ret 0 Err#10061 WSAECONNREFUSED Connection refused

Here's another article for this one:


SYMPTOM:

While attempting to connect to an Oracle Rdb database using the Oracle
ODBC driver for Rdb or a native SQLServices client with a WINSOCK
compliant TCPip implementation fails with the following error:

Connect Ret 0 Err #10061 WSAECONNREFUSED Connection refused [#-2003]


SOLUTION:

Check to see if SQLServices is running by doing a SHOW SYSTEM command
on the server node and looking for the SQLSRV$SERVER process.  If it
is not running, start it by issuing @SYS$STARTUP:SQLSRV$STARTUP at the
VMS DCL prompt.

If the server is running but you still get the error, check the
SQLServices Communications server logfile for a problem binding to
TCPip. To do this, edit SYS$MANAGER:SQLSRV$.LOG and look for

     ERROR: TCP/IP Server activation failed

The line following the error would indicate why the bind failed, for
example,

     %SYSTEM-W-NOSUCHDEV, no such device available

The NOSUCHDEV error is common and indicates UCX was not running  at
the time the server was doing startup.  This can happen if the
SQLServices server was started before UCX, if UCX startup failed, or
if DEC TCPip services for OpenVMS was not installed on the server
node.

A successful bind message would look like:

     TCP/IP Server activated

Another possibility for this error would be if the initial bind to
TCPip was successful but TCPip returned an unrecoverable  error during
subsequent data processing.  In this case, restarting the server  will
usually clear up the problem.  If the problem is intermittant, you may
want to seek additional assistance from your Network Administrator or
your network vendor.


ANALYSIS:

The network returns this error when you unsuccessfully attempt to
bind to the SQLServices server software on the remote system.  Reasons
for this  error to be returned might be that SQLServices was not
running on the remote node, that the server software was not able to
bind to the TCPip port properly at server startup, or that an error
returned by the server network software caused the network bind to
fail.

NOTE: The only supported TCPip interface for SQLServices (OpenVMS) is
DEC TCPip services for OpenVMS (UCX).  Other TCPip implementations may
work if they can emulate UCX but these implementations are
unsupported.


REFERENCE:

[TM] Microsoft MS-DOS is a registered trademark of Microsoft
Corporation.
    

    The connection refused message indicates we got off the PC, went to the
    server and the server refused the connection. Noone was listening on
    that port. 
    
    Either SQLSRV is not bound to TCP/IP or you are going to the wrong
    server node. I have seen cases where customer had duplicate ip address
    and depending on what part of the building they were in, some PCs work
    and some didn't... If SQLServices is binding to Ip OK, watch for dup
    nodes... 
    
    john

    
    Does anybody know about a PC or server-based utility that reports
    the physical Ethernet address back if you do something like PING
    it ?  Duplicate IPs could be dastardly to debug otherwise !
    
    [Thanks for John and Renee both.]
    
    Regards,
    rcs
    

As long as you have TCP/IP installed under W95 or WNT, you should be
able to pull down on the start menu, select Run... and in the
resulting dialog type:

	ping host-name

I just tried it on WNT (4.0) and Win95 and it worked.

Bryan

    Telnet from VMS also resolves the address.
    
    UCX Ping nodename/all also.
    
    /Regina
    
    

    There are a couple of problems where ping doesn't really help. If
    WINSOCK.DLL is broke, pink will not catch it unless they are using a
    Winsock ping. Most ping utilities go in at a different level and don't
    use Winsock at all...
    
    Another issue (and this was the one Richard was looking for) is when
    there is more than one machine with the same IP address. The ping will
    stick to the one in closest proximity. If they have a PC and a VMS
    Server with the same ip address, there is no way to tell which one is
    answering the ping. I just ran into this a couple of weeks ago. 
    
    The symtom would be the connection refused message but it would appear
    SQLSRV was listening to TCP/IP and that TCP/IP was working (because
    ping worked). Some Pcs worked and some didn't. 
    
    The customer had more than one Rdb server system out there and we were
    able to pinpoint the problem just by going to one of the other
    machines. We found that we could connecct to any other server except
    one and some people could get to the bad one but it depended on where
    in the building they were...
    
    Ugly...
    
    John
    
    	Oh, to answer your original question, I don't know of any utilities
    like DECNET TELL in TCP/IP that could help here...
    
    John

    
    A note to prior postings regarding PING: while PING resolves the
    IP address from host name, I was looking to dump the actual
    PHYSICAL ETHERNET ADDRESS (e.g. 08-AD-C7-0A-DA-FC) and NOT the
    IP address (e.g. 128.219.123.42).  Thanks anyway, though ;-)
    
    John: do you know of a WINSOCK PING utility ?
    
    Thanks,
    rcs
    

    
    SQLSRV$.LOG was dying with a "Error, TCP/IP Server activation failed:
    sts = 2312" and "%SYSTEM-W-NOSUCHDEV, no such device available".  I
    checked UCX$DEVICE though and there is a BG0: (and they are using
    UCX V3.3 eco 10).  The IVP passes DECnet, as expected since people
    are using that fine, but dies with "SQLCA: SQLCODE: -2003
    SQLERRD[0]: 61  SQLERRD[2] 0"  and "%SYSTEM?-BADESCAPE, syntax
    error in escape sequence".
    
    The thread has been taken to 2153.0 in SQL_SERVICES.
    
    Regards,
    rcs