Yeah, this has been answered here:

http://wiki.eeeuser.com/howto:setupsamba

press ctrl-alt-T to get a terminal window
type sudo nano /etc/samba/smb.conf
scroll down to workgroup=WORKGROUP
replace it with workgroup=<windows network>, where <windows network> is the name you made note of on the Windows machine
press ctrl-O to save, Enter to accept the filename and ctrl-x to exit
close the terminal window
open the File Manager again and try to access the Windows network

Then see what happens.

My problem is I have never been able to get the EEE PC to see the other computers on a wired Windows network in two different locations.  I've gone through all of the solutions, Easy mode, Advanced mode, File Manager Administrator, etc.

The funny thing is that all the other computers on the network sees the ASUS and can both copy files from it and to it.  But the ASUS can't see them.

The ASUS correctly sees the Workgroup on the network, but says "Error connecting to DELL.  No route to host."  (Dell is the first PC on the network.)

The other PCs all have shared directories and can see each other.  So I'm stumped.  Some other people have reported similar problems.  I'd be happy to hearof any solutions.

I followed the wiki but still getting error messages "no route to host".

Windows PC can see eee pc's shared folder but not the other way. I'm frustrated.

madhippy wrote:

i had this problem - tried a few things ...

1) try setting host in /etc/hosts
2) disable firewall on windows pc

seemed to work after that - not had time to mess about to see if both bits were necessary mind ...

hmmm...set the host to what exactly?

also: would there be another way to set it up w/o disabling the firewall?

haven't had success with my local network yet. only unidirectional from the win PC to my eee. not the other way around...

OK, Madhippy's first suggestion worked, no need to disable the firewall on the window PC though.

In advanced mode, start menu - applications - system - console

Then I typed sudo nano /etc/hosts

Enter the IP of the computer you want to access, space, and then it's name, CTRL+O to save, CTRL+X to exit.

Then it picked up just fine in my windows network, and even picked up the other computer on that network without having to enter it into the hosts file. Works fine now.

I don't understand why I had to open a terminal just to have it locate the IP of the computer I wanted to connect to. I would have figured that sort of thing to "just work".

Kelbear wrote:

OK, Madhippy's first suggestion worked, no need to disable the firewall on the window PC though.

In advanced mode, start menu - applications - system - console

Then I typed sudo nano /etc/hosts

Enter the IP of the computer you want to access, space, and then it's name, CTRL+O to save, CTRL+X to exit.

Then it picked up just fine in my windows network, and even picked up the other computer on that network without having to enter it into the hosts file. Works fine now.

I don't understand why I had to open a terminal just to have it locate the IP of the computer I wanted to connect to. I would have figured that sort of thing to "just work".

This worked fine for me also - and then managed to also connect to my shared printer - thanks

I have the same problem says "No route to host.".  I've tried to turn off both Windows firewall and AVG control center but the problem still exist.

I have  the stream video playing problem too. I don't want to copy video files to Eee PC but watch them using SMB. But Smplayer doesn't support stream playing.

Madhippy's suggestion worked for me. I ended up listing the IP address, computer name, and workgroup. Then I had to search for the computer before it would show up as a Windows Network option.

Hi Everyone,

I too suffer from this malody.  I can see the eeepc from the other computers on my Network but not the XP computers from the eec.  (no route to host) error.

I would like to try MadHippy's method but I don't quite understand how to do that from the instructions.  I have found the ip address of my host XP cpmputer.  On my eec computer I can get to the below screen after typing
sudo nano /etc/hosts

then I get this on the screen

192.168.2.29     eeepc-virginiaj.WorkGroup          eepc-virginiaj # 1an2
127.0.0.1          localhost.localdomain             localhost

Where do I type the IP address of the host?  Do I replace one of the above lines?

Thanks for all your help

The /etc/hosts edits got me going as well. Just one small thing to add, the computer name in /etc/hosts is case-sensitive. Took me a few tries but I eventually figured that out.

First I had to right-click on Workgroup in File Manager tree and then select Find. Then in the new box Search on Name *. All my computers on the network show up except I could not connect to them. All was well once I copied the exact name (first letter was a capital) from the list into /etc/hosts for one of the machines.

Strange that this originally worked out of the box, I had transfered files off another computer over the wireless network and I have no idea what changed to prevent my ability to connect. There were no configuration changes to anything. Anyway glad it works with firewalls left active.

Thanks for the guidance.

I'm still not able to see the windows box from my eee after completing the etc/hosts fix, i've only moved one step closer, i can now see that my workgroup is indeed called workgroup, but double clicking reveals "one or two of the computers on the network cannot be accessed."


ping from konsole seems useless, but i can access shares from my windows computer.

help please.

Any solution yet with this?  I am having this exact problem, trying to connect to a Windows XP-based network printer (which worked fine out of the box with the eeePC).  The "etc/hosts" trick didn't work for me.  Even turning off my firewall on my XP machine doesn't work.  Any help would be appreciated!