robcrazee
asked on
WHEN IS IT TIME TO CHANGE CAT5 CABLE USED IN A SMALL WINDOWS NETWORK?
We have a customer that has a small Windows network on a DOMAIN with a server using SERVER 2003 and workstations using WINDOWS XP PRO.Only 4 workstations total.The cabling on the network maybe close to 10 YEARS OLD.They have network slowness in general at times as well as connection issues.The SWITCH has been replaced as well as the patch cables from patch panel to switch.This was done about a year ago.When is the network cable too old? Is there a time frame to change cat5 cable?
***there is a linksys router(no wireless) and sonicwall on the network as well***
***there is a linksys router(no wireless) and sonicwall on the network as well***
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I really doubt they're going to have intermittent connectivity due to the cabling, especially since there are only 4 workstations.
Who are they using for their internet provider? Is their modem new?
Get a network analyzer, like WireShark, and take a look at network traffic.
Who are they using for their internet provider? Is their modem new?
Get a network analyzer, like WireShark, and take a look at network traffic.
How is the network wired together? Are you using the two routers to create DMZ?
ASKER
Thank you all for the responses.Their internet connection is provided by a company called BEAMSPEED. It is a wireless internet service that relies on line of sight.The office is in a very rural area that does not have dsl or cable access. The internet connection is actually "ok".The network access to their main program on the server is what is "flaky" sometimes.At times the drive mapping gets lost.
The switch is NOT a Gigabit switch.The Sonicwall was used for remote access to another sister company. We will actually be re-wiring the place very soon anyways so i'll keep you posted.Thanks.
The switch is NOT a Gigabit switch.The Sonicwall was used for remote access to another sister company. We will actually be re-wiring the place very soon anyways so i'll keep you posted.Thanks.
I'd look at DNS. What is providing DNS and DHCP-- the Windows Server? And are you sure that all other sources have DHCP turned off?
What kind of application is it that is primarily being used? If applicable, what type of Database does it use?
I also doubt performance is lost at the physical layer here. A LAN this small and simple would run just fine on something as slow as an old 10mbps Ethernet setup.
As the last two comments, I also think the problem is at the DNS Design or an Application Level problem,...or both at the same time since a DNS problem can cause an authentication problem in the business Application.
As the last two comments, I also think the problem is at the DNS Design or an Application Level problem,...or both at the same time since a DNS problem can cause an authentication problem in the business Application.
Billy