- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: a network cable is unplugged
Switches, Hubs, and Modems
1753734
Members
4691
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2004 07:26 AM
02-15-2004 07:26 AM
Re: a network cable is unplugged
Hi Hao Tian,
With the network cable unplugged, are you able to do an "IPCONFIG" from a command prompt? If you're using a newer Windows version, you should be assigned a 168.x.x.x address if you're a DHCP client. Ping 127.0.0.1 and if that works, we can rule out Layer 3 failure.
An "IPCONFIG /ALL" should reveal your MAC address. If that works, it means that the OS+driver thinks that the NIC is working fine. We can almost rule out Layer 2 failure.
Given the intermitent nature of the problem, Layer 1 is the prime suspect. If you're sure that your UTP network cable is good, chances are it's bad RJ45 connector on your laptop may it be (a) the RJ45 connector being bad itself or (b) a cold solder between the connector pins and the PCB.
With the network cable unplugged, are you able to do an "IPCONFIG" from a command prompt? If you're using a newer Windows version, you should be assigned a 168.x.x.x address if you're a DHCP client. Ping 127.0.0.1 and if that works, we can rule out Layer 3 failure.
An "IPCONFIG /ALL" should reveal your MAC address. If that works, it means that the OS+driver thinks that the NIC is working fine. We can almost rule out Layer 2 failure.
Given the intermitent nature of the problem, Layer 1 is the prime suspect. If you're sure that your UTP network cable is good, chances are it's bad RJ45 connector on your laptop may it be (a) the RJ45 connector being bad itself or (b) a cold solder between the connector pins and the PCB.
If a problem can be fixed, there's nothing to worry. If a problem can't be fixed, worrying ain't gonna help. Bottom line: don't worry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2004 02:26 AM
02-20-2004 02:26 AM
Re: a network cable is unplugged
sorry to all... think it's nothing of all..
Since XP I knew this problem on several networks...
I would have a look at the error statistic on the Switchport you are connected...
It can be cuased with by a saturated network (not only the local - even in direction to your servers)
It can be caused by Duplex/Full/Half-Settings when the switchport is not properlly set (e.G Cisco Portfast)...
looking forward for further feedbacks...
Since XP I knew this problem on several networks...
I would have a look at the error statistic on the Switchport you are connected...
It can be cuased with by a saturated network (not only the local - even in direction to your servers)
It can be caused by Duplex/Full/Half-Settings when the switchport is not properlly set (e.G Cisco Portfast)...
looking forward for further feedbacks...
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP