redbearduk
IS-IT--Management
We have an established network that extends over a number of factories on an industrial estate. Buildings are linked via fibre into the backs of 3COM 3300 switches. We have 5 NetWare servers supporting various services.
Border Manager / Proxy Server is on NW 6
Manufacturing system is supported by a pair of NW 5.1s
DHCP, DNS and printing services also on a 5.1
files and databases on a 5.0
There have been recent extensions to the CAT-5 cabling into the factory areas.
We have experienced a couple of computers developing connection problems. These are Windows 98 based and both in buildings away from the servers.
The problem disappears when the computer is moved into the same building as the servers.
The connectivity problem is only experienced with the connection to the NW 5.0 server.
Copies of small files are successful, copies of larger files can be corrupt. Copies of large files result in connection to the server dropping. A reboot is forced and often has to be done twice before a successful connection is made.
The clients are TCP/IP only. NALEXPLD is run at the end of the login script. Delivering a new application fails because the files are delivered from the 5.0 server.
Typicaly a user can log in and run the software from other servers, but will eventually get a message saying that they have been disconnected from the 5.0 when they have accessed something on it.
I could understand if the problem was consisten, but why is it only happening across the other side of the fibre links? We have a single class C subnet, no reconfiguration is required when moving PC's around.
Any pointers?
thanks
Brian
Border Manager / Proxy Server is on NW 6
Manufacturing system is supported by a pair of NW 5.1s
DHCP, DNS and printing services also on a 5.1
files and databases on a 5.0
There have been recent extensions to the CAT-5 cabling into the factory areas.
We have experienced a couple of computers developing connection problems. These are Windows 98 based and both in buildings away from the servers.
The problem disappears when the computer is moved into the same building as the servers.
The connectivity problem is only experienced with the connection to the NW 5.0 server.
Copies of small files are successful, copies of larger files can be corrupt. Copies of large files result in connection to the server dropping. A reboot is forced and often has to be done twice before a successful connection is made.
The clients are TCP/IP only. NALEXPLD is run at the end of the login script. Delivering a new application fails because the files are delivered from the 5.0 server.
Typicaly a user can log in and run the software from other servers, but will eventually get a message saying that they have been disconnected from the 5.0 when they have accessed something on it.
I could understand if the problem was consisten, but why is it only happening across the other side of the fibre links? We have a single class C subnet, no reconfiguration is required when moving PC's around.
Any pointers?
thanks
Brian