# Etherlite 160 "unexpected network error" **URL:** \ **Category:** Realport\ **Created:** [January 24, 2010, 1:33pm UTC](https://forums.digi.com/t/etherlite-160-unexpected-network-error/7323 "2010-01-24T13:33:39Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![radokac](https://avatars.discourse-cdn.com/v4/letter/r/53a042/32.png) [@radokac](https://forums.digi.com/u/radokac)\ **Post date:** [January 24, 2010, 1:33pm UTC](https://forums.digi.com/t/etherlite-160-unexpected-network-error/7323/1 "2010-01-24T13:33:39Z")
Hello Since few days i`m almost happy owner of Digi Etherlite 160(PN1P050000986-04 C ). I`d likt to use Digi Etherlite 160 to connect to the console with my Cisco routers and switches in my home lab I`ve got problems when i`m trying to connect via Secure CRT to virtual serial COM(pic).(translated=UNEXPECTED NETWORK ERROR) ![](http://img4.imageshack.us/img4/2599/unexpectednetworkerror.jpg) RealPort software has been installed(pic). ![](http://img407.imageshack.us/img407/6233/portsdevicestatus.jpg) ![](http://img213.imageshack.us/i/rlogin2.jpg/) Digi network service is running properly(pic) ![](http://img407.imageshack.us/img407/9194/digirealportservice.jpg) I`m able to Rlogin to Digi Etherlilte(pic) [img]http://img4.imageshack.us/img4/8366/rlogin1.jpg[/img] [img]http://img213.imageshack.us/img213/8809/rlogin2.jpg[/img] I`m able to ping device(pic) ![](http://img213.imageshack.us/img213/1729/pingdevice.jpg) Iits impossible to establish connection via any virtual COM port created by RealPort software Etherlite is directly connected with my PC. IP change, firmware update, everything is ok. but why i cannot use any COM from Digi? What`s wrong ? ---
**Author:** ![Admin1](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Admin1](https://forums.digi.com/u/Admin1)\ **Post date:** [January 25, 2010, 4:24pm UTC](https://forums.digi.com/t/etherlite-160-unexpected-network-error/7323/2 "2010-01-25T16:24:36Z")
I know exactly what’s wrong. In your rlogin output, note that the EL is listening on TCP port 10001. This tells me the Etherlite in question has the old FAS firmware loaded (confirmed by the ver output showing 7.9), not Realport firmware. FAS firmware only works with the obsolete/unsupported FAS driver, so this is why Realport can’t talk to it. Once you’ve loaded Realport firmware on your EL, you’ll notice in the rlogin “sockets” output that the EL now listens on TCP port 771, the TCP port that Realport uses in other words. The EL-160 ver. 1.6 Realport firmware can be found here: [http://www.digi.com/support/productdetl.jsp?pid=2482&osvid=0&tp=2&tp2=0](http://www.digi.com/support/productdetl.jsp?pid=2482&osvid=0&tp=2&tp2=0) ---
**Author:** ![radokac](https://avatars.discourse-cdn.com/v4/letter/r/53a042/32.png) [@radokac](https://forums.digi.com/u/radokac)\ **Post date:** [January 26, 2010, 11:21am UTC](https://forums.digi.com/t/etherlite-160-unexpected-network-error/7323/3 "2010-01-26T11:21:02Z")
Absolute right!!! Thank you 😉 PS. what`s the difference between FAS and Realport firmware ? ---
**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\ **Post date:** [January 26, 2010, 2:11pm UTC](https://forums.digi.com/t/etherlite-160-unexpected-network-error/7323/4 "2010-01-26T14:11:50Z")
The FAS firmware/driver is the original driver and firmware from before Digi International acquired Central Data. After Digi acquired Central Data the RealPort firmware was designed to work with Digi’s proprietary RealPort driver, making FAS obsolete. More information can be found here: [http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=521](http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=521)