(SOLVED)things that you forget: configure two pc network with a cross-over cable

[T6]

"Are you doing this as a proof of concept or? Why doing it on a live cd?"

i am doing it in the case i need to recover information form a infected machine, i tried friday on a friend's pc with a annoying virus/antivirus stealing system and taskbar

i required to move out of the hard disk some files, over 10 gbs and didn't had enough space on usb devices but had space on my netbook and had the livecd on hand so it sounded as a good idea

in the end i had to do some tricks on windows to make it work while i copied the files and then reinstall machine later to copy back the files, i had to wipe hard disk and create a new partition

"you can always go to the repository through a web browser, download samba-server rpm and install it manually on a live-cd using rpm. Tracking the package dependencies maybe problematic and annoying but its doable as i dont think the package has many if any dependencies"

extremely complicated and won't work since i have a 2010.1

files won't work on older versions of kde4 and too many steps to accomplish a task that i need to do as fast as possible and not always i will be able to have internet access or the rpms available to do it

what i want to do is very simple, have access to a single folder or partition from a second machine, i don't need a local network or anything else, just copy files form point a to point b using a cross patch ethernet cable

[muungwana]

samba ships with two packages, samba-server and samba-client.

samba-client is included in the live cd, samba-server isnt. In your cause what you needed was samba-server on your netbook and samba-client on the live-cd(already included)

In your case,
What you need to do is make sure samba-server is installed and running on your netbook and then you can open konqueror and type "smb://" on the address bar on the live cd and the netbook computer will show up on the list and you will then be able to transfer files from the live cd to the netbook.

Dolphin has a network area too and you can use dolphin to reach a network share on the netbook from the live cd.

When talking about file sharing, it is useful to mention what computer will be a client and what computer will be a server since different packages are used on each end and the live cd ships with packages supporting only one side(client side).

[T6]

"samba-client is included in the live cd, samba-server isnt. In your cause what you needed was samba-server on your netbook and samba-client on the live-cd(already included)"

will try that now

"Dolphin has a network area too and you can use dolphin to reach a network share on the netbook from the live cd"

that was what i was using

thanks for your time and patience

[muungwana]

Go to dolphin's network area on your netbook and the netbook's name should show up if samba-server is installed and running and the firewall is off.

If you have configured folders to be shared, you should also be able to access those shares even from within the netbook since it already has samba-client installed.

Basically, before you start going to the live-cd and start wondering if the connection btw the two computers even works, make sure you can see the shares on the netbook from the network section on the netbook. If the netbook can not see itself and its shares on the network, all remote systems wont either.

[T6]

SUCCESS!

thank you, the key here seems to be the command ifconfig

i will recap here if anyone needs this info

1. loaded pclinux fully updated on one machine and in the other i loaded livecd(both kde4)

2. in the updated machine i had samba-clien and samba-server installed previously

3. in both machines i changed ethernet settings to use as ip 192.168.1.2 and 192.168.1.3(different ip for each machine), both using the same netmask 255.255.255.0

4. in the machine with pclinux installed i created a samba shared folder by right click on a folder/properties and setting shares in the share tab(check samba)

5. be sure to set a workgroup, this can be done in pclinux control center/network sharing/share drives and directories with windows smb

in there click on the samba server/configure/standalone and click on ok, in the next window i created another workgroup but you can leave the one is there, this must be done in both machines so both machines are in the same workgroup

6. after this steps are done you can add more folders there or in dolphin, whatever you find more easy

7. to confirm a point to point connection i used the command ifconfig

in both machines i opened konsole and became root by writing su and pressing enter and then writing root password

then i wrote ifconfig eth0 192.168.1.2 -pointopoint

i wrote the other ip on the other machine but the rest is the same, i specified in the command eth0 because i am using the ethernet card on both machines, i don't know if this step applies for a wireless connection

after this steps both systems still report as not connected or error but i could do ping to each machine so there was connection but not the one system wanted

i opened dolphin and could find the machine that was sharing the folder and could access the files after giving a user and a password i created on that machine in the samba settings under the samba users tab in pclinux control center, this step is possibly unnecessary but i was testing if it was using the permissions i gave(read/write)

this kind of connection is complicated on both os(windows and linux) but on linux seems to be a little more complicated 

[muungwana]

 "ping" responses from both ends of the connection was sufficient to know if the two computers saw each other or not and should have been after step 3.

The rest is basic file sharing over the network using samba, how to set it up is pretty easy and straight forward once you know what to do(isnt everything? )

This seem more complicated that it is because you were trying to solve two problems at the same time and didnt seem to know where one problem ended and where the other started.
I am glad you got it to work.

I am glad you got it to work ...i hate getting involved in threads that do not lead to a happy conclusion.

you know the drill, can you change the title of the thread and add "solved" to it?

[T6]

before i tried to create share i could do ping on both machines and in fact i had samba server installed on the netbook so i still believe that the ifconfig helped but i was using it wrong, i added too many spaces on the command

"This seem more complicated that it is because you were trying to solve two problems at the same time and didnt seem to know where one problem ended and where the other started"

in fact i did but as i said, things that you forget  

"you know the drill, can you change the title of the thread and add "solved" to it?"

no, i don't, please explain    

thank you  

i was doing some extra research about something mentioned earlier in this post, about the capability of recent hardware to do cross-over connection and supposedly any switch can do it but in direct connection between two pcs i never could do it

[wedgetail]

T6

"the drill" 

You go to your original post, or your first post.  Use the Modify field in the right hand side.

Then you can edit your subject title to include [solved] or similar then anyone can see the thread had a concluding finish.

[T6]

i like more (SOLVED) because some keyboards won't make the [] properly