Jump to content

Search the Community

Showing results for tags '10BaseT'.

The search index is currently processing. Current results may not be complete.
  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. We recently acquired a MacBook Pro laptop, running Mac OS X 10.10. I installed the 12.5 client on it, and tried to do a backup, but on the client CP, I saw: "protected by Retrospect, client name: zzzzz (IP xx.xx.xx.xx) (multicast port unavailable)" When I went to the server to "connect" the client, it did not show up, and I had to add it manually - which worked, because I knew the IP. A search on the web revealed no solutions, or other information on this problem. I ended up changing the ethernet connection to the machine, and the "port unavailable" message in the client went away. When I set it up originally, I plugged it into an old 10 BaseT "satellite" ethernet hub that was closest to the laptop. Since it was slow, I ended up switching to a direct connection to the main switch via a longer ethernet cable. The "port unavailable" went away when I connected directly to the switch. Just FYI. It may or may not be interesting to anyone else. Maybe someone else out there is still using older 10BaseT hubs, and is seeing this sort of problem.
  • Create New...