Title: | TeamLinks for Windows |
Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
Created: | Mon Aug 28 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2238 |
Total number of notes: | 9650 |
Can anyone shed any light on the following error. WHen the customer : Chooses Teamlinks client icon, (v2.7) Brings up logon box. Chooses local mailbox with local username and password. Click OK & File cabinet service is not running or is not available. Or file cabinet service is configured incorrectly. I have had the customer create a CFC log and the following error was found. CFCLOG has produced the error "socket()=10047" Addr family not supported by prot family. He says that outside of Teamlinks everything works fine, he can Telnet and PING nodes both on and offsite without fault. He also has no other similar problems with any other PC on site. Note: Pathworks loads only the TCP/IP stack, no LAT or DECnet. and LANMANAGER 2.2 is loaded into windows. Can anyone offer any advice ??
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2104.1 | Would you verify the transport selected | MANANA::FLANAGAN | Thu Apr 03 1997 11:30 | 6 | |
Can you have the customer verify what network transport is selected and also verify the they are not using a startup configuration which overrides it. Sounds like they might have selected DECnet instead of TCP/IP using Window Sockets. / Peter | |||||
2104.2 | WINSOCK.DLL | KERNEL::BURDENI | Fri Apr 04 1997 05:13 | 8 | |
Thanks for the reply, the problem was caused by a duplicate dll, because there was another older version of WINSOCK.DLL in the windows directory. The older file was renamed (in the windows directory) and then everything came to life. Thanks for the pointers, Ivan. |