Crio Ethernet Port 'Crashes', Error 42

The problem relates to this post and might even be the same:
http://forums.ni.com/ni/board/message?board.id=170&thread.id=345733
It took me a while to figure out what was going on. Even had a network analyzer to monitor the network traffic. I now am able to reproduce this problem in a very simple way. I have a 'TCP open connection.vi' immediately followed by a 'TCP close connection.vi'. There are some additional shared variables to monitor the status of the TCP open and close vi's. I run this program in an 100 ms timed loop.
I run the program on the controller. I unplug the network cable, wait 5 seconds, replug the cable and voila. It is not possible to ping the controller or to connect to it through the project explorer. However the shared variables are still alive and through an application that is running on my pc I can see that the 'TCP open connection.vi' generates an error 42. In fact any TCP vi generates this error.
The Compact rio is not able to recover from this problem. The only way I know is to reboot the crio in the project explorer or MAX or do it manually. Since we have 15 Crio's that are supposed to run 24/7 and who's only way of data-streaming is through TCP this is a big problem.
Is there any other way to recover from this problem? Is it possible the check the 'readynes' of the ethernet hardware to prevent something like this?
Controller: 9014
Network: use DHCP
halt system if TCP/IP fails = false.
Solved!
Go to Solution.
Attachments:
Controller Test V03.vi ‏33 KB
controllervi.jpg ‏203 KB

Ok I got a bit further , although the problem is not solved. I run the test5 vi (see attachment) and unplug the cable wait 10 secs or so and reconnect the cable. This is how I get it in error-mode. If I try to ping it from DOS, I get a positive reply, so that works. If I try to reconnect from the project window, I get an error. If I watch the shared variables I first see an error 56, wich after 10 seconds or so changes in the error 42. The shared variables are still approachable.
If however, and now it gets intersting, I unplug it in the designated 5000 ms time-frame (see attachment) and then later reconnect the cable, I can reconnect with the vi through the project explorer. This may take a few tries, but eventually I can reconnect. Something seems to go wrong when you unplug the cable while it busy with a tcp/ip function.
This is kinda interesting. Still have to figure out how to use this information to design an application that ALWAYS works.
Attachments:
Controller Test V05.vi ‏37 KB

Similar Messages

How can I configure one of the gateway NI9792 Ethernet port to communicate with a cRIO PAC ?

Hi NI Engineers,
I intend to use my gateway NI9792 the following way:
1. One Ethernet port for network connection. That's how I'll develop it, download software and monitor my application through my PC at my desk.
2. Can the other port be used to communicate with a cRIO device? If so, how can I do it?
It seems to be a stupid question, but I truly could not work this out!
Thanks in advance,
Luiz
"Together we stand, divided we fall..."
Certified LabVIEW Associate Developer
Solved!
Go to Solution.

Good afternoon, Luiz
Follow the first link to guide which module can be used and other links to the best part of bore configuration CRIO. Any questions please contact us.
How Do I Configure My Time Server on the NI WSN-9791 or NI 9792 Gateway?
http://digital.ni.com/public.nsf/allkb/44FA322FAFF8D58D862575BD00591A54?OpenDocument
NI WSN Product and Configuration Guide
http://zone.ni.com/devzone/cda/tut/p/id/8710
Configuring the Dual Ethernet Ports on Real-Time Controllers
http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
video setup and installation CRIO
http://www.ni.com/swf/demos/us/crio/outofbox/
Automatic Network Configuration for cRIO-9073 and cRIO-9074 CompactRIO Controllers
http://digital.ni.com/public.nsf/allkb/37C790309A210A748625757000570938?OpenDocument
Sincerely,
Mauro Vera.

Access to serial and ethernet port in FPGA for cRIO-9068

hi
i want to know if i can Access to serial and ethernet port in FPGA for cRIO-9068 like camera IP
thanks for help

dalyto wrote:
thanks
but how i can i acquire image with IP camera and fpga ???
The Ethernet hardware interface in the cRIO is not directly connected to the FPGA backplane in a way that you could directly access it. Even if you could it would be a pretty bad idea to try to do. A fully operational TCP/IP network stack implementation in the FPGA would not leave much resources for anything else even on the biggest FPGAs available. That doesn't include support for the typical image compression algorithmes which are even more complicated to implement on FPGA. Even if you would go to highly optimized VHDL code directly it would be a pretty difficult thing to do!
In fact implemenintg the MAC and PHY of an ethernet interface on the FPGA is totally trivial in comparison. The IP level could also be implemented fairly easily in the FPGA but anything above that is going to give you bad headaches and still will be very limited in number of connections and packet sizes it can support.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Vfc error disabled because of Ethernet port down?

We are building a new datacenter and is starting to set up the SAN.
This small DC consist of 2 Nexus 5596UP, a Compellent SAN and 2 Dell M1000e cassis with blade servers.
naive FC part in Nexus has been easy to set up but we have problems with the FCOE setup.
Since the blades are not installed yet none of the Ethernet ports are up. As soon as we bind an ethernet port to a vfc the vfc goes to error disable with this message:
%PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 1900%$ Interface vfc101 is down (Error disabled)
Config snippets:
vlan 1900
fcoe vsan 1900
name VSAN-A-FCOE
vlan 1901
name VSAN-B-FCOE
vsan database
vsan 1900 name "VSAN-A"
vsan 1901 name "VSAN-B"
interface vfc101
bind interface Ethernet1/1
no shutdown
vsan database
vsan 1900 interface vfc101
vsan 1900 interface fc2/13
vsan 1900 interface fc2/14
vsan 1900 interface fc2/15
vsan 1900 interface fc2/16
interface Ethernet1/1
switchport mode trunk
spanning-tree port type edge trunk
vlan 1900
fcoe vsan 1900
name VSAN-A-FCOE
vlan 1901
name VSAN-B-FCOE
vsan database
vsan 1900 name "VSAN-A"
vsan 1901 name "VSAN-B"
vsan database
vsan 1900 interface vfc101
vsan 1900 interface fc2/13
vsan 1900 interface fc2/14
vsan 1900 interface fc2/15
vsan 1900 interface fc2/16
interface vfc101
bind interface Ethernet1/1
no shutdown
interface Ethernet1/1
switchport mode trunk
spanning-tree port type edge trunk
Do the vfc go error disable because the ethernet interface being down? I was under the impression it should just go "down"

What you are seeing is normal.. Here are outputs from my lab switch where I shut Eth1/20 which is tied to vFC 20
24.10.5020A.1(config)# int ethernet 1/20
24.10.5020A.1(config-if)# shut
2011 Oct 21 10:16:01 24 %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface Ethernet1/20 is down(Config change)
2011 Oct 21 10:16:01 24 %FLOGI-5-MSG_PORT_LOGGED_OUT: %$VSAN 100%$ [VSAN 100, Interface vfc20: mode[TF]] Nx Port 21:00:00:c0:dd:12:0e:35 logged OUT.
2011 Oct 21 10:16:01 24 %PORT-5-IF_PORT_QUIESCE_FAILED: Interface vfc20 port quiesce failed due to failure reason: Epp Not Supported by Peer (0x19d)
2011 Oct 21 10:16:01 24 %PORT-5-IF_DOWN_NONE: %$VSAN 100%$ Interface vfc20 is down (None)
2011 Oct 21 10:16:01 24 %PORT-2-IF_DOWN_ERROR_DISABLED: %$VSAN 100%$ Interface vfc20 is down (Error disabled)
2011 Oct 21 10:16:02 24 %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet1/20 is down (Administratively down)
24.10.5020A.1(config-if)#

RT: How do I use two independent Ethernet ports?

I have looked around at the forums and seems like no one has had a real solid answer or example on how to use 2 Ethernet ports with RT.
Right now I have two connections configured on the RT:
Primary Connection:
IP:192.168.2.181
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1
DNS Server: 192.168.1.1
Secondary Connection:
IP:192.168.1.180
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1
DNS Server: 192.168.1.1
After using this initial setup, I made a RT project where I used 'UDP Open' for both 192.168.2.181 and 192.168.1.180, and had them both read and write in a sequence (Read and Write for the 2.181 connection, then Read/Write for 1.180).
The computer I'm using to send the data is connected to a switch, which in turn is connected to the RT. Both the RT and my host computer have 2 ports, one of them with ports configured to be 192.168.2.x and 192.168.1.x
Using this configuration I get some weird results:
If I send a packet to 192.168.2.181, I receive it from the UDP Receive vi that has an input connection from my UDP Open assigned to 1.180. I also receive the data the same way when sending packets to 1.180 (as expected). Basicly, no matter what IP I'm sending it to on the RT, the data from either packet will arrive from the same location/vi.
Why is this? Is there anyway to fix this? Did I not configure something correctly?
Does anyone have an example of dual Ethernet ports actually working with LabView RT?
I tried checking out "KnowledgeBase 3VQ6278T: Can I Use Multiple Network Adapters in a PXI or Desktop Real-Time System?", but after following the link to the page, I get:
"Error You are not authorized to view this document". Can any NI people look into this?
Having to make two IPs with different subnet masks obviously just makes things unnecessarily complicated. Can anyone tell me why LabView/NI did this? I know for a fact this isn't a limitation in hardware.
Any help would be greatly appreciated, thanks!

Hey Weizbox.
Sorry to hear you're having such a difficult time using multiple ethernet devices with RT.
Let me go ahead and get the easy stuff out of the way, the link you
have is dead because it's archived (and thus removed forever) though
unfortunately the link on ni.com wasn't corrected to point to the
following resource, which the KB was a word-for-word duplication of
(which is supposedly why it was removed):
http://zone.ni.com/reference/en-XX/help/370622C-01/lvrthelp/configuringdual/
Unfortunately, though, it's much less useful than it sounds.
Before you start feeling like a woodpecker in a petrified forest, lemme
fill you in on why the requirement is there for the two ethernet NICs
to be on seperate subnets. Simple enough, it has to do with the
network stack on both of the operating systems used for LabVIEW
Real-Time - however, the same falls true for even Windows (without
using fancy vendor-specific drivers), so let's not be too hasty.
Neither PharLap ETS nor VxWorks, the two OS's used under the hood,
support redundant network ports. Because of this, if you give two (or
more in the case of PXI and RT Desktop) ethernet devices IP addresses
on the same subnet the routing tables in the network stack get horribly
confused and literally cannot resolve the proper adapter, which either
brings down the ethernet on the entire system or makes it such that one
or more network adapters becomes useless and one adapter takes over all
network traffic (there's no way to predict which adapter that will be,
nor can you control it based on what's plugged in and what's not). On
Windows this is handled by bridging the adapters, but RT does not yet
support bridging (that opens a whole nother can of worms). Long story
short, you still wouldn't be able to give both NICs individual IP
addresses on the same subnet.
Let's take that even one more step. You cannot simply just assign both
ethernet NICs different IP addresses on "virtual" subnets, you actually
need to put both NICs on literally different subnets for the network
routing to actually work. Multiple ethernet devices for LabVIEW RT
were designed with the following mantra in mind - "The FIRST ethernet
device is designed for a TCP/IP network, the SECOND and SUBSEQUENT
ethernet device is designed for OTHER protocol uses." By "OTHER
protocol uses" I mean the second NIC should be used for RT
Deterministic Ethernet (PXI, RT Desktop, et. al.), direct connections
with other targets, and 3rd party or custom ethernet protocols.
Now, realistically, we can't expect users to not use the second NIC for
TCP/IP use, nor should we. However, if you ARE going to use TCP/IP on
the second NIC, you should only use the second NIC for connecting to an
unroutable network in the eyes of the first NIC. So, for instance, the
FIRST NIC can have an IP address of 10.0.62.128, but the SECOND NIC
would need to have an IP address on 192.168.100.23 - and the
10.0.62.128 should not be able to route a TCP packet to the 192.168.x.x
network, and vice versa. In your example I noticed that both networks
used the same Gateway - unless your Gateway is configured to identify
and seperate the two networks, it's not going to end well, and you
shouldn't expect to be able to send data from one NIC to the other NIC
(at least with what you know now). To reiterate, using multiple NICs
using TCP/IP should only be done in cases where you've got (n-1)
isolated subnets, where n is the number of NICs you have using TCP/IP.
A classic example of this is a command-based measurement environment;
the RT system uses the FIRST NIC to talk to a TCP/IP network, in order
to transfer data or provide status to a network, and the second NIC is
connected to a TCP/IP network designed specifically for measurement or
control, where one node sends commands to a single or multiple nodes on
the network at once to perform tasks (like "Take a Measurement", "Stop
a motor", "Bake me a Pie", etc...). The isolated TCP/IP subnet is free
from "random" TCP/IP traffic (especially system announcement
broadcasts) and can have whatever topology/configuration it wants. The
dual networking allows the RT system to work/communicate/perform on
both networks.
I hope this helps shed some light on your situation.
Cheers!
-Danny

No internet access via ethernet port

Hi, have been using my emac via ethernet cable to router, for many months with NO problem accessing internet and others cabled to same router also having no problem and I have used my Pwr Mac wtih no problem and have never had to make any specific settings to either to access the net via the router which gets its wifi signal from elsewhere. With system preferences > network > ethernet open I can see the the router is being recognized cause it appears or dissappears as soon as I plug or unlug the ethernet cable. I open "Activity Monitor" and occasionally, very briefly, there will be data incoming( green spikes ) or outgoing( red spikes ). HD verified OK, ran disk permnissions and scripts. Have not yet run Apple or other( Micro-mat ) hardware testing programs tho I will later. Does anyone know if there is a PLIST file that can get corrupted that would affect ethernet port functioning properly? My guess it is hardware but since I can see the router is recognized makes me wonder about corrupt file ergo a system error or possibly inloaded some file that caused conflict. I also booted from my external drive and tried accessing from the cloned OS system and still did not work. The cloned system is the original has never been updated, nor has any of the applications in clone, so, if it was "system" problem the clone should have worked. However, I had cloned user ergo newest documents, library etc, so that would be the only possible source of conflicts when booted from clone system....Thx Ran

Ping test should be interesting.
Start by pinging router address. Should be able to ping building router if you can figure out it's address.
Could you go wireless to building net? You might buy a usb dongle.
USB dongle
Introducting RokIt, a new wireless USB adapter that is compatible with Mac OS 10.3, 10.4, and 10.5 Leopard.
http://rokland.com/store/productinfo.php?productsid=319
Newer Technology MAXPower 802.11n/g/b USB Adapter. The easiest way to add Wireless Connectivity to ANY computer! 2 Year Warranty.
http://eshop.macsales.com/item/Newer%20Technology/MXP802NU2C/
There are usb to ethernet cable.
You could try another browser.
*MAC Address*
Every ethernet port has a unique MAC Address. A router can block on a MAC Address. That is why I suggest you check out your router.
Note MAC is not Mac. MAC is all upper case.
definition: http://en.wikipedia.org/wiki/Mac_address
*Ethernet port hardware*
I'd say this was some kind of strange hardware problem.
*Dns problem?*
It has symptoms of a DNS problem. The little traffic is a symptom of the problem. You said all the numbers were the same, however.
Verify DNS
apple > system preferences > network
Double click on network connection you are using.
Pick the TCP/IP tab.
Verify that you have a DNS Server. If you do not, look on your windows machine and see what the net address is. You can also pick using DHCF and still enter you DNS server address.
You can use
harddrive > applications > utilities > network utility
to diagnose the situation.
You can ping google.com. Result:
Ping has started ...
PING google.com (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=215.362 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=279.597 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=189.747 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=250.657 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=183.232 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=243.753 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=173.108 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=230.239 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=180.639 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=232.177 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 173.108/217.851/279.597/33.615 ms
If that does work, try pinging 64.233.167.99 Result:
Ping has started ...
PING 64.233.167.99 (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=189.655 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=213.471 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=257.873 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=172.745 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=226.723 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=171.883 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=260.308 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=172.963 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=198.840 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=181.215 ms
--- 64.233.167.99 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 171.883/204.568/260.308/32.247 ms
If pinging 17.254.3.183 works but pinging Google.com doesn't. You have a bad DNS Server address.
BDAqua suggests in a post.
You can use OpenDNS for looking up web addresses.
Put these numbers in Network>TCP/IP>DNS Servers for a try...
208.67.222.222
208.67.220.220
I think they now pretend you need to join to use, but you don't.
https://www.opendns.com/homenetwork/start/device/apple-osx-tiger
(Please note that you do not need to a joint Open DNS to use it.)
http://discussions.apple.com/message.jspa?messageID=5908432#5908432
Google provides free dns lookup too. There numbers are:
8.8.8.8
8.8.4.4
Robert
=======================================================
I suggest that you try pinging Google.com.
Macintosh-HD -> Applications -> Utilities -> Terminal
mac $ ping -c4 google.com
PING google.com (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=177.617 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=251.899 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=169.291 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=250.119 ms
--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 169.291/212.232/251.899/38.894 ms
mac $ ping -c4 64.233.187.99
PING 64.233.187.99 (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=176.723 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=247.889 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=176.890 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=244.623 ms
--- 64.233.187.99 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 176.723/211.531/247.889/34.744 ms
mac $
Analysis: If you cannot ping Goolge.com but you can ping 64.233.187.99, then you need to enter you dns address. For some reason Mac OS X sometimes doesn't set the dns. You can set it manually.
apple > system preferences > network
tcp/ip tab and enter address of dns servers
example 162.33.160.100
You will need to use a different number.
PS.
You are a little short on stating results. You state what you did, but I have to guess the result.
Did: X
Result: Y
Did:
1) Power Book's ethernet cable plugged into router port 5. Working to yahoo.com.
2) Unplugged power book's ethernet cable from router
3) Plugged eMac's ethernet cable into port 5.
Result: eMac using Firefox was not able to access yahoo.com
Robert

How to specify one ethernet port for network home directories (other for normal filesharing)?

So I'm trying to get Home Directories up and running on a 10.6.8 Xserve (waiting until I get my NFS sharepoints migrated to a Linux server [for other reasons] before moving up to 10.7 Server). But posting here since that will be happening in the next few weeks, and it might be applicable now (so I can at least get that resolved ahead of time).
I have a different DNS entry for each ethernet port: server.office.domain.com at 192.168.0.11 for the first, and homes.services.internal at 192.168.0.10 for the second. DNS lookups for both resolve correctly (as does the reverse lookup).
If I use the Server Admin to pick a sharepoint as an automount for Home Directories, everything is fine, but it picks the server.office.domain.com hostname. Picking that works just fine, but that is also the connection that feeds the filesharing. I'd prefer to split that home directory traffic out onto the second ethernet port. So I tried just duplicating the initial connection (since it can't be edited directly in Workgroup Manager) and changing the hostname to the internal one, but I get an error when attempting to log in (the client login screen gives a very helpful "Couldn't login because of an error" error message) and don't see anything in the server logs.
The client machine shows the following line:
Code:
10/20/12 5:27:42.688 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] |
PremountHomeDirectoryWithAuthentication( url=afp://homes.services.internal/Users,
homedir=/Network/Servers/homes.services.internal/Volumes/HomeDirectories/Users/ user123, name=user123 ) returned 45
(added line breaks so it didn't extend off the page)
So it looks like this is failing because the automount isn't in place, but I'm not sure how to work that out either (i.e. how do I add that making sure it uses the internal hostname?).
Any suggestions on getting this to work?
I realize one solution is just to LACP the two ports, but that is a different ball of wax (I may do that later if I get a 4 port ethernet card and performance limitations demand it).

A possible solution might be this.
On ADSLBOX and CABLEBOX configure different subnets for the LAN, e.g.
ADSLBOX: 192.168.1.0/24
CABLEBOX: 192.168.2.0/24
The MEDIABOX gets these static IPs:
ADSL-LAN: 192.168.1.2
CABLE-LAN: 192.168.2.2
On the MEDIABOX, configure the two network interfaces using two routing tables.
The ADSL-LAN routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2 table 1
ip route add default via 192.168.1.1 table 1
The CABLE-LAN routing table
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2 table 2
ip route add default via 192.168.2.1 table 2
The main routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2
# use the CABLE-LAN gateway as default, so general internet traffic from MEDIABOX runs over CABLEBOX
ip route add default via 192.168.2.1
define the lookup rules
ip rule add from 192.168.1.2 table 1
ip rule add from 192.168.2.2 table 2
To test the setup:
ip route show
ip route show table 1
ip route show table 2
I don't know how to persist something like this in ArchLinux using netctl. Might require to write a special systemd unit for it. Above is a working example from a RedHat box at my company.
Last edited by teekay (2013-12-04 07:42:22)

Can I convert a PB 1400's PC card port to a ethernet port for file sharing?

My plan here is to connect a PowerBook 1400cs/133 running OS 8.6 to an iBook G4 running OS 10.4 by means of an ethernet crossover cable, and move my important files (ClarisWorks 4.0 docs and games mostly) to the new computer. But the PB 1400 has no ethernet port! Is there something I can put in the PC card slot that will convert it to an ethernet port?

jpl, Denis, here's my setup:
The PB 1400 is connected to the iBook via a Farallon EtherWave/EtherMac Ethernet PC Card (with a blue arrow, PCMCIA 2.1, PC Card Standard). I have the Farallon software installed and the Farallon extension turned on. A "Farallon EN Card" icon appears on my desktop, and the little light on the cord where it connects to the card is green. I used to use the card to connect to the internet back in the day when the 1400 was my primary computer, so I'm confident it works.
The PB 1400 (name: Ben's PowerBook 1400): AppleTalk, configured to connect via alternate ethernet. File sharing, on. TCP/IP, connected via AppleTalk (Mac IP). I've tried configuring that both "Using Mac IP server" and manually by entering in the iBook's IP address and router address (the 1400 is not connected to the internet). As far as I can tell, Users/Groups is configured; it has "Ben" as "user" and "Guest" as "guest user."
The iBook (name: Ben's iBook G4) is set up basically identical to the way jpl describes his iMac above. Like his, the services panel of sharing on the iBook says "Other Macintosh users can access your computer at afp://x.x.x.6." I also manually entered the iBook's IP address, subnet mask, and router. Under my shared location, under Built-in Ethernet, TCP/IP is configured and AppleTalk is active.
Still, file sharing is not working. When I try to access the iBook from the 1400, I go to the Chooser, click the AppleShare icon, and "Ben's iBook G4" in the file server window. When I select it and click OK, I go to a screen to enter my name (Ben) and password as a registered user. I'm not sure if the password it wants is the file sharing password I set up for the 1400 or the administrator password for the iBook, so I tried them both. I also tried connecting as a "guest." In all cases, after I hit the "Connect" button, I got the error message "The connection to this server has been unexpectedly broken."
No luck going the opposite direction either. When I go to Go: Connect to Server: Browse on the iBook, "Ben's PowerBook 1400" appears in the Network area, but when I select it and hit the "connect" button, I get this error message: "The file server uses an incompatible version of the AFP protocol. You cannot connect to it."

Dynadock U3.0 - Not able to use Ethernet port after Win 8.1 update

Hi everybody,
i am using a Dynadock u3.0 dock with my Vaio SCP 13.
Since I updated my device to Windows 8.1 Update 1 I am not able to use the Ethernet port of the Dynadock.
Before that everything worked fine.
I am not able to reinstall the drivers correctly (tried 7.6m0, 7.5m2). While the driver insaller tries to start i am getting an error message, that the installer is not able to set a bunch of registry Keys (SYSTEM\CurrentControlSet\Services\DisplayLinkGA\D evice1) (till 0). (Image 1)
If i ignore those messages and do install the driver, the Ethernet port will remain uninstalled in the device manager. (Image 2)
If I try to install the driver manually (DisplayLink Network Adapter NCM), Ill get an error message that a driver was found but that the access was denied. (Image 3)
I started the safe mode and could install the driver. But if I reboot to normal mode, the device could not be started.
I also tried to disable UAC and I am logged in as the "real" administrator.
Please find the error messaged attached (in German):
[image 1]: http://picload.org/image/lcalwop/toshiba.png
[image 2]: http://picload.org/image/lcalwoc/toshiba2.png
[image 3]: http://picload.org/image/lcalwlg/toshiba3.png
BTW: If I unzip the installer (7.6m0) and install the *inf for the right ven&dev (4503) it still does not work...
I dont know what to do anymore...

Hi
After Windows 8.1 upgrade, you should also update the Display Link driver/software
This is very important!
The latest driver can be downloaded here:
http://www.displaylink.com/support/downloads.php
Note: the old version should be removed!

Can't login to Mac App store on mac mini. Is it because my ethernet port is fried?

Hi
like many others, I am unable to log in to the mac app store on my mac mini. I get the error message saying "An unknown error has occured". I believe the ethernet port is damaged after an electrical storm, but I can still get online wirelessly. I've read on these forums that the app store verifys the account using the ethernet port. Can anybody confirm if this is the case, is there a workaround that anyone knows of?
I can log into the App store on my laptop fine, just not the mac mini.
Thanks in advance
Paul

This is happening on 2 of my machines. One is OSX Lion, the other OSX Mountain Lion. My personal rig works just fine - all on the same network, all with the same basic configuration. All can log in and out of iTunes, but the two servers can't login via Appstore. My rig and one of the servers even use the same Ethernet driver, so it's not that.
I would seriously doubt your Ethernet card would be working at all if it was indeed damaged by the lightning. The transducers are relatively sensitive, and it would either fry or not. You won't get "intermittent" operation as you have described. Here is a list of all the things I've tried (based on a number of forum suggestions), none of which has worked:
1) Sign out of itunes, sign back in, try to sign in to AppStore.
2) Re-enter information in your account info and save it again (knew that wasn't it but tried anyway).
3) Ran AppStore as root.
4) Using EFIStudio, I got the hex string ID of my ethernet card and specifically reference "device-properties" in the boot.plist. Others have said this works, so you might give it a try -
http://legacy.tonymacx86.com/viewtopic.php?f=169&t=28477
5) Deleted all other ethernet devices to avoid "confusion" of the return.
6) Verified I can get HTTPS returned from NAT device.
7) Used Wireshark to get a packet capture of it working on mine and not working on the other. On the one that doesn't work, all I get is a couple of SYNs to the appstore and then nothing. It was along these lines that I was hoping the "device-properties" would work.
I just thought of something though. If I don't see that ACK at all, it might be sending the packets somewhere else. hmmm. I'm going to hard-code in all HTTPS to be routed to that box and try it just for S&G.
Good luck!

Built-In Ethernet Port Doesn't Show Up In The Network Preference Pane

My ethernet port no longer shows up in the Network preferences pane under Network Status. The status Airport and the Internal Modem are still displayed though. Plugging in an ethernet cable causes my machine to crash; sometimes I get a message that I need to hold down the power button to reboot, and other times command line-like text is displayed on top of whatever was on screen.
The only change I've made to my system since last using a wired connection was installing Security Update 2006-001 on March 1st and OS X Update 10.4.5 on February 14th. After running the 10.4.5 updater, my machine initially refused to reboot. On the first attempt, it played the start up chime, but the screen remained black. The second time, the Apple logo appeared, but the spinning pinwheel never did. The third attempt was successful and my system appeared to be functioning normally.
How do I get my ethernet port to work again?

Does "Built-in Ethernet" show up as a choice in the 'Show:" popup? If so, is it configured as you would expect? For instance, if "TCP/IP" is set to use DHCP, do you have an IP address, subnet mask, etc.? There is an "off" setting for TCP/IP; make sure that hasn't been selected somehow.
There is also an "Assist Me" button that will let you launch the diagnostics app. Does this also crash the Mac? If not, what are the results of its tests?
Also, you may want to do a permissions repair with Disk Utility if you haven't done this since applying the updates.
If you still get crashes, there may be a conflict with a log-in item, particularly if you have any third party ones. (Check that in the "Accounts" pref.) One way to diagnose things like that is by creating a new test account & logging into it. If the problems go away, you can assume a user cache, .plist, or login item is the problem.
If none of this turns up anything, you may need to reinstall the OS. Short of that, you can try downloading the 10.4.5 combo update & running it. It replaces more components than the "delta" update so it just might do the trick. Besides, if you end up having to reinstall the OS, having the combo version handy will save you the time of downloading & installing any incremental updates to get back to 10.4.5.
As always, backup all important files before applying any updates.
Good luck!

Mac Mini Ethernet port gone bad, doesn't show in network preferance pane?

My friend 's Mac Mini was doing fine then he shutdown disconnected everything and brought it over to my house for LAN games. He then couldn't get online through my router. I told him go to his network pane to see what kind of error it was giving, cable errors IP but no internet...etc, and only internal modem was displayed in the list. So I immediately went to his port setting and ethernet was checkmarked. So then I thought well maybe some PMU reset problem so I tried the resets and still not present from the network pane. So then I hooked my external hd to his firewire as a startup drive to eliminate that it just wasn't a software problem and it is still not showing up on network pane. I then skimmed through some online articles and things but to no avail. I just was thinking it was a 5 minute drive from his house to here and he said didn't do anything different from the other times he was here but something must have jarred it or perhaps just a coinseidense that the ethernet port went out when he was coming over. And to top it off he had made arrange for next weekend to sell it to a friend and get a new Intel iMac, which right now has to be put on the backburner until he has a working unit again. Applecare is up so that is out of the question. Any suggestion out there would be appreciated. Or is it just beyond easy fixes and has to either be repaired or keep and save from scratch for a new one?

OMG, guys I feel so dumb the new update to Tiger changed the way network pane worked so that was the whole problem its normal under 10.4.5 so plugged in a good cable and it came up fine go figure right. For being Apple certified for repair I sure looked past such an easy solution.

Airport express and the ethernet port

Since January, I've had my older g/b model of airport express set to "join the network," which is an 802.11n airport extreme connected to my cable modem. Until last week, the ethernet port of the airport express could be used to connect in my DVD player or TV. I could do software updates on the DVD player, and watch youtube on the TV, etc. The connection became slow last week, so I decided to reconfigure the airports. Since then, the ethernet connection to the airport express is no longer recognized.
Please note, although the airport express is not an "n" model, this set-up did work just fine! The DVD or TV was automatically able to display my IP address. The express has a green light, it has no errors in Airport Utility, and AirTunes still works just fine — it's only the ethernet port that has become completely inactive.
Any thoughts?

Not sure how you managed to do this with an 802.11g AirPort Express unless you had it configured to extend the wireless range of the 802.11n AirPort Extreme in a WDS. As far as I know, the ProxySTA (wireless Ethernet bridge) capability is only available with the 802.11n Express.

HT201257 Ethernet Port

My Ethernet port has stopped working. We had some strong winds and my ethernet cable spans accross from a shed to the house. I have my laptop plugged in and it works fine, but when i plug my ethernet cable (cat5e) in, it says the network cable is unplugged.
I ran an AHT and nothing came up as an error, i have done a PRAM reset also.
ANY IDEAS?
I have an imac 24 in early 2009 with 4gb RAM running 10.5.8

Ok,
So
/private/var/run/StartupItems no such file
/Library/StartupItems
in this folder was
/System/Library/StartupItems (EMPTY)
/System/Library/LaunchDaemons
in this folder plus a heap more i couldnt capture 126 in all:
/Library/LaunchDaemons
in this one:

Is there a fix for a dead ethernet port besides a new logic board?

My ethernet port went dead on my IMac. I unplugged the ethernet cable and plugged it into my laptop and it worked instantly. I am still able to connect wirelessly. I bought an apple USB to Ethernet converter and plugged it in. It worked for about 3 days and then it went dead. Once again I was able to unplug the ethernet cable, plug it into my laptop and instantly had a connection. Is there a fix for a dead ethernet port besides a new logic board and if not how do I figure out which logic board I need?
Thanks
Step

This problem baffled me. I kept getting the "ethernet cable unplugged" error after testing my cables good. Was abut to write it off as port gone bad when I found this thread.
The YouTube video reference above fixed my problem. (http://www.youtube.com/watch?v=u1P6X87qArs)
Basically go to SETTINGS/NETWORK. Then highlight your ETHERNET port and click the ADVANCED button. From there click the HARDWARE tab.
Set
CONFIGURE to MANUALLY
SPEED to whatever your ethernet speed is, in my case 1000baseT
DUPLEX - FULL DUPLEX, FLOW CONTROL
Leave MTU at Standard
Hit OK.
Then don't forget to hit APPLY. I didn't do this the first couple of times assuming hitting OK applied these settings. You gotta hit APPLY.
In about two seconds, my Ethernet connected again.
I went back and reset it to AUTOMATIC just to test and after doing so got the cable unplugged error again. So I am leaving it on manual and it's working.

Crio Ethernet Port 'Crashes', Error 42

Similar Messages

Maybe you are looking for