Reply
Regular Visitor
redhawk1942
Posts: 3
Registered: ‎08-12-2012
0

Go Flex time stamping wrong and one computer cannot access it.

Running Windows 7 64 bit have the GoFlex 1TB drive.  It is networked to 3 computers, one desktop and 2 laptops.  It works fine from the desktop and one of the laptops.  On the other laptop, Go Flex doesn't show up right away when I look in my Network folder or in My Computer, although Dashboard shows it is there and connected. Sometimes the drives aren't available for more then 30 minutes. Plus when I save files the time and date stamp are wrong, sometimes a couple of hours or a couple of days. The time on the computer is right and all three of my computers time sync to the same internet time server.

 

Anyone have any ideas or solutions?

 

Thanks

 

Zettabyte
kenji57
Posts: 504
Registered: ‎04-13-2012
0

Re: Go Flex time stamping wrong and one computer cannot access it.

[ Edited ]

Are all the computers on the same Workgroup? If 2 computers connect wthout problems then the problem is with your other laptop. 


If it doesn't show up, instead of waiting for it type    \\goflex_home\    into the file explorer.

 

For the timestamp issue go to server preferences in Seagateshare preferences and set the right time

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For the sake of your own health and sanity, if your data is important to you, keep a second copy on another storage (a backup)
Regular Visitor
redhawk1942
Posts: 3
Registered: ‎08-12-2012
0

Re: Go Flex time stamping wrong and one computer cannot access it.

All computers are in the same workgroup.

The time in Goflex preferences is set to syncronize with the internet server. Plus the timestamp is right is I save a file from the other computers.

 

Zettabyte
kenji57
Posts: 504
Registered: ‎04-13-2012
0

Re: Go Flex time stamping wrong and one computer cannot access it.

[ Edited ]

The time in Goflex preferences is set to syncronize with the internet server

 

No the time is set to synchronize with an internet server, probably Seagate servers and maybe that is your problem.

Try  "Set date and Time from the internet" = No. Unless you live on a boat or a mobile home the time zone doesn't change much.

 

edit: actually I'm a little confused by your posts. before you wrote "Plus when I save files the time and date stamp are wrong". Now you seem to be saying that 2 computers are working fine with the GFH but you are having problems with one laptop. That's probably an issue for a different forum.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For the sake of your own health and sanity, if your data is important to you, keep a second copy on another storage (a backup)
Kilobyte
DavyB
Posts: 17
Registered: ‎08-07-2012
0

Re: Go Flex time stamping wrong and one computer cannot access it.

Which time servers are being used by the client computers, the same?,

 

or is the dodgy laptop using a different timeservice?

 

or does it have a problem with it's clock,

could the frequency of time checks be increased, they may only be daily or 12-hourly 

 

Looks like a problem with the oddball laptop!

~~
iMac7,1, 4GB Ram, Core 2 Duo, 2.4 GHz, OS X 10.8.2
using both GoFlex Home and GoFlex Net
Regular Visitor
redhawk1942
Posts: 3
Registered: ‎08-12-2012
0

Re: Go Flex time stamping wrong and one computer cannot access it.

It's a crazy thing.  All clocks on all computers are synced to the same time service.  The "problem" laptop timestamps all other files, even those saved to external drives hooked to other computers on the network..  Anyway, whatever the problem was. It seems to have gone away although I haven't done anything other then check the clocks. I did notice that there was a Windows 7 update installed recently that "fixed a network problem where sometimes a network printer would disappear". I wonder if that had something to do with it since everything seems to be fie since that update was installed.

 

I still would like to solve the mystery though.