| Home | Register | Members | Search | Links |
![]() |
| Thread Tools | Display Modes |
|
|
|
| |
|
Lanwench [MVP - Exchange]
Guest
Posts: n/a
|
Control Freq <(E-Mail Removed)> wrote:
> Hi, > I appreciate that I am not giving you much to go on, but I have a > networking problem. > > I have a Sony Vaio Laptop, a 3Com OfficeConnect Hub and a Dell PE 2800 > server. > Laptop is Win XP Pro, Server is Windows Server 2003. > > The Server has an embedded Intel 10/100/1000 NIC as standard. Based on what you've written, this really doesn't sound like a server problem. I suspect you're having problems on your workstation (see below). You also ought to swap out that hub for a decent Ethernet switch - they're much better performing and are not expensive nowadays, even for small offices. > > > Now, the problem is that I get intermittent ping responses from the > server. > This is not a broken cable issue. > > If I set up a 'ping -t 192.168.1.100' in a command prompt on the > laptop, then I might see successful ping responses from the server. > The IP address just mentioned is the IP of the server. > > Now, if I unplug the Cat 5 cable from the laptop, the ping response > changes to 'Hardware Error' and eventually changes to 'Destination > unreachable' Yes, that's normal behavior. > > Now, If I plug the network cable back in, I SOMETIMES start to receive > ping responses after a few seconds, but most often the laptop will > keep responding with 'request timedout'. Stop the ping and start it again. You're unplugging & reconnecting your network connection - this sounds perfectly normal to me so far! > > After a few minutes of seeing 'request timedout' the laptop might > suddenly get a good reply to the ping. > > So, I can't work out what is wrong with this? > > Why would the server respond OK sometimes and not others? It really doesn't sound like it's the server's fault - sounds like the issue is with your laptop reconnecting to the network. This is either your laptop (if you're using sony's crappy network management software, disable or uninstall it in favor of the built-in networking stuff in Windows) or you're having a problem on your hub. > > Just as a further test, I can also plug in another PC into the hub, > and this same ping test succeeds every time to that piece of kit. I am > inclined to believe that there is something wrong with the NIC on the > server, From the server, you might mention whether you are having any problems connecting to anything. > but I need more advice. > > Also, in the full network setup. If I plug in a hardware firewall into > the hub, and have lots of PCs connecting through the firewall, they > all ping the server OK everytime!!! You'll have to explain what you mean by "plug a hardware firewall into the hub" -as in, is this going onto your LAN, etc. > > I don't understand enough about this problem. Sorry, but I really don't understand what the problem *is* yet. What are the symptoms of the issue that caused you to write, outside of the ethernet cable disconnect/ping thing? > > Any help appreciated! > > > Regards |
|
|
|
|
|||
|
|||
|
Control Freq
Guest
Posts: n/a
|
On 31 Jan, 13:24, "Lanwench [MVP - Exchange]"
<lanwe...@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote: > Control Freq <n...@nhthomas.freeserve.co.uk> wrote: > > Hi, > > I appreciate that I am not giving you much to go on, but I have a > > networking problem. > > > I have a Sony Vaio Laptop, a 3Com OfficeConnect Hub and a Dell PE 2800 > > server. > > Laptop is Win XP Pro, Server is Windows Server 2003. > > > The Server has an embedded Intel 10/100/1000 NIC as standard. > > Based on what you've written, this really doesn't sound like a server > problem. I suspect you're having problems on your workstation (see below). > You also ought to swap out that hub for a decent Ethernet switch - they're > much better performing and are not expensive nowadays, even for small > offices. > > > > > Now, the problem is that I get intermittent ping responses from the > > server. > > This is not a broken cable issue. > > > If I set up a 'ping -t 192.168.1.100' in a command prompt on the > > laptop, then I might see successful ping responses from the server. > > The IP address just mentioned is the IP of the server. > > > Now, if I unplug the Cat 5 cable from the laptop, the ping response > > changes to 'Hardware Error' and eventually changes to 'Destination > > unreachable' > > Yes, that's normal behavior. > > > > > Now, If I plug the network cable back in, I SOMETIMES start to receive > > ping responses after a few seconds, but most often the laptop will > > keep responding with 'request timedout'. > > Stop the ping and start it again. You're unplugging & reconnecting your > network connection - this sounds perfectly normal to me so far! > No, this is not normal. The ping command can keep going while the cable is unplugged/replugged. The symptoms of my problem are shown best with the ping responses. If I unplug the cat5 cable, then the ping response shows "request timedout". OK so far. Now, if I plug the cat5 back in then one of two things happens. 1) The ping responses from the server are received again within approx 5 seconds of reconnecting the cable. 2) The ping command continues to show "request timedout" for several minutes. If I repeatedly do this test, I get condition (1) above in about 25 percent of cases. > > > > After a few minutes of seeing 'request timedout' the laptop might > > suddenly get a good reply to the ping. > > > So, I can't work out what is wrong with this? > > > Why would the server respond OK sometimes and not others? > > It really doesn't sound like it's the server's fault - sounds like the issue > is with your laptop reconnecting to the network. This is either your laptop > (if you're using sony's crappy network management software, disable or > uninstall it in favor of the built-in networking stuff in Windows) or you're > having a problem on your hub. > Well, I have tried two PCs, my sony laptop, and an XP embedded touch screen copmuter. All of these have different NIC hardware. I have also used an older 3Com SuperStack II hub. In each case the problems are the same. The only common piece of equipment is the PE2800 server. > > > > Just as a further test, I can also plug in another PC into the hub, > > and this same ping test succeeds every time to that piece of kit. I am > > inclined to believe that there is something wrong with the NIC on the > > server, > > From the server, you might mention whether you are having any problems > connecting to anything. > > > *but I need more advice. > > > Also, in the full network setup. If I plug in a hardware firewall into > > the hub, and have lots of PCs connecting through the firewall, they > > all ping the server OK everytime!!! > > You'll have to explain what you mean by "plug a hardware firewall into the > hub" -as in, is this going onto your LAN, etc. > > > > > I don't understand enough about this problem. > > Sorry, but I really don't understand what the problem *is* yet. What are the > symptoms of the > issue that caused you to write, outside of the ethernet cable > disconnect/ping thing? Well, the problem is a lack of connectivity between the server and a PC. The problem is best described by observing the ping responses, as described above. > > > > > > > Any help appreciated! > > > Regards- Hide quoted text - > > - Show quoted text - |
|
|
|
|
|||
|
|||
|
Lanwench [MVP - Exchange]
Guest
Posts: n/a
|
Control Freq <(E-Mail Removed)> wrote:
> On 31 Jan, 13:24, "Lanwench [MVP - Exchange]" > <lanwe...@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote: >> Control Freq <n...@nhthomas.freeserve.co.uk> wrote: >>> Hi, >>> I appreciate that I am not giving you much to go on, but I have a >>> networking problem. >> >>> I have a Sony Vaio Laptop, a 3Com OfficeConnect Hub and a Dell PE >>> 2800 server. >>> Laptop is Win XP Pro, Server is Windows Server 2003. >> >>> The Server has an embedded Intel 10/100/1000 NIC as standard. >> >> Based on what you've written, this really doesn't sound like a server >> problem. I suspect you're having problems on your workstation (see >> below). You also ought to swap out that hub for a decent Ethernet >> switch - they're much better performing and are not expensive >> nowadays, even for small offices. >> >> >> >>> Now, the problem is that I get intermittent ping responses from the >>> server. >>> This is not a broken cable issue. >> >>> If I set up a 'ping -t 192.168.1.100' in a command prompt on the >>> laptop, then I might see successful ping responses from the server. >>> The IP address just mentioned is the IP of the server. >> >>> Now, if I unplug the Cat 5 cable from the laptop, the ping response >>> changes to 'Hardware Error' and eventually changes to 'Destination >>> unreachable' >> >> Yes, that's normal behavior. >> >> >> >>> Now, If I plug the network cable back in, I SOMETIMES start to >>> receive ping responses after a few seconds, but most often the >>> laptop will keep responding with 'request timedout'. >> >> Stop the ping and start it again. You're unplugging & reconnecting >> your network connection - this sounds perfectly normal to me so far! >> > > No, this is not normal. I disagree. > The ping command can keep going while the > cable is unplugged/replugged. Not if the computer isn't reconnecting quickly enough. Try this: Ping as described Unplug the cable Plug it back in In a new command window type ipconfig /all and see if you even have an IP address. > The symptoms of my problem are shown best with the ping responses. > If I unplug the cat5 cable, then the ping response shows "request > timedout". OK so far. > Now, if I plug the cat5 back in then one of two things happens. > 1) The ping responses from the server are received again within approx > 5 seconds of reconnecting the cable. > 2) The ping command continues to show "request timedout" for several > minutes. > > If I repeatedly do this test, I get condition (1) above in about 25 > percent of cases. On *all* your computers? If so, this points to the hub ....or whatever is doing DHCP on your network, which you haven't mentioned. >> >> >>> After a few minutes of seeing 'request timedout' the laptop might >>> suddenly get a good reply to the ping. >> >>> So, I can't work out what is wrong with this? >> >>> Why would the server respond OK sometimes and not others? >> >> It really doesn't sound like it's the server's fault - sounds like >> the issue is with your laptop reconnecting to the network. This is >> either your laptop (if you're using sony's crappy network management >> software, disable or uninstall it in favor of the built-in >> networking stuff in Windows) or you're having a problem on your hub. >> > > Well, I have tried two PCs, my sony laptop, and an XP embedded touch > screen copmuter. All of these have different NIC hardware. > I have also used an older 3Com SuperStack II hub. In each case the > problems are the same. What about a switch? It's 2008 - hubs have been obsolete for a long time. > > The only common piece of equipment is the PE2800 server. >> >> >>> Just as a further test, I can also plug in another PC into the hub, >>> and this same ping test succeeds every time to that piece of kit. I >>> am inclined to believe that there is something wrong with the NIC >>> on the server, >> >> From the server, you might mention whether you are having any >> problems connecting to anything. You still haven't answered that. Can you ping your router's LAN IP (in a loop) on the server, with no issues? >> >>> but I need more advice. >> >>> Also, in the full network setup. If I plug in a hardware firewall >>> into the hub, and have lots of PCs connecting through the firewall, >>> they all ping the server OK everytime!!! >> >> You'll have to explain what you mean by "plug a hardware firewall >> into the hub" -as in, is this going onto your LAN, etc. >> >> >> >>> I don't understand enough about this problem. >> >> Sorry, but I really don't understand what the problem *is* yet. What >> are the symptoms of the >> issue that caused you to write, outside of the ethernet cable >> disconnect/ping thing? > > Well, the problem is a lack of connectivity between the server and a > PC. I mean the initial problem that caused you to start doing ping testing to *begin* with :-) > The problem is best described by observing the ping responses, as > described above. More info might help. Are you using AD? If so, please post an unedited ipconfig /all from the server & a workstation (and label each clearly). Check your event logs on clients & server to check for errors. Tell us more about your topology. Etc. |
|
|
|
|
|||
|
|||
|
Control Freq
Guest
Posts: n/a
|
On 31 Jan, 15:09, "Lanwench [MVP - Exchange]"
<lanwe...@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote: > Control Freq <n...@nhthomas.freeserve.co.uk> wrote: > > On 31 Jan, 13:24, "Lanwench [MVP - Exchange]" > > <lanwe...@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote: > >> Control Freq <n...@nhthomas.freeserve.co.uk> wrote: > >>> Hi, > >>> I appreciate that I am not giving you much to go on, but I have a > >>> networking problem. > > >>> I have a Sony Vaio Laptop, a 3Com OfficeConnect Hub and a Dell PE > >>> 2800 server. > >>> Laptop is Win XP Pro, Server is Windows Server 2003. > > >>> The Server has an embedded Intel 10/100/1000 NIC as standard. > > >> Based on what you've written, this really doesn't sound like a server > >> problem. I suspect you're having problems on your workstation (see > >> below). You also ought to swap out that hub for a decent Ethernet > >> switch - they're much better performing and are not expensive > >> nowadays, even for small offices. > > >>> Now, the problem is that I get intermittent ping responses from the > >>> server. > >>> This is not a broken cable issue. > > >>> If I set up a 'ping -t 192.168.1.100' in a command prompt on the > >>> laptop, then I might see successful ping responses from the server. > >>> The IP address just mentioned is the IP of the server. > > >>> Now, if I unplug the Cat 5 cable from the laptop, the ping response > >>> changes to 'Hardware Error' and eventually changes to 'Destination > >>> unreachable' > > >> Yes, that's normal behavior. > > >>> Now, If I plug the network cable back in, I SOMETIMES start to > >>> receive ping responses after a few seconds, but most often the > >>> laptop will keep responding with 'request timedout'. > > >> Stop the ping and start it again. You're unplugging & reconnecting > >> your network connection - this sounds perfectly normal to me so far! > > > No, this is not normal. > > I disagree. > > > The ping command can keep going while the > > cable is unplugged/replugged. > > Not if the computer isn't reconnecting quickly enough. Try this: > > Ping as described > Unplug the cable > Plug it back in > In a new command window type ipconfig /all and see if you even have an IP > address. OK tried that. I doesn't change anything. > > > The symptoms of my problem are shown best with the ping responses. > > If I unplug the cat5 cable, then the ping response shows "request > > timedout". OK so far. > > Now, if I plug the cat5 back in then one of two things happens. > > 1) The ping responses from the server are received again within approx > > 5 seconds of reconnecting the cable. > > 2) The ping command continues to show "request timedout" for several > > minutes. > > > If I repeatedly do this test, I get condition (1) above in about 25 > > percent of cases. > > On *all* your computers? If so, this points to the hub ....or whatever is > doing DHCP on your network, which you haven't mentioned. > > Sorry, fogot to mention that the computers in question have static IP. Laptop is 10.4.54.135 and server is 10.4.54.133. Both have 255.255.255.0 as mask and both use 10.4.54.1 as gateay, even though it isn't plugged in at this time. I don't think that makes a difference though. > > > > > > >>> After a few minutes of seeing 'request timedout' the laptop might > >>> suddenly get a good reply to the ping. > > >>> So, I can't work out what is wrong with this? > > >>> Why would the server respond OK sometimes and not others? > > >> It really doesn't sound like it's the server's fault - sounds like > >> the issue is with your laptop reconnecting to the network. This is > >> either your laptop (if you're using sony's crappy network management > >> software, disable or uninstall it in favor of the built-in > >> networking stuff in Windows) or you're having a problem on your hub. > > > Well, I have tried two PCs, my sony laptop, and an XP embedded touch > > screen copmuter. All of these have different NIC hardware. > > I have also used an older 3Com SuperStack II hub. In each case the > > problems are the same. > > What about a switch? It's 2008 - hubs have been obsolete for a long time. > > Yes, I know, but I don't have a switch to hand. Only two 3Com hubs to play with. > > > The only common piece of equipment is the PE2800 server. > > >>> Just as a further test, I can also plug in another PC into the hub, > >>> and this same ping test succeeds every time to that piece of kit. I > >>> am inclined to believe that there is something wrong with the NIC > >>> on the server, > > >> From the server, you might mention whether you are having any > >> problems connecting to anything. > > You still haven't answered that. Can you ping your router's LAN IP (in a > loop) on the server, with no issues? > > Erm no. There is only one Laptop, a hub and a Pe2800 Server. There are only two addressable devices involved here. However, I now have a Dell PE 2900 to test with. If I replace the PE2800 server with this new PE2900 server then the problem doesn't happen. So, I have to assume that the PE2800 network card is intermittently faulty. Unless you can show otherwise. > > > > > > >>> but I need more advice. > > >>> Also, in the full network setup. If I plug in a hardware firewall > >>> into the hub, and have lots of PCs connecting through the firewall, > >>> they all ping the server OK everytime!!! > > >> You'll have to explain what you mean by "plug a hardware firewall > >> into the hub" -as in, is this going onto your LAN, etc. > > >>> I don't understand enough about this problem. > > >> Sorry, but I really don't understand what the problem *is* yet. What > >> are the symptoms of the > >> issue that caused you to write, outside of the ethernet cable > >> disconnect/ping thing? > > > Well, the problem is a lack of connectivity between the server and a > > PC. > > I mean the initial problem that caused you to start doing ping testing to > *begin* with :-) > > > The problem is best described by observing the ping responses, as > > described above. > > More info might help. Are you using AD? If so, please post an unedited > ipconfig /all from the server & a workstation (and label each clearly). > Check your event logs on clients & server to check for errors. Tell us more > about your topology. Etc.- Hide quoted text - > > - Show quoted text -- Hide quoted text - > > - Show quoted text -- Hide quoted text - > > - Show quoted text - |
|
|
|
|
|||
|
|||
|
Lanwench [MVP - Exchange]
Guest
Posts: n/a
|
Control Freq <(E-Mail Removed)> wrote:
<snipped for length> >> Ping as described >> Unplug the cable >> Plug it back in >> In a new command window type ipconfig /all and see if you even have >> an IP address. > > OK tried that. I doesn't change anything. But what did you *find* when you tried? > >> >>> The symptoms of my problem are shown best with the ping responses. >>> If I unplug the cat5 cable, then the ping response shows "request >>> timedout". OK so far. >>> Now, if I plug the cat5 back in then one of two things happens. >>> 1) The ping responses from the server are received again within >>> approx 5 seconds of reconnecting the cable. >>> 2) The ping command continues to show "request timedout" for several >>> minutes. >> >>> If I repeatedly do this test, I get condition (1) above in about 25 >>> percent of cases. >> >> On *all* your computers? If so, this points to the hub ....or >> whatever is doing DHCP on your network, which you haven't mentioned. >> >> > Sorry, fogot to mention that the computers in question have static IP. Ah, yes, that does make a difference. I don't recommend statics, by the way, though. > Laptop is 10.4.54.135 and server is 10.4.54.133. Both have > 255.255.255.0 as mask and both use 10.4.54.1 as gateay, even though it > isn't plugged in at this time. I don't think that makes a difference Probably not, but an unedited ipconfig /all from the server & a client would help. <snip>> >> What about a switch? It's 2008 - hubs have been obsolete for a long >> time. >> >> > Yes, I know, but I don't have a switch to hand. Only two 3Com hubs to > play with. Get a switch - they cost next to nothing these days. Seriously. >> <snip> >> >>>> From the server, you might mention whether you are having any >>>> problems connecting to anything. >> >> You still haven't answered that. Can you ping your router's LAN IP >> (in a loop) on the server, with no issues? > > Erm no. There is only one Laptop, a hub and a Pe2800 Server. There are > only two addressable devices involved here. You'll need more, if you want to do any proper isolation testing. So you have no Internet access on this network? > > However, I now have a Dell PE 2900 to test with. If I replace the > PE2800 server with this new PE2900 server then the problem doesn't > happen. > So, I have to assume that the PE2800 network card is intermittently > faulty. > Unless you can show otherwise. You haven't demonstrated that your server ever has any problems connecting to anything. > <snip> >> >>>> Sorry, but I really don't understand what the problem *is* yet. >>>> What are the symptoms of the >>>> issue that caused you to write, outside of the ethernet cable >>>> disconnect/ping thing? >> >>> Well, the problem is a lack of connectivity between the server and a >>> PC. >> >> I mean the initial problem that caused you to start doing ping >> testing to *begin* with :-) >> >>> The problem is best described by observing the ping responses, as >>> described above. Again, you still aren't describing anything other than a problem that happens when you disconnect & reconnnect your Ethernet cable. >> >> More info might help. Are you using AD? If so, please post an >> unedited ipconfig /all from the server & a workstation (and label >> each clearly). Check your event logs on clients & server to check >> for errors. Tell us more about your topology. Etc.- Hide quoted text Please address these. |
|
|
|
|
|||
|
|||
|
|
|
| |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| DNS Failures? | Chip | Broadband | 20 | 08-11-2006 09:27 PM |
| DNS failures? | Joe Soap | Broadband | 23 | 07-25-2006 09:54 PM |
| Plusnet failures | Peter | Broadband | 1 | 06-11-2004 07:13 AM |
| NetDiag Failures | Rajeev | Windows Networking | 2 | 01-29-2004 02:30 PM |
| Constant NIS failures | Paul Raines | Linux Networking | 1 | 10-09-2003 05:41 PM |
Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc. |



Linear Mode

