2008-02-27, 02:24 PM
To all,
I have found that his particular niche forum is a very technically competent and just a plain smart crowd: a great resource! enough brown-nosing I guess...![Big Grin Big Grin](https://forums.nextpvr.com/images/smilies/biggrin.png)
Anyway, I am having an issue with my home network. Here are the stat's for all of the network appliances:
- D-Link DI-524 Wireless B/G Router, My machines are all setup with Static DHCP assigned IP's
- Hardwired Machine: ECS K7S5A (old board but a workhorse!) with onboard SiS 900 NIC, 1.5 GB DDR RAM, Athlon XP 2400+, Windows XP Home
- Primary Wireless Machine: HP Laptop, AMD TK-57 Core Duo, 2 GB RAM, Built-in Wireless, Windows Vista Home Premium
I could toss out stats all day, but I don't think anymore is necessary.
Originally, the hardwired machine (acting more as a NAS and video capture server while serving some video editing functions) was connected to the router via a 6 foot factory made ethernet cable. These were both located in my basement. Wireless signal strength seemed to be OK. No major file transfer problems, etc. with this setup.
To the present, I got a wild one up the "you-know-what" and decided to rebuild the server as strictly a storage and tv capture machine. In doing so, I decided to move my broadband modem and router to my first floor where the laptop does most of the work for increased signal strength and for the desire to add a MediaMVP to the network (5 feet from the router). So, I decided to do the rebuild of the hardwired machine on my first floor to keep from having to sit in the basement for hours on end. While doing this, I used a 15' foot factory made ethernet cable to connect to the router. Everything with file transfers, internet downloads, etc. were fine.
After finishing the build, I placed the "server" style box back into my basement and made up a cable out of some Cat5 I purchased from Lowe's approximately 40' long. I hooked everything up and found that when initially connecting to the network, everything worked fine, but in short order, everything crawled to a halt. I could ping the machine from my laptop but started noticing packet loss and increased ping times. I assumed that I maybe goofed up a connector on one end of the cable, i.e. poor crimping, improper crimp, etc. So, I cut both ends, testing each one separately, and replaced. Same story! I then thought I was maybe getting some goofy interference from my cable routing path. So, I isolated the ether net cable, but still the problem remained. Tried different router lan ports, but no change. Router reboots produced the same problems. Checking some drivers and finding a few other problems, I reloaded windows, installed some older, known working drivers on the mobo and found that the problem still existed! So, I decided to bring the machine back upstairs and connect through the 15' cable I connected to earlier and everything worked as it should! :eek:
My thoughts are that the cable, somehow is just plain bad. Never ran across bad cable myself (bad terminations yes, but not bad cable itself). However, I am wondering if the problem is maybe the increased length of cable. If that is the case, is it the onboard NIC or the router having trouble with the distance.
So, my question/help request is: What are everyone's thoughts here? Cable, hardware? How would everyone go about testing the individual components without spending gobs on individual new equipment pieces (Besides, that is just "spraying and praying" to fix the problem, not really evaluating and solving)?
Thanks in advance and my apologies for the thesis-length post!
I have found that his particular niche forum is a very technically competent and just a plain smart crowd: a great resource! enough brown-nosing I guess...
![Big Grin Big Grin](https://forums.nextpvr.com/images/smilies/biggrin.png)
Anyway, I am having an issue with my home network. Here are the stat's for all of the network appliances:
- D-Link DI-524 Wireless B/G Router, My machines are all setup with Static DHCP assigned IP's
- Hardwired Machine: ECS K7S5A (old board but a workhorse!) with onboard SiS 900 NIC, 1.5 GB DDR RAM, Athlon XP 2400+, Windows XP Home
- Primary Wireless Machine: HP Laptop, AMD TK-57 Core Duo, 2 GB RAM, Built-in Wireless, Windows Vista Home Premium
I could toss out stats all day, but I don't think anymore is necessary.
Originally, the hardwired machine (acting more as a NAS and video capture server while serving some video editing functions) was connected to the router via a 6 foot factory made ethernet cable. These were both located in my basement. Wireless signal strength seemed to be OK. No major file transfer problems, etc. with this setup.
To the present, I got a wild one up the "you-know-what" and decided to rebuild the server as strictly a storage and tv capture machine. In doing so, I decided to move my broadband modem and router to my first floor where the laptop does most of the work for increased signal strength and for the desire to add a MediaMVP to the network (5 feet from the router). So, I decided to do the rebuild of the hardwired machine on my first floor to keep from having to sit in the basement for hours on end. While doing this, I used a 15' foot factory made ethernet cable to connect to the router. Everything with file transfers, internet downloads, etc. were fine.
After finishing the build, I placed the "server" style box back into my basement and made up a cable out of some Cat5 I purchased from Lowe's approximately 40' long. I hooked everything up and found that when initially connecting to the network, everything worked fine, but in short order, everything crawled to a halt. I could ping the machine from my laptop but started noticing packet loss and increased ping times. I assumed that I maybe goofed up a connector on one end of the cable, i.e. poor crimping, improper crimp, etc. So, I cut both ends, testing each one separately, and replaced. Same story! I then thought I was maybe getting some goofy interference from my cable routing path. So, I isolated the ether net cable, but still the problem remained. Tried different router lan ports, but no change. Router reboots produced the same problems. Checking some drivers and finding a few other problems, I reloaded windows, installed some older, known working drivers on the mobo and found that the problem still existed! So, I decided to bring the machine back upstairs and connect through the 15' cable I connected to earlier and everything worked as it should! :eek:
My thoughts are that the cable, somehow is just plain bad. Never ran across bad cable myself (bad terminations yes, but not bad cable itself). However, I am wondering if the problem is maybe the increased length of cable. If that is the case, is it the onboard NIC or the router having trouble with the distance.
So, my question/help request is: What are everyone's thoughts here? Cable, hardware? How would everyone go about testing the individual components without spending gobs on individual new equipment pieces (Besides, that is just "spraying and praying" to fix the problem, not really evaluating and solving)?
Thanks in advance and my apologies for the thesis-length post!