[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

1192.0. "Socket error 1001 installing HUBwatch in Novell LAN" by CGOOA::VAOP21::SZOSTAK (NIS TEAM VANCOUVER) Wed Jul 06 1994 16:08

I have been trying to install HUBwatch V T2.0.1 into Novell 3.12 IPX LAN.
HUBwatch is being installed onto a IPX only client and I have been
successful in binding the IP stack with IPX over ODI.  The boot process
shows no errors.  I am able to ping the HUB successfully but when I start
up Windows and click on the HUBwatch icon I get the Following Error
"Unable to create Socket error 1001"

The following some info that might be usefull.

Autoexec.bat file calls the following:

LSL
EXP16ODI    -->  INTEL NIC Driver
IPXODI
SCHK.EXE /NDIS
DLLODI.EXE
TCPIP
TN
BAPI
NETX

net.cfg file contains the following:

preferred server = ADMINSERVER
cache buffer = 0
file handles = 100

Link Support
  Max boards	4
  Mempool	4096
  Buffers	8

Link Driver EXP16ODI
  Frame Ethernet 802.3
  Frame Ethernet II
  Frame Ethernet 802.2
  Frame Ethernet SNAP
  Protocol IP  0800 ETHERNET_II
  Protocol ARP 0806 ETHERNET_II
  int 3
  port 300

Protocol TCPIP
  bind exp16odi
  ip address  192.192.192.10
  ip netmask  255.255.255.0
  tcp sockets 8
  udp sockets 8
  raw sockets 1
  nd sessions 4
  nd commands 8
  nd_adapter  0

As I indicated before the network load shows no errors, I have tried this
configuration on my laptop using the customer net.cfg, changing the Link
Driver to support the XIRCOM NIC I have in the laptop.  The Laptop booted
fine and I was able to connect to the hub.

Any suggestions!!!

T.R Title User Personal
Name Date Lines

1192.1 One solution to socket error problem CUJO::HILL Dan Hill-NetMgtConsult-Denver-553-3624 Thu Aug 11 1994 11:28 16

T.R	Title	User	Personal Name	Date	Lines
1192.1	One solution to socket error problem	CUJO::HILL	Dan Hill-NetMgtConsult-Denver-553-3624	`Thu Aug 11 1994 11:28`	16
	One of my customers encountered the same problem. They had been starting windows as follows: c:> win/n They copied LSL.EXE and IPXODI.COM from WINDOWS directory to IPX directory. They started windows again, this time just using c:> win Additionally, the 3COM driver (which they were using) was listed as 3C5X9 instead of 3C509. ***How did you solve the problem?

    One of my customers encountered the same problem.  They had been
    starting windows as follows:
    	c:> win/n
    
    They copied LSL.EXE and IPXODI.COM from WINDOWS directory to IPX
    directory.
    
    They started windows again, this time just using
    	c:> win
    
    
    Additionally, the 3COM driver (which they were using) was listed as
    3C5X9 instead of 3C509.
    
    
    ***How did you solve the problem?