Wired port not conencting

I have a poor wired connection running to my bedroom - only 4 wires available instead of the 8 wire Cat-5. I have had an old Airport connected (original model) and it worked fine. I tried to upgrade to the new Airport Extreme and the internet connection does not work. The Airport Extreme works fine at other locations so I dont think it has the problem. Further, I cannot get my Apple TV or Mac Book Pro to connect at this wire. The original Airport still connects fine, however. The ethernet is operating on wires 1,2,3 and 6 only.
Any thoughts? (I realize that this is not proper set-up, but this is all I can do)

Not sure what else to try. Could the wire type be part of the problem? Not using cat-5 but using 8 wire phone cable, and four of the wires are being used for the phone jack. Still seems strange that everything would be fine with Airport device (802.11B only) and not with any of the 802.11G or N devices I have tried (Linksys, Airport Extreme N, Apple TV)

Similar Messages

Wired ports not connecting

Have a WRT600N that works fine on both wireless bands, but simply will not connect on any of the 4 wired ports. I've tried 2 different ethernet cables (both confirmed working via the modem), 2 different computers, 2 different OSes. Nothing. LEDs light up on both ends to indicate a gig connection, but adapter can't get an IP. Apadter status always shows zero bytes received (on BOTH computers). Weird thing is, it WILL get an IP if a machien is conencted via wire AND wireless; I assume the IP is somehow being assigned by conencting through the wireless link, as the wired adapter still shows zero B received.
I've done multiple resets to no avail. I've read all the troubleshooting tips and other posts indicating similar problems. I've hit a wall and suspect that the router is physically hooped.
Anybody know something worth trying before I am force to buy a new one?

The reason why I'm asking you to disable the wireless is to avoid conflict while we troubleshoot your wired connection. If the wireless adapter obtains an IP from the router first, the wired connection might have trouble getting an IP from the router. This is for isolation purposes only.
If you want an easier path, upgrade your router's firmware. If you already did that, try re-flashing it.

AEBS won't assign IP via Wired ports, but it does assign IP Wirelessly

I'm having the strangest problem, my AEBS will assign an IP address in the 192.168.1.X range when connected to it wirelessly, but when I connect to it via one of the wired ethernet ports in the back I get a bad IP (169.XXX.XXX.XX).
This started happening over the weekend and I have tried reseting the unit and still can't get the AEBS to assign the correct IP over Wired ports, not even to a Airport Extreme connected via wired ethernet on another room (all I get is the amber flashing light on the AX).
Any help would be appreciated.
Black MacBook, Intel iMac & Mini Dual Mac OS X (10.4.9)

Hi Duane,
Yes I did configure my AEBS to give IP's in the range of 192.168.1.XXX. But when I connect my MacBook via Airport I get the correct 192.168.1.XXX IP, but if I connect it via Wired Ethernet i get the other 169.XXX.XXX.XXX address. This also happens with my Airport Express that it also gets an IP in the 169.XXX.XXX.XXX range which is consistent when a device doesn't issue a correct IP address.
Any help is much appreciated

Wired ports 1,3,4 no longer work on WRT54G

I have a wireless router, WRT54G v2, and the wired ports 1,3,4 do not work anymore. The only one that works is port 2, and after a variable amount of time, but within a day or two, both the lights for port 2 and port 4 will light up. At that time I will no longer be able to connect to the Internet unless I disable my LAN connection. If I cycle the power on the router it will go back to working for a day or so.
Until now this hardware had been working beautifully for almost 2 years. Is it beyond fixing?
Thanks

try doing a hardreset or updgrade the firmware and check if it would fix the prob..and try checkin gyour cables also..if it would do the same thing then i guess your router hardware part is broke..

Is there ANY way to configure the wired ports on Airport Extreme with 7.6.1 software?

I need to connect a Cisco router to one of the wired ports because I'm creating a home lab with several switches and routers and attached hosts. I need the VERY BASIC ability to set (or even just to SEE) what IP address the AirPort is using/assigning, but with the current AirPort Utility, you apparently can't show the DHCP table for wired connections or set up a static pool of addresses to use or really, to do anything else that is ABSOLUTELY BASIC networking configurations for a router. I don't even know what range of IP addresses the AirPort is using for the wired ports.
I love this device - it works much better than my old Linksys that I replaced a couple years ago, but this is the Apple Nannies taking things too far. Sure, make the products easy to configure and use, but stop taking away the ability for advanced users to actually use the product because all you're doing is ******* off your power users - which are the exact people whose friends always ask for recommendations on what products to buy. I've always recommended Apple products to everyone, but if they're going to engineer everything so that only stupid people can use them, then only stupid people will buy (and recommend) them. (Can you tell I'm annoyed that I've wasted so much time on a completely unnecessary and irrelvant side-issue when I should be already working on my actual work project?)
/Rant-off
So, does anyone know how to access the actual configuration of the AirPort Extreme so I can use a static IP address for my Cisco router that's plugged into one of the AirPort's wired ports? That's all I need.
Thanks.

The AirPort assigns IP addresses via DHCP in a range you specify. You may also elect to assign devices their own static IP addresses. That does not involve the Extreme at all, though you may "reserve" those addresses in its DHCP Reservations table.
AirPort Utility > Network > Network Options...
Assigning static IP addresses obviates any need to determine the IP addresses the Extreme assigns.
Update its firmware to version 7.6.3.

Wired port cannot establish TCP connections

I have come across an error that I have so far been unable to solve via google/searching forums.
From time to time, the wired port loses the capability to establish TCP connections. I can ping fine, I can resolve names fine indicating that at least UDP 53 is working. It's impossible to complete a three way handshake for any TCP connection, be it SSH, HTTP, FTP or anything else. This happens randomly after a network connection has been working fine for days. The Internet Connection Wizard claims everything is peachy as it probably just performs a ping to some site.
A reboot does not fix the problem - what does fix it is unplugging the cable, changing to wireless and associating with a network, opening a connection, then shutting down AirPort again and plugging the cable back in. Just replugging without establishing a TCP connection via AirPort does not work.
Is there anything I am missing here? Should I be contacting an Apple Store to talk about repairs/replacements?
Thanks for your time and consideration, if there's any other information needed to make light of the problem, I will post it as soon as I see the request. Unfortunately, I cannot produce the problem at will and have so far neglected running a traffic sniffer to look at exactly what is happening on a packet level - tho "telnet server 80" times out when "ping server" works fine.

Well, I have gotten the FMS on Windows to work via my basic client app (via localhost in the NetConnection call). Taking the same SWF and specifying the external IP of the Windows machine doesnt work.
So I am kind of back to square one.
I made sure that the default Adaptor is bound to any IP (using ":1935,80" in the default Adaptor.xml HostPort tag). So FMS should be bound to all network interfaces.
Just to clarify: FMS is running in "development" mode. Does that mode prevent external connections?

WRT320N Can't get IP Address - only using 1 wired port - no internet access - web setup pages hang

Just bought Linksys WRT320N to replace Netgear MR814.
Can't get connected to internet using Linksys WRT320N.
Setup:
ISP: Cox Communications (Cable)
Firmware: v1.0.03 build 010 Jul 24, 2009
1 wired - port 1- to Windows XP SP 3 Dell Desktop
Setup Attempts:
1. Tried to setup using install CD. Kept erroring out with Error 302: Internal Error. tried this 3 times
2. Went through the reset, power down, power up procedures.
3. Ping 192.168.1.1 = success
4. Connected to 192.168.1.1 via web browser
5. Set MAC Address = computer's MAC address
6. Set MTU = Auto (1500). Also tried Manual 1492
Was unable to get IP address using IP Address Release and IP Address Renew. Internet IP Address still = 0.0.0.0
Note that the web page will always get stuck after perfoming a couple of actions (like after switching between tabs). Message in bottom of browser is "Wating for http://192.168.1.1/Status_Router.asp". And on the screen the hourglass symbol never goes away.
Note that the old Netgear router still works fine and I am currently connected to the internet using the Netgear router. I'd appreciate any help getting the new Linksys router functioning/connecting to the internet/obtaining and IP address.
Thanks for your help.
Solved!
Go to Solution.

I don't know where I was unclear: you wrote before that you have used the mac address clone function on the WRT to clone the MAC address of the PC. This way the WRT "pretends" to be the PC if you connect the WRT internet port to your modem.
However, the PC is not the device which you used before to connect to the internet. The PC was not the device which was connected before to the modem. If you connect the PC directly to your modem it won't get an IP address either. It won't have internet.
The problem is that your ISP only allows you to have a single active internet connection at any given time. If you simply connect a different device with a different MAC address to your modem this other device won't get an IP address. As you have connected the Netgear router to your modem and you have internet then you have to clone the MAC address of your Netgear router. That's the device which is connected to your internet and that's the MAC address for which your ISP has locked your internet connection.
Thus, one more time: clone the MAC address of the netgear router (the internet or WAN port MAC address) on your Linksys router. Then the Linksys pretends to be the Netgear router and your ISP should accept the Linksys router. The netgear router should have a status page in it's web interface which shows you the correct MAC address to be cloned.

Airport express wireless networks stop working. wired ports fine

Hi,
My AirPort Extreme has recently started this odd behavior.
For. Some reason, the wi-fi networks fail. The device cannot be detected by the management utility and powering cycling the device is the old way to recover. I have confirmed that the wired ports and internet connection are still working when the extreme enters into this state. (Odd, since my wired pc cannot find the device). So I assumed some firmware issue.
I was at at firmware 7.6.4. When this problem showed up. I downgraded to 7.6.3 and it still occurs.
From other threads:
Interference references- don't think so. We are in a remote location
Overheating- device does not feel unusually warm. It is mounted an a stud. Plenty of air flow around device
Any thoughts?
Thanks

I did find this work around for Airport Utilitiy 5.6, which has allowed me to reset both of my Airport Expressses and configure them from Mavericks. So far so good, but the base station named "Roving Airport Express" is still fussy, at least in the eyes of Airport Utility.
http://coreyjmahler.com/2013/10/24/airport-utility-5-6-1-on-os-x-10-9-mavericks/

Connecting a BEFSX41 to a WRT610N to provide extra wired ports

I just upgraded my home network to use a WRT610N as the primary router/switch (just behind the DSL modem). I've got more than 4 wired devices that I'd like to connect to the network. Can I use my old BEFSX41 as just a simple Switch (or router/switch) to give me extra ports (even though they're slower 10/100 ports rather than 10/100/1000 ports like the 610 has)? How do I wire them together? How do I reconfigure the 41 to behave nicely in the new network config? (that is, any machine (including wireless) can connect to any other machine in the overall network, and possibly even machines outside the network can come in and talk to machines on either router?) What other device(s) can I use instead of the 41 to give me extra wired ports (especially if I need 10/100/1000 ports)? Thanks very much.

The ideal solution for your setup would be to use a gigabit switch, such as the SD2008, or the EG008W.   A switch has no setup, just wire it to any LAN port on your WRT610N and it will work, allowing all computers on network to share files and/or printers. Note that when you wire a switch to your router, you will "waste" one port on each device, therefore a 4 port router wired to an 8 port switch will give you 4+8-2 = 10 useful wired ports.
If you prefer, you can convert your BEFSX41 to a switch, and use it.   However, this will only add 2 wired ports to your network, because 4+4-2 = 6.
To convert your BEFSX41 to a switch, do the following:
1) Power down the BEFSX41 and disconnect it from your network and all other devices, then wait one minute.
2) Next reset the BEFSX41 to factory defaults. To do this, power up the BEFSX41 and allow it to fully boot (1-2 minutes), then press and hold the reset button for 30 seconds, then release the button and allow the BEFSX41 to reset and reboot (2-3 minutes). Then power down the BEFSX41, and wait one minute.
3) Power up the BEFSX41, then (using a computer that is wired to a LAN port) login at 192.168.1.1 and make the following changes:
   a) Set "Local IP address" to 192.168.1.2 (this assumes that your WRT610N is using 192.168.1.1, and that you are not using the 192.168.1.2 address elsewhere in your network.)
   b) Set the "DHCP server" to "disabled".
   c) Click on the "Save Settings" button, then wait (3-60 seconds) for the screen to refresh. You will likely be disconnected from the BEFSX41. Do not worry about this. Power down the BEFSX41 and your computer.
4) Next, wire the WRT610N and the BEFSX41 together, LAN port to LAN port. Do not connect anything to the Internet port on the BEFSX41.
5) Power up your network. It should work.
Message Edited by toomanydonuts on 03-22-2009 03:53 AM

Prime 2.1 wired port attribute report, vlan report

Hi Guys,
I'm looking to run a report on prime for a customer to show them their wired inventory. I'm particularly interested in displaying switch name, switch port number, vlan assigned. I have generated a wired port attribute summary which seems to have most of the info, but the Vlan id is alway 0 instead of the correct vlan ID. AM i missing something for this?
Also if i select Device name to customize the report it keeps reverting to Device IP which is not useful for the customer!

Isn't Interface Capacity the same thing?

Mountain Lion Mac Mini Server Ethernet Port Not Working

I have a Mac Mini Server and once I upgraded to Mountain Lion Server the Ethernet port is unresponsive. It worked before upgrading. Is there something with Mountain Lion Server that is causing the Ethernet port not to work properly?

Make a "Genius" appointment at an Apple Store.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

PI MDM Adapter Error - MDM port not found

We are working on an R/3 - PI - MDM scenario using the PI MDM Adapter. We are currently encountering the following errors.
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-08 15:31:22 Error Message could not be forwarded permantely to the JCA adapter. Reason: System error: MDM port not found
2009-09-08 15:31:22 Error Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found
2009-09-08 15:31:22 Error Adapter Framework caught exception: System error: MDM port not found
2009-09-08 15:31:22 Error Delivering the message to the application using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.ra.cci.XIAdapterException: System error: MDM port not found.
Is there an issue with our receiver communication channel and the MDM Access Parameters? We are using the Port code and Remote System code provided by the MDM team.
Anyone experience this same issue?

We are no longer seeing the MDM Port Not found error, but we are still seeing the UnknownServer error. Looking at RWB Message Monitoring it appears that the message is successfully sent to the MDM server, but nothing is coming into the Ready folder. Any ideas on where the message is going, and why it is not showing up in the Ready folder?
In RWB - Communication Channel Monitoring
MDM Adapter listener could not start due to: Can not create repository session '<server=XXXXXXXX serverUser=Admin repository=Product user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'XXXXXXXX' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer
In RWB - Message Monitoring
2009-09-11 14:04:15 Information The message was successfully received by the messaging system. Protocol: XI URL: http: //XXXXXXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-11 14:04:15 Information Using connection MDM_http ://sap.com/xi/MDMAdapter. Trying to put the message into the receive queue.
2009-09-11 14:04:15 Information Message successfully put into the queue.
2009-09-11 14:04:15 Information The message was successfully retrieved from the receive queue.
2009-09-11 14:04:15 Information The message status was set to DLNG.
2009-09-11 14:04:15 Information Delivering to channel: MDS_TEST_CC
2009-09-11 14:04:15 Information The message was successfully delivered to the application using connection MDM_http ://sap.com/xi/MDMAdapter.
2009-09-11 14:04:15 Information The message status was set to DLVD.
I thought the implementation of the MDM Adapter was suppose to be straightforward and simple
Edited by: Chris Williar on Sep 11, 2009 9:56 PM

Problem removing bluetooth stack / hidden devices / COM ports not released

Hi
Having problem completely removing Toshiba Bluetooth stack / hidden devices / com ports not released
I uninstalled Toshiba BT s/w...
But:
1) Toshiba BT hidden devices still appear and I can not remove (get error)
2) COM ports occupied by Toshiba BT not released (so they cannot be used by another BT stack) and still appear in registry
ex: friendly name Toshiba BT Port (COM4) still in registry
3) These unreleased com ports do NOT appear in device manager
Thanks

It seems that you still have some configurations which were not removed during the uninstallation.
This means that the resources can not be release, because those are still necessary in case of a
new installation of the stack.
The first I would try is the following:
- Install the latest Toshiba Bluetooth stack.
- Uninstall it. Ensure that you answer all questions with "yes" ! This means also the one which asks if all configurations should be removed.
- Reboot
- Check again

Serial ports not appearing in MAX - VISA installed.

Hi All,
Had a rather strange issue today that I couldn't resolve with serial ports not appearing in MAX (and hence being inaccessible to LabVIEW). Under the windows device manager it shows 4 COM ports and I have verified with an external program that they are functioning correctly.
I had the LabVIEW 2011 SP1 f2 runtime installed, DAQmx 9.6.1 and NI-VISA 5.3 (5.2 also didn't work).
Things I have tried:
- Updating VISA from 5.2 to 5.3
- Reinstalling the COM port devices under device manager
- Changing the COM port numbers
- Verifying that the COM ports are functioning correctly
- Tried adding a USB to Serial converter as a new COM port
- Reinstalling MAX
- Reinstalling NI-VISA
- Reinstalling everything (reboot each time when prompted)
- Resetting the hardware configuration from within MAX
- Run installers / MAX as administrator (this is running from the local admin account)
- Checked that NI-VISA appears under software in MAX
- Repaired MAX/NI-VISA
Is there anything else that could cause the COM ports not to appear in MAX when they appear (and work correctly) in device manager when a reinstall of NI VISA / MAX won't solve?
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets
Solved!
Go to Solution.

I found the solution - it turns out that the serial ports were available to LabVIEW, they just didn't show up in MAX because installing just the runtime does not show the devices in MAX.
Despite doing a lot of googling earlier, it didn't throw up this knowledgebase article until I searched for it under a different phrase - http://digital.ni.com/public.nsf/allkb/766FD80DAE42E52886256A0200619CFE?OpenDocument
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Parallel Port Not Assigned

Changed my LapTop with ME to another one with XP. While trying to configure my DAQPad 1200, MAX 2.2 shows no options on the parallel port other than "Not Assigned". I have an older Lap also with XP and I could install the DAQPad. Both computers are TOSHIBA, Satellite. Is there a driver with corrected bugs for XP? Thanks for the help

Refer to the previous post linked below:
DAQPad-1200 parallel port not assigned

Wired port not conencting

Similar Messages

Maybe you are looking for