08-21-2012 08:25 PM - edited 08-22-2012 03:16 PM
Pages 13..14 of the user guide says:
Accessing GoFlex Net Without Using the Pogoplug Service (Mac)
You can access the drives connected to GoFlex Net from the Network window (without using the Pogoplug Web interface). Follow these steps to set up local network access.
1. Select Go from the menu bar at the top of the desktop.
2. Select Network from the menu.
3. Double-click Seagategroup.
4. Locate and then double-click the name associated with your GoFlex Net.
NOTE: Your GoFlex Net name starts with the letters “FADS” followed by the last six alphanumeric characters of its MAC address. This 12 digit address, preceded by “MAC:”, is printed on the label on the bottom of GoFlex Net.
5. If prompted, select the volume for the drive connected to GoFlex Net.
6. If an authentication screen displays asking for a password, click OK (you do not need to enter a password).
The volume is added to your desktop. Double-click the volume to access the devices connected to GoFlex Net.
Sadly, (I know this document was written in 2010) this does not work (for me), since I do not see Seagategroup at step 3, I see nothing other than the goflex home family (GOFLEX_HOME, GoFlexHome, goflex_home and goflex_home_atm) and my HP networked printer/scanner when I open the menu. I know the IPv4 private address is currently 192.168.1.14 and the Mac address etcan
FYI I'm using Mac OS X 10.8 (Mountain Lion) on an iMac, a Netgear DG834G.v2 ADSL2+ Modem/Router (Not gigabit ethernet capable), with the GoFlex Net connected to a GS605.v2 switch (there are several in my LAN), which means the whole of my LAN wiring is Gigabit capable, and is running at gigabit ethernet speed except for those devices that are 802.3 100BASE-TX rather than 1000BASE-TX
PS I also have a 2TB GoFlex Home which is working fine, running Time Machine backups.
Opinion: the Hipserv software works fine, the Pogoplug stuff looks like a Lemon and Seagate dropped the ball (not for the first time) when selecting the embedded software for the GoFlex Net. And I would prefer to use stronger non-PC and definitely not G-rated language here.
My question is as in the subject field, thanks in advance for any helpful advice, please don't get confused between GoFlex Net and GoFlex Home configuration setups
08-22-2012 12:09 AM
Have you activated the device at www.seagate.com/activatemygoflexnet?
Until you do that the device is unuseable.
I had a Goflex net briefly but screwed up the device activation and couldn't do anything with it. By the time I got a reply from Seagate support 3 days later I had already swapped it for a Goflex home.
08-22-2012 03:15 PM - edited 08-22-2012 03:19 PM
Yes it is activated,
was not helped by pogoplug backup causing kernel panics until I got an updated version
the 'seagategroup' option did show up for a short time but its disappeared again, the device names don't seem stable of the set
(GOFLEX_HOME, GoFlexHome, goflex_home and goflex_home_atm), the allcaps flavour comes and goes
I dont see why we have to stump up money for junk software (pogoplug pc - a trial - surely seagate should be providing a code for free to make the trial nature go away) so that you can control and safely eject storage disks
08-23-2012 06:18 AM
I think you may be confusing the GoFlex Home with the GoFlex Net. They are different devices, one using Axentra's HipServ platform, and the latter using PogoPlug's firmware. Obviously the GoFlex Home is better
Jokes aside, the GoFlex Home cannot be registered without access to the internet. Once its successfully registered, you can choose to disable Remote Access in Preferences. I'm guessing you have a GoFlex Home and not Net, since the NetBios name and Samba shares you list specify "Home" and are ones that are provided by the GoFlex Home.
08-24-2012 03:52 AM - edited 08-24-2012 04:11 AM
I'm not confusing them the quoted text is from the GoFlex Net setup user guide, (a poor, minimalist, user Guide about 12 pages compared with)
In my original I did state I have BOTH a GoFlex Net AND a GoFlex Home
I'm having the problem with the GF NET not The GF Home they are both working, the GF NET not as I want and as it can do according to the documentation
I notice that the update from Mac OS X 10.8 to Mac OS X !0.8.1 mentions that it fixes a bug with long SAMBA names, but I'm not on at home on my usual iMac but on someone elses Win 7 machine so cannot check that out yet
08-26-2012 02:25 AM
I don't see the workgroup (a windows term, meaningless in a Mac environment) "SEAGATEGROUP" which appears to be generated by the GF Home.
However the sparse documentation I got with the GF Net suggests I should see "Seagategroup" which if it is being generated in a different character case by the GF Net could cause havoc. Are these servernames case sensitive or not?
I only saw "Seagategroup" fleetingly about 10 hours after installing the GF Home, the GF Net had not yet arrived from Amazon marketplace.
I do now see a "fads999999" (all 9s to hide the last 6 digits of the real mac address) server but cannot connect to it, it rejects guest and any registered user on the network, rejecting all passwords. This server took at least 24 hours to appear.