05-07-2012 04:02 PM
Got this item a couple of days really I have I think done everything I can think of trying to get the
'thing' to register with the seagate server
using a belkin router
done portforwarding ,tested the right ports are open, UPNP , using the web interface it just will not register, this device certainly tests your patience
any ideas what to try next ? or just return it and move on....
Your GoFlex Home cannot reach seagateshare.com. The Configuration Wizard cannot continue.
05-08-2012 11:47 AM
Known issue with some models of Belkin routers. We're working on producing an updated firmware that contains a work-around to the Belkin issue so you can re-flash your GoFlex Home with it(unless you decide to upgrade your router). I'll update this thread as soon as the update is ready.
05-24-2012 08:40 AM
First off, I'd appreciate any help or suggestions anyone has, please and thank you in advance!
I've just got my first Seagate GoFlex Home and spent most of the past couple of days on and off, trying to get it installed and initially working, to no avail. I've tried just about everything I've read about on this forum and others, as well as the official instructions. (more obvious culprits in my case include MAC address filtering and firewalls, disabling didn't seem to help)
As with several other posts that I've seen here, my GFH appears "good" with the solid green and white light(s), but will NOT get to the point where it has an IP address from my router's DHCP.
THIS is my direct question for THIS thread: can anyone attest to whether or not THIS NAS product SHOULD work with my Belkin N150 F9K1001v1 router (firmware F9K1001_WW_1.00.12). If NOT, the GFH probably goes back.
At some point, I upgraded the router firmware; from v.08 to v.12 (as above); v12 "changes" mentioned "fixed issue preventing UPNP media sharing on Windows..." so I thought that sounded good; but still no love.
Also: In this router's "Security Log" I can see that it appears to be ATTEMPTING to give the GFH an IP, logs the GFH's MAC, but NEVER shows up in the router's list of DHCP clients ... (there's another thread here from a Douglas Wagner/Illydth w/similar issue, LOTS of technical info., very little response/help)
Again, I'm hoping someone here has used this router successfully and/or replaced it or upgraded it and gotten the GFH to work ...
A couple of things that I've read about (here & elsewhere) that I have NOT yet tried: 1) connecting the GFH base DIRECTLY to my PC via. ethernet (without the router), and 2) GFH firmware reflash (or upgrade) ...
I have to admit, that I *did* buy this slightly impulsively at a local "discount" store (significant discount over other local electronics stores, online); it was obviously unopened/unused, but appeared to have been dropped at some point - an INTERNAL box (for base) was crumpled a little; however, there are NO markings or indications of damage to anything, and I'm thinking that if there WERE, I shouldn't expect to get the "normal" solid green & white (looks "blue" to me) lights. The real downside of this purchase is, I only have a couple more days to return it for refund, so I'm getting stuck.
Thanks again in advance!
I'm thinking of replying to other threads here, on specific topics, such as "resetting" (I don't appear to get ANY response from reset button) ... And, in the meantime, I'll probably go through the whole routine again, disable every router security feature I can find, etc.
05-24-2012 03:46 PM
Well, at this point, I'm thinking strongly of taking the GFH back for a refund ...
I've tried everything including plugging it directly into my PC via. ethernet (which actually WORKS as far as it goes) ...
AND disabling every bit of "security" that I can find on my router. (followed by every other procedure to connect a couple of times)
When plugging the GFH into the PC via. ethernet, it shows up in the Network devices, and you CAN access it by IP.
Under "Network" (Windows 7 Home Premium 64bit), it shows up as a "Media Device" named "GoFlex Home:UPNP-AV" and it's "Device Webpage" is set to "http://169.254.6.43/dlna.php" and when accessed, shows a text label "Friendly Name:" followed by a text box pre-populated with the device name, and underneath is a button labelled "Submit Query" - when clicked, appears to do nothing at all ...
If I manually enter the "bare" IP address into a browser, it gets: http://169.254.6.43/admin/wizards/setup for a moment, then shows: "Your GoFlex Home cannot reach seagateshare.com. The Configuration Wizard cannot continue."
I then figured it must need Internet access (problematic since the GFH has the PC's ethernet port), so I enabled the PC's wifi adapter, and connected to the router, on the Internet, no problem. However, with the GFH IP as above, same error ...
So ... The final two options that I see to try are:
1) go ahead and reflash here:http://support.GoFlexHome.HipServ.com/en/reflash/i
2) unplug the GoFlex Desk drive from the GFH dock, try plugging the standard SATA connectors to a cheap USB-to-SATA/IDE adapter that I have. I don't really see a point to this right now; I paid a good price for a NAS setup, but only a so-so price for a 2TB SATA drive of otherwise unknown specification ...
Also, in reference to the reflashing: the reflash link above shows version 2.7.1 ...
The "GoFlex Home - Firmware Release Notes" page http://knowledge.seagate.com/articles/en_US/FAQ/21
shows the latest as: "Firmware version 2.5.3: 188.8.131.527 Released August 2011" ...
Now, the "reflash" version above contains files dated from 12/10/10 to 5/17/12 (latest: hipserv2_seagateplug-20120508.ubi).
Also, there's another version referenced in a message on this board: "2.6:184.108.40.2062: 1.2.340" from mid-December 2011 ...
That seems a bit odd ... Not to mention the fact that all of the "update firmware" or "check your firmware version" assume that you're already setup in the first place!
Sigh. This stuff ought not to be THIS difficult ... Now I wonder, with all of the different things I've tried, what minute permutation might I have missed to cause it to fail as usual, OR is it just that my ROUTER doesn't support it somehow ?! (it DOES say it supports UPnP but not much configuration options just enable/disable) ...
If anyone's actually READ another long post, thank you! If you have any ideas, please let me know, I'll pretty much try anything if I haven't already.
05-24-2012 03:49 PM
Any update on this so far in the past couple of weeks ?
Any specific information as to WHICH models of Belkin have a "known issue" and if some do not ?
05-24-2012 08:46 PM - edited 05-24-2012 08:54 PM
Hi Mike, I would recommend getting a refund while you can.
When it works the Goflex Home is fine, but when you have troubles it can be a real pain sorting them out and unless you like a challenge there are better options.
Many users find that It is not "simple setup" as advertised. It is absolutely essential that you have an internet connection to register the device otherwise it is completely unuseable as there are no default user accounts. Does it mention that on the box?
It is forever dependent on Seagate servers for remote access (and only gosh and Seagate know what else). Unlike my Netgear router, which I can access remotely (assuming I know the external IP address) without getting Netgear's permission every time, the Goflex device always has to check with Seagate first.
This is sort of understandable if you don't have a static IP address and you want to send links to your friends to share your photos or whatever, but how many people do that? Isn't that what facebook, google+ and flickr are for?
Remote share should be an option and the majority(?) of people who just want a NAS for their own use should be able to just plug it in and use it and avoid all the associated complications.
On the other hand, I seem to have tamed my Goflex and it is now fine as a NAS, remote access is an occasionally useful novelty and dlna works OK with my devices.
I used to leave it turned off for long periods because it would often disconnect from the network and I'd have to reboot it. After updating the firmware the connection is pretty robust but now the drive is running more than I would like, so I'm not sure how long it will last.
Edit: apparently we can't write "gosh" in this forum, even appropriately capitalised and in context (what are we 8 years old?) but it is OK to have a user name of "**bleep** you" http://forums.seagate.com/t5/user/viewprofilepage/
05-24-2012 10:10 PM
Score one for "Factory Reflash" ... http://support.goflexhome.hipserv.com/en/reflash/i
After getting down to what I considered the most drastic measure, I dug up my smallest flash drive and re-flashed the GFH.
Lo, and behold, the SOB worked exactly as intended! The setup detected the GFH (actually, since I'd already tried the Windows install, it was lurking in my System Tray, jumped up and found the GFH during the post-firmware-flash reboot!) etc., it now shows up in my router's DHCP client list, and it has "drive" access in Windows!
I have NOT tried SeagateShare.com or anything other than just copying a large file to the GFH and my FreeAgent USB drive just to annoy myself w/the comparison: PC to GFH: ~10 MB/s, PC to FA-usb: ~22 MB/s ...
Of course, I actually expected something of the sort, since I know that my cheap router is NOT "gigabit" as is my PC and the GFH; I'll probably try (tomorrow) plugging the GFH back directly to the PC just to try it w/out that "fast ethernet" router throttling the two gigabit adapters. And of course, NOW I want a "gigabit" router to go with !
At this point, I'm not sure what else I can do to "test" the unit, and/or the actual drive itself, except USE it as much as possible.
Thank y'all, and good NIGHT!
05-25-2012 05:56 AM
Sorry I missed this post Mike,
Yes, we had to do a firmware update for these Belkin routers(The N150 is one of the known-problem ones), they do some funky stuff with the MTU's, so we had to tell the GoFlex to ignore them and now they can get an ip. The 2.7.1 update was released last week just because of these routers Glad you found our support pages and managed to fix it yourself. By the way, the Seagate support call center is supposed to be aware of this update and be able to point you to it! If this wasn't the case, let me know.
07-01-2012 09:54 PM
just read with interest the issue of IP addresses and problems with belkin routers. Ive just spent very much time trying to work out why my BalckArmor NAS 220 would not find a DHCP IP on my particular router. Its not belkin but that is not the point.symptoms appear to be similar.
i tested NAS 220 on TWO totally seperate networks. with at least 6 different PC's. using internet explorer 7, 8 and firefox. although both networks using the same model router. one that ive been using many many many of in many of nmy customers installations and therefore ive been using for about 4 or 5 years i think. never a glitch. never a problem. even the slightest.
originally i was tempted to set up and test the seagate nas on a THIRD network of a totally different brand router. but thought that in the end it HAS to work on my normal network at home so i can stream DLNA stuff and so on.
the same router in the test lab here has been found to work with several devices which use those discovery type programs including Stardot Technologies internet cameras, Hava video streamer, networked media players like the Snazio SZ1350, Snazio Tera NAS Raid drive, Ovislink NAS drive, a "no brand" NAS drive, a panasonic blue ray recorder with dlna server, a sony ps3 which i stream dlna from a pc running ps3 server software thru the router and ethernet over mains to the ps3 LOL... and every conceivable pc weve ever plugged into it including win95,98,xp,win7 etc. Never had a problem of any device such the ps3 or pansonic media player for example finding a DHCP ip address and then being able to access internet thru my beloved router
BUT for some reason the NAS 220 FAILS to pick up a DHCP IP address!
Today i completed my final testing. heres my rather interesting test results:
hooked the nas up on our fixed IP WAN. works ok
set the nas to FIXED 192.168.123.234 and connected to my router. works ok
set the nas to DHCP and connected to my router. router sees the nas. allocates DHCP IP 192.168.123.119 but nas fails
set the nas to FIXED 192.168.123.119 and connected to my router. works ok
set the nas to DHCP and connected to different model of same brand router. fails
set the nas to DHCP and connected to another brand router thats 192.168.1.1 base address. works ok
Tried setting my router to 192.168.123.1 base address. nas fails
When it works the discovery software,pings and browser all work.
When it doesnt work then discovery software, pings and browser all fail.
So it looks like the nas doesnt like my brand of router DHCP. But nas is happy using FIXED IP anywhere even in both the Reserved or DHCP 192.168.123.x range.
When the NAS is set to DHCP my router ALLOCATES a DHCP IP ok and even shows the nas hostname in its DHCP clients list. but the nas just does not seem to ACCEPT it. Cant ping the nas. pretty dumb really.
Maybe an MTU problem ?
The NAS Firmware has been upgraded to 2000.1231 and does not work on DHCP
My router DHCP base and gateway and dns address is 192.168.123.254
so....do u have a DHCP firmware fix for the NAS 220 ?