Subject | NWLink ?? |
---|---|
Author | Woody |
Post date | 2001-06-19T17:46:47Z |
I am trying to track down the infamous i_net error 10054 (Winsock error).
The network is set up as follows:
Novell server 4.x - main network server
Workstations - variety of Win95/98/2000
Interbase Server - Win2000 server running only Interbase (V 6.0.1.0 ,
all clients updated and program uses latest IBX components)
The clients log in only to the Novell server, not the 2000 server so
they are still running IPX/SPX as well as TCP/IP. I am currently researching
the master browser setup to dsable it on all machines so as to eliminate any
excessive traffic in that regard.
I have several questions:
1. If a rogue workstation is causing excessive 10054 errors, is that enough
to disconnect everyone else from the Interbase server?
2. The Interbase server is running NWLink as well as TCP/IP. Could that
cause a problem?
3. Not all workstations are assigned IP addresses, just TCP/IP protocol. Is
that a potential problem or one waiting to happen? (DHCP is not implemented)
Thanks for any insight into this ongoing and perplexing problem...
Woody
The network is set up as follows:
Novell server 4.x - main network server
Workstations - variety of Win95/98/2000
Interbase Server - Win2000 server running only Interbase (V 6.0.1.0 ,
all clients updated and program uses latest IBX components)
The clients log in only to the Novell server, not the 2000 server so
they are still running IPX/SPX as well as TCP/IP. I am currently researching
the master browser setup to dsable it on all machines so as to eliminate any
excessive traffic in that regard.
I have several questions:
1. If a rogue workstation is causing excessive 10054 errors, is that enough
to disconnect everyone else from the Interbase server?
2. The Interbase server is running NWLink as well as TCP/IP. Could that
cause a problem?
3. Not all workstations are assigned IP addresses, just TCP/IP protocol. Is
that a potential problem or one waiting to happen? (DHCP is not implemented)
Thanks for any insight into this ongoing and perplexing problem...
Woody