Add Product

Search Results:

Reply
Highlighted
Visitor
Posts: 5
Registered: ‎10-27-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

I have a 2012 MBA and am experierencing the same issue. I'm starting to wish I spent the few extra dollars to buy the one that Apple makes, who seems to care about their customers and plan ahead.

Highlighted
Visitor
Posts: 2
Registered: ‎10-23-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

Same disappointment here.  There's a reason vendors have beta programs.  Seems strange to not be ready, or at least have a statement on compatibility/support for a new OS when it comes out.  Fortunately I just bought mine last week so I can still return it to BestBuy as I got the Apple USB to Ethernet connector for $24.44 on Amazon.  Problem solved for me.  Good luck to others.

Highlighted
Visitor
Posts: 8
Registered: ‎10-28-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

Customers pay good money for a product that is necessary for work and school. With ample time, I can't believe they have just started to work on a new driver. Definitely disapointed after this one. 

Highlighted
Visitor
Posts: 6
Registered: ‎10-25-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

I agree as well.  I am now regretting buying their product.  With the little planning and communication ive seen, i'll be thinking twice in the future.

Highlighted
Visitor
Posts: 2
Registered: ‎10-25-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

My solution was to go buy an Apple branded USB to Etherenet.  That is working for me on a 2011 Mac Book Pro running Mavericks.

Highlighted
Visitor
Posts: 1
Registered: ‎10-30-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

Any word on this issue yet?  Will there be a new Driver release?

Highlighted
Visitor
Posts: 8
Registered: ‎10-28-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

Ye, i'm waiting too. I can't believe it's taking so long and I'll definitely reconsider buying/promoting their products in the future. I would definitely recommend calling since then they may take this matter with more urgency. The more calls the better. 

Highlighted
Visitor
Posts: 8
Registered: ‎10-28-2013

When will a new online driver for the Rocketfish Ethernet-USB adapter be available?

A lot of customers who've purchased this adapter (model # RF-PCC132) for Macbooks have recently installed OS Mavericks on to their computers. Since the driver is no longer compatible with this OS, the outdated online driver provided online no longer works and now many users cannot access the internet. It's been some time now since OS Mavericks has been out yet there is no fix. I was wondering if a Rocketfish representative could assess this issue and provide an expected wait time for a new, working driver to be released.

 

I'd like to stick with this product instead of going through the hassle of returning it and buying a new one that is more expensive, but a working adapter is better than one that doesn't. Any help with regards to this issue is greatly appreciated. 

Highlighted
Visitor
Posts: 1,496
Registered: ‎10-15-2013

Re: When will a new online driver for the Rocketfish Ethernet-USB adapter be available?

Hello everyone,

The engineers are still working on this.  As soon as I get an update, I will pass it on.

Regards,
Jeremy
Rocketfish™ Support

Highlighted
Visitor
Posts: 3
Registered: ‎11-05-2013

Re: Rocketfish USB 2.0 Model: RF-PCC132 no longer working since new Mac OS (Maverick) release

So I've manually configured the network adapter with an IP address/mask/gateway and DNS servers.  The adapter shows "online" and I can ping addresses anywhere I want.  The problem seems to be that the higher OSI level protocols are not functioning properly (ARP, DNS, DHCP, etc).   These protocols have not changed over the last several years it is strange that a mere OS update has caused this issue.  It almost seems like Apple has engineered a way to prevent non-apple derived products from functioning properly.