Network Help

[conholster]

If you're running KDE you can use fish:// only requires sshd to be running on the computer you want to connect too. To connect you simply press Alt+F2 and write into "run command..." box:

Code:

fish://ip.of.target.computer

then you can move as easy as to a usb memory stick.

[janvl]

Hi,

One more simple solution,
install tightvnc on both, you can do filetranfer with that too.

Regards,
Jan

[Jaws]

Sorry for not replying sooner. What a bunch of great replies, neat ideas. I'm thinkin' this here topic may be of interest to others as well. Unless everyone else knows this stuff; than I ain't as nerdy as I thought. 

So I got a choice, what 4 - 5?; decisions, decisions 

I got to pick one, one of these days and just learn it inside out. Probably working in a terminal would be easiest.

One thing I need, is to transfer both ways; each computer will have something the other wants. Time to do some thinking and research.

Cheers

[rnojonson]

I ran across this this morning:  http://ubuntuforums.org/showthread.php?t=191643

Most sites automatically assume a MS network and sharing between an MS machine and a Linux machine. It's not easy to find Linux only network info. Also most info is server oriented and distributed by server wise users. To have desktop user deciphered info for simple connection problems is over looked. This is why I think desktop support (single user and small networks) should be forked out of system administration (more focused on large networks). We think because Linux is scalable all info should apply. In theory yes, in practice no. Caring for a forest is an ecosystem, then there is tending to a single tree or a group of trees in your back yard.

Also check out Synergy a software KVM for controlling multiple networked PCs from one keyboard and mouse.
And check out Guake Terminal, a terminal with an invisibility cloak and one key activation/deactivation (F12).

Unless everyone else knows this stuff; than I ain't as nerdy as I thought.

Relax Jaws, that's it, stretch out with your feelings, we are mostly noobie-wons, all learning the ways of open source.

[janvl]

Hi

one more remark. If you use the gui-tools networking is more complicated then it should be.
They show ALL possible settings, also the ones you do not need.

If you use the settings in the text-configuration-files in /etc
things are really much easier. For Samba there are example config-files
and the simplest is about 10 to 15 lines long.
I have done this on Suse/Debian/(K)Ubuntu it is no big deal.

Samba is extremely flexible you can manage networks from just a few to
several hundreds or thousands of PC's.

Kind regards,
Jan

[janvl]

Just stumbled upon the manual, it is called
Samba3-ByExample.pdf

Google on it and have a look at
example network configurations.

Good luck.
Jan

[Jaws]

Thanks Jan.

I was going to ask if you would hold my hand while I learned Samba a week or 2 ago. But I got real busy, so time constrains prevented me from following through. Problem is, I don't want to start something and then have to put it on hold.

That's for the manual link. I'll try studying up first, try some things and I'm sure I'll get back to you with questions.

Cheers

[PGTips91]

Just stumbled upon the manual, it is called
Samba3-ByExample.pdf

Google on it and have a look at
example network configurations.

Good luck.
Jan

Thanks for that link to the manual, I've downloaded it to study myself. It's a bit daunting at 638 pages but I will try to learn enough to get my home network doing what I need it to.

I did the Google search and I think the manual was the first hit.

Paul