Network Problems
07 February 2003, 05:00 PM
#1
Scooby Regular
Thread Starter
Join Date: Jan 2003
Posts: 502
Likes: 0
Received 0 Likes
on
0 Posts
just a hub i'm afraid, there is not enough network traffic/users to warrant a switch!
edited for my fantakka spelling
[Edited by ragnarock2 - 7/2/2003 5:01:18 PM]
edited for my fantakka spelling
[Edited by ragnarock2 - 7/2/2003 5:01:18 PM]
02 July 2003, 04:23 PM
#2
Scooby Regular
Thread Starter
Join Date: Jan 2003
Posts: 502
Likes: 0
Received 0 Likes
on
0 Posts
Hi,
We have a customer that has been experiencing network problems recently. We provide a MIS for label printers, and as part of that provide the hardware for the system etc.
Our product runs via telnet sessions and the problem is thus:
The customer has a W2k network (installed by us), the app runs on w2K and the clients connect in via telnet. The hub is a 3com superstack, 100BaseT item, and all cabling was done by BT before we got involved
At the same time of the day (on random days), the telnet session will slow right down, and kick random users off the telnet session, I have looked through the W2K logs, and also Unidata logs (what our software runs on) but there are no problems reported.
My best guess is that this is an environmental issue (i.e. some power surge due to something being turned on) and/or various network cables are dragged over powercables etc, or they are experiencing power surges/spikes etc (the hub is not protected by UPS)
Any other thoughts on what it can be? Any thoughts on how we can prove it is the power etc? As the customer is munching my nuts but I am at a loss as to where the problem is!
We have a customer that has been experiencing network problems recently. We provide a MIS for label printers, and as part of that provide the hardware for the system etc.
Our product runs via telnet sessions and the problem is thus:
The customer has a W2k network (installed by us), the app runs on w2K and the clients connect in via telnet. The hub is a 3com superstack, 100BaseT item, and all cabling was done by BT before we got involved
At the same time of the day (on random days), the telnet session will slow right down, and kick random users off the telnet session, I have looked through the W2K logs, and also Unidata logs (what our software runs on) but there are no problems reported.
My best guess is that this is an environmental issue (i.e. some power surge due to something being turned on) and/or various network cables are dragged over powercables etc, or they are experiencing power surges/spikes etc (the hub is not protected by UPS)
Any other thoughts on what it can be? Any thoughts on how we can prove it is the power etc? As the customer is munching my nuts but I am at a loss as to where the problem is!
02 July 2003, 05:27 PM
#7
Moderator
Join Date: Dec 1998
Location: Staffs
Posts: 23,573
Likes: 0
Received 0 Likes
on
0 Posts
That's okay - sometimes find the autosensing on switches can cause problems if it doesn't set the duplex properly.
Have you got Perfmon running and logging to a file? It might show a CPU spike or something. Alternatively, if nothing shows up you can look away from the server.
Have you got Perfmon running and logging to a file? It might show a CPU spike or something. Alternatively, if nothing shows up you can look away from the server.
Trending Topics
02 July 2003, 11:04 PM
#8
Scooby Regular
Thread Starter
Join Date: Jan 2003
Posts: 502
Likes: 0
Received 0 Likes
on
0 Posts
Nothing doing in perfmon - the server is behaving fine - that's why I am veering toward some environmental issue (that and the fact that the network is fine all other times of the day!)
02 July 2003, 11:13 PM
#9
Scooby Regular
Join Date: Mar 2000
Location: Gloucestershire, home of the lawnmower.
Posts: 4,531
Likes: 0
Received 0 Likes
on
0 Posts
Same time of day may give a clue.
Any chance you can advance the clocks on all machines involved by say six hours until it happens again ?
This way, if it occurs at the same time as it does now according to the machines, then it is something on the machines. If it occurs but at the same wall clock time as it does now, then it is external and that would narrow it down for you.
Hope that makes sense.
Cheers
Ian
Any chance you can advance the clocks on all machines involved by say six hours until it happens again ?
This way, if it occurs at the same time as it does now according to the machines, then it is something on the machines. If it occurs but at the same wall clock time as it does now, then it is external and that would narrow it down for you.
Hope that makes sense.
Cheers
Ian
03 July 2003, 09:07 AM
#11
Scooby Regular
Thread Starter
Join Date: Jan 2003
Posts: 502
Likes: 0
Received 0 Likes
on
0 Posts
good idea RE clocks, but as it is on random machines, I would guess it is not a problem with the machines themselves. There is nothing scheduled to run at that time of day (all back-ups, checks etc are scheduled for overnight)
03 July 2003, 10:59 AM
#13
Scooby Regular
Thread Starter
Join Date: Jan 2003
Posts: 502
Likes: 0
Received 0 Likes
on
0 Posts
Nope, nothing like that either!!!
The only thing that we originally thought could be the problem, was that there old system was a lotus approach file (of 1.5GB) and they may have been opening/sorting this over the networ, but we have been assured they havent touched the file (mind you, who ever believes end-users?)
The only thing that we originally thought could be the problem, was that there old system was a lotus approach file (of 1.5GB) and they may have been opening/sorting this over the networ, but we have been assured they havent touched the file (mind you, who ever believes end-users?)
Thread
Thread Starter
Forum
Replies
Last Post