| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2130.1 | Is RMU_DISP up and running? | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Thu Jan 23 1997 11:21 | 15 |
| 2130.2 | Are the clients finding the wrong winsock.dll? | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Fri Jan 24 1997 15:15 | 16 |
| Hi again,
The truth this time maybe. Your original note does say you were able to
connect via TCP/IP from the RMU clients, so the RMU dispatcher is probably up
and running.
The SQL/Services clients (this includes ODBC) link in the DECnet static
library, so they don't look for a DECnet DLL at runtime. The RMU clients
dynamically load WINSOCK.DLL. This is why your ODBC driver is able to
connect via DECnet and your RMU clients aren't.
Is the WINSOCK.DLL that the clients are finding the Pathworks DLL? Can you
connect to the server node with DECnet on this system via another DECnet tool
(an NCP loop or NFT copy or something)?
Sue
|
| 2130.3 | WINSOCK.DLL ? | CHSR36::JSUBRI | Focus on Open/Rdb++ | Tue Jan 28 1997 04:03 | 4 |
| Everything works perferctlly with DECnet and IP, just the DBApack still
fails, the WINSOCK.DLL on 3.11 is dated 21-NOV-94 !!!
Which one are you running ?
|
| 2130.4 | Wrong winsock.dll found for DECnet | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Wed Jan 29 1997 13:32 | 11 |
| My guess is that your DBAPack clients are finding the Windows 3.11
WINSOCK.DLL first and not the Pathworks WINSOCK.DLL. Only the Pathworks
WINSOCK.DLL has DECnet support.
It may be that the DECnet tools you've tried don't use the WINSOCK interface.
ODBC and SQL/Services do not use the WINSOCK interface - but the other
DBAPack clients do use the WINSOCK interface for DECnet.
(My WINSOCK.DLL is dated 2-22-95)
Sue
|
| 2130.5 | Where do I get a new WINSOCK.DLL? | chsr38.ch.oracle.com::ROHR | The Packers did it! | Thu Jan 30 1997 11:07 | 4 |
| Where does WINSOCK.DLL come from? Where can I or the customer get a
newer version?
/Regina
|
| 2130.6 | From your network provider | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Thu Jan 30 1997 14:18 | 6 |
| Hi Regina,
Pathworks ships a WINSOCK.DLL that provides both DECnet and TCP/IP support.
Other TCP vendors (including Microsoft) provide their own WINSOCK.DLLs.
Sue
|
| 2130.7 | Who to decipher socket errors? | chsr38.ch.oracle.com::ROHR | The Packers did it! | Fri Jan 31 1997 02:27 | 9 |
| Thanks Sue.
Is there any way to decipher what this means:
socket error 0x283f
Thanks,
Regina
|
| 2130.8 | | UKVMS3::RVIRR | High cost of ownership... | Fri Mar 14 1997 11:15 | 12 |
| I spoke to the customer in .0. They have PW5.1 and a TCP/IP stack from
Microsoft. Looking at the PC they only have one WINSOCK.DLL in the windows dir.
If its the PW WINSOCK then it should be in the PW dir. I assume PW is trying to
find WINSOCK.DLL, cant, and then is checking the path and hence finding the MS
version.
Does anyone know what interface ODBC and SQL/Services use (PWSOCK)?
Cheers,
Rich.
|