We have discovered recently that our Cisco 1760 onboard ethernet connection is 10/100 and the Ethernet WIC is only 10BASE-T
I am curious if anyone has heard of a hack or workaround to get this to 10/100
I am pretty sure there is not, but sometimes things are possible.
Thanks for your thoughts
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I would first get a new Ethernet cable and try it. If that doesn't fix it, call your cable company and have them do a diagnostic from their end. They can tell if it is their equipment or not. It their modem is OK, and the Ethernet cable is OK, then your LAN (Ethernet) card is either going bad, or possibly not completely inserted in the socket. To check: turn off and unplug your PC. Take the side off, look where the Ethernet cable goes into your computer. If it is on the motherboard, you may want to get a LAN card and use it instead of the onboard. If the cable goes into a card plugged into one of the slots, make sure it is fully inserted. If it is, you may want to get a new card.
Change out your cable from the wall drop to the phone. A Cisco phone is capable of receiving inline power (Power Over Ethernet) via the blue and brown pairs of the cable. It sounds like you may have a cable with a short in either the brown or blue, or both pairs, shorting out the power when it is connected via ethernet.
If you can, have your IT Tech check the cable, and the line through the wall to the switch.
Had a similar problem with P5ne-sli motherboard, Intel Q6600 cpu, Nvidia GTS 8800 video card. One day the ethernet just stopped working, but it was working... It would connect to my network but would see "limited or no connectivity" in the taskbar. Went into BIOS and looked at the signals and for some reason only 4 of the 8 signals were getting a reading. Figured a power spike had fried my onboasrd ethenet card. Switched to an old PCI ethernet card... after two years I was doing a fresh install, of XP and for shits and giggles I just plugged the ethernet cord into the onboard with the PCI ethernet card removed. When windows went to validate it detected and installed my onboard ethernet...validated then proceeded to update windows. Over a year later it still works. Never bothered to update BIOS until last month and that was only to fix the long boot time with ATI 5770 video card. Willing to bet that resetting your BIOS will fix the problem for you. Just unplug computer, remove battery, attempt power up to clear any juice still in the system. Replace battery and boot up computer... Also removed a DIMM that went bad around the same time. May have been a factor so try testing your RAM.
Going through the GUI would take too long, so use CLI to add the commands below. After that, check the GUI and see how those changes appear.
VLANs: On all equipment use 802.1q tagging. The example below puts adsl ports 1 to 10 in vlan10 and ports 11-12 in vlan2. These vlans are 802.1q tagged on the ethernet ports.
switch vlan set 1 1~12:X enet1~enet2:FT DEFAULT switch vlan set 2 1~10:X 11~12:FU enet1~enet2:FT VLAN2 switch vlan set 10 1~10:FU 11~12:X enet1~enet2:FT VLAN10 switch vlan set 17 1~12:X enet1~enet2:FT VLAN17 switch vlan pvid 1~10 10 switch vlan pvid 11~12 2 switch vlan pvid enet1~enet2 1 switch vlan priority * 0 switch vlan gvrp * disable switch vlan frametype * all switch vlan cpu set 1
ATM circuit: Each port requires one or more VPI/VCI circuit. You could map different circuits to corresponding vlans. The config below creates a primary circuit 1/35 on each port. On ports 5 and 9 is another circuit 1/32 mapped to vlan10
adsl pvc set * 1 35 super DEFVAL adsl pvc set 5,9 1 32 10 0 DEFVAL
Remember a dslam is just a switch, bridging packets from a VC onto a VLAN or straight onto ethernet.
I recently had a client switch do this to me. The only way to get it working was to manually put the NIC on my laptop to 10 Mb and Half duplex. After calling Cisco and opening a TAC case, it was deemed faulty hardware.
If you have SmartNet (anyone buying Cisco should always buy SmartNet) on the switch, call TAC and open a case. It's probably faulty hardware.
You must use a router to perform NATing to the ISP. Simply use a Netgear or Linksys router and plug your access point into it. You can even use a Netgear or Linksys wireless router with the ethernet ports built into it. Just disable the onboard wireless.