Vista and file sharing.....

[crispy2010]

Why is so gd hard to simply share files between my home pcs. You have to jump through so many hoops to get it to share, then it takes forever. I perfer vista over xp, but damn, I just simply want to take home video from one machine and put it on another. What a fing pain, if bill gates was here right now.:|

 

[VinDSL]

Ppl were complaining about the lack of security in Windows, et al, so MS fixed it.

If it's so &^%$ hard for legitimate users to 'share files' between PCs, imagine what those poor hackers are going through...

 

[VinDSL]

Originally posted by: crispy2010
I just simply want to take home video from one machine and put it on another. What a fing pain...|

The best way to transfer files between machines is to use FTP protocol!

What I do is install a FTP server on the machine that hosts the files.

My current favorite is Cerberus FTP (*FREE* for personal use)

Install it on your host machine, then use a FTP client (Internet Explorer has FTP built-in too) to transfer the files to the other machines.

FTP is simple, and it works first time, every time - it's the only reason it's still around...

 

[bsobel]

The best way to transfer files between machines is to use FTP protocol!

Wow, just wow. Yes cleartext authentication rocks :roll:

As to the OP, what issues are you actually having, I found file sharing in Vista to be easier than XP. Just make sure both machines are in the Home Location and you have the same named account on both (or have login credentials to one). Things like your public folders should just be working.

 

[doan]

Originally posted by: bsobel

The best way to transfer files between machines is to use FTP protocol!

Wow, just wow. Yes cleartext authentication rocks :roll:

As to the OP, what issues are you actually having, I found file sharing in Vista to be easier than XP. Just make sure both machines are in the Home Location and you have the same named account on both (or have login credentials to one). Things like your public folders should just be working.

The most common problem with file sharing not working is accounts without passwords. As bsobel said you need to have the same named acounts (and passwords) on each system.

 

[Rubycon]

Originally posted by: doan

The most common problem with file sharing not working is accounts without passwords. As bsobel said you need to have the same named acounts (and passwords) on each system.

A third party security account manager that could be accessed by a common super user would be nice for workgroup management. Does such a thing exist?

 

[Nothinman]

A third party security account manager that could be accessed by a common super user would be nice for workgroup management. Does such a thing exist?

You mean a central authentication source like AD?

 

[RebateMonger]

Originally posted by: doan
The most common problem with file sharing not working is accounts without passwords. As bsobel said you need to have the same named acounts (and passwords) on each system

Yeah. People HATE passwords. Everybody does. So they try to use their non-password-protected accounts for file sharing, and Windows doesn't like that, unless you are using wide-open shares in XP Home or Simple File Sharing.

 

[VinDSL]

Originally posted by: bsobel

The best way to transfer files between machines is to use FTP protocol!

Wow, just wow. Yes cleartext authentication rocks :roll:

Heh!

1. 1. We're talking about going across a LAN. Hello?!?!?! You afraid your wife's running a sniffer?
   
   2. FTP offers error CORRECTION, other protocols simply offer error detection. FTP will keep resending until it gets it right!

I can guarantee, if you're passing BIG files across machines using a non-error correcting protocol, you WILL have errors...

Don't believe me?

Move a 1 GB ZIP file across machines using something other than FTP, and test it for integrity - let me know what it says...

Screenies might be in order, not that I don't trust ya!

 

[Nothinman]

2. FTP offers error CORRECTION, other protocols simply offer error detection. FTP will keep resending until it gets it right!

No, it doesn't. FTP doesn't do any integrity checking on the data being passed around.

 

[VinDSL]

Originally posted by: Nothinman
FTP doesn't do any integrity checking on the data being passed around.

Proof?

 

[George P Burdell]

It was a pain to set up file sharing options in the Control Panel, but that was a one time thing. Now I find Vista file sharing to be easy to use.

Heck, I gave my dad a 101 on file sharing across the network at home and he picked it up in 5 minutes.

 

[bsobel]

Originally posted by: VinDSL

Originally posted by: Nothinman
FTP doesn't do any integrity checking on the data being passed around.

Proof?

FTP relies on TCP/IP, thats the level of error correction the protocol has. If you've been told anything different you've been informed incorrectly. If you feel this is incorrect, please feel free to site where in the RFC FTP does what you state. To save you some time, its RFC 959 which directly states " There is no provision for detecting bits lost or scrambled in data transfer; this level of error control is handled by the TCP."

Bill

 

[QuixoticOne]

FTP wow.. now there's a retro suggestion!

If you're going to use something like that, how about something more secure and easy to set up like SCP with or without RSYNC on top of it?

Or even easier for the typical person, just run a bittorrent program on both PCs on your LAN and make sure that you know enough to NOT make the PCs accessable via the full internet while you're doing that.

There have to be a million super easy for a computer novice BT clients out there considering the main audience for such things, and they share folders / files well, and transfer using error detection / correction.

DC++ client, same deal.

http://en.wikipedia.org/wiki/BitTorrent_client

http://en.wikipedia.org/wiki/Azureus
http://en.wikipedia.org/wiki/LimeWire

At least then all you may need to do is poke some holes in your firewall for local LAN based traffic, though the client software may already be 'smart' enough to do that for you though, again, you should ensure that it is only doing it on a LAN scope and not full internet wide.

 

[VinDSL]

Originally posted by: bsobel
FTP relies on TCP/IP, thats the level of error correction the protocol has. If you've been told anything different you've been informed incorrectly.

Nice try...

I'll save you 'Lifers' SOME TROUBLE!

 

[VinDSL]

Originally posted by: QuixoticOne
FTP wow.. now there's a retro suggestion!

Thank you!

K.I.S.S.

 

[Nothinman]

http://www.google.com/codesear...0.1/src/retr.c&start=1

Show me where there's any data integrity checking in fd_read_body or fd_read_hunk.

edit: Fix URL that FuseTalk ate.

 

[bsobel]

Originally posted by: VinDSL

Originally posted by: bsobel
FTP relies on TCP/IP, thats the level of error correction the protocol has. If you've been told anything different you've been informed incorrectly.

Nice try...

I'll save you 'Lifers' SOME TROUBLE!

Re-read what you posted, it directly contradicts what you claim. You linked to an article on FTP restart which deals with lost connections, FTP is no way deals with data corruption. Again, per RFC 959 it provides no bit level error correction.

Your constant corrections while your constantly wrong continue to annoy me.

Bill

 

[VinDSL]

Originally posted by: QuixoticOne
If you're going to use something like that, how about something more secure and easy to set up like SCP...?

Heh!

Been using SCP for years!

Basically, SCP is FTP over SSH...

LoL!

Now... there's something we can argue about!!!

Anyway, use FTP for transferring files across your LAN... end of problem!

Either that, or beat your silly heads against the wall - makes no difference to me...

 

[bsobel]

Either that, or beat your silly heads against the wall - makes no difference to me...

Nice dodge on the fact that your completely wrong in your above post.

 

[Nothinman]

Basically, SCP is FTP over SSH...

Actually SFTP would be FTP over SSH, SCP is RCP over SSH.

 

[VinDSL]

Originally posted by: bsobel
FTP is no way deals with data corruption. Again, per RFC 959 it provides no bit level error correction.

Sure it does!

The only problem is... FTP resends from the point of error, so (if it happens early on) it can double the amount of bandwidth required to send a file.

Is this a problem on a home LAN?

 

[VinDSL]

Originally posted by: bsobel
Nice dodge on the fact that your completely wrong in your above post.

LoL!

I love you, man!

I'm gonna let you *win* one of these days...

 

[VinDSL]

Originally posted by: Nothinman
Actually SFTP would be FTP over SSH, SCP is RCP over SSH.

I know, sweetie!

I just wanted to see if anyone would catch it at 1:30 AM...

 

[Nothinman]

The only problem is... FTP resends from the point of error, so (if it happens early on) it can double the amount of bandwidth required to send a file.

So point out what lines of code in the link I've provided above do that.

I just wanted to see if anyone would catch it at 1:30 AM...

It's 3:30 here.