 |
 |
 |
|
 |
You are not logged in.
Hi. I hope someone can help. I can't see the Windows network at all despite editing smb.conf and changing the Workgroup to the Workgroup name (in my case MSHOME)
Form a Windows XP machine I can see the eeePC
When I open File Manager in Easy mode, I don't see the Windows network. All I see is NFS Network and when I click on that it's a blank
I have tried static IP configuration as well as DHCP and nothing works.
I can ping the machines on the LAN
I basically am trying to access shared folders in my Landrive.
The only way for me is to use ftp to the Landrive!
Offline
Edit: Bit the bullet and did an F9 Factory restore. I can see the Windows Network now. But strange I could not see any shared machines (despite editing smb,conf to ensure it's the same workgroup)
Only when typing the IP/Shared folder in the address bar could I get to the shared folder.
Last edited by palmdoc (2008-06-07 7:45:23 am)
Offline
Just to throw the cat in, I'm able to see all the PC's on our Windows Workgroup (and transfer files etc) but they can't see the eeePC.
Offline
Offline
hi All
Just a thankyou this info sorted my problem out
Graham
Offline
I need help and I'm hoping someone can help. I've been literally working on this issue all day and no luck. After doing the sudo nano /etc/hosts, I no longer get the "No Route To Host" error. The Workgroup and Computer Name both show up under windows network. Listed under each is my computer name for the Asus, but no file sharing or printer. Does this mean I have to do something from my XP desktop to get the printer to work from here...? If so what? I have sharing enabled on my XP. Please help... 
Offline
This is my HOSTS file. It worked for me, hope it serves as an example. Two other computers on my network also showed up in File Manager after I added the three entries into my hosts file.
192.168.1.130. ASUS. ASUS. # lan2 127.0.0.1. localhost.localdomain.localhost 192.168.1.119 DAD 192.168.1.124 ZAPPA 192.168.1.126 TERASERVE
Last edited by Goldy (2008-07-08 9:30:32 pm)
Offline
I was able to get my EEE PC to see the drives on my Acer Vista laptop, but when I click on a drive icon, it asks for a user name and network password, even though there are no password protected areas on the Acer laptop, not (to the best of my knowledge anyway) on the network.
Offline
Patience!
After struggling on and off for days to get my eeePC 900 to see *anything* on my Windows network, I have just discovered that it takes 5 minutes for my eeePC to connect to my workgroup(s). I think I still have to tweak my hosts file, but finally this is progress!
Offline
WINS is supposed to handle the case where the router is handing out possibly different IP addresses each time the network is taken down and then up again (through DHCP) - has anyone made this work? I suspect full WINS functionality is only on Vista-business and XP-pro systems, not the 'home' ones.
Offline
Folks, I had the "No route to hosts" problem on my home network. I didn't want to try the /etc/hosts hack, as hardwiring a host address in the commonly-used 192.168.0.0 address range seemed like a recipe for trouble if I brought my 900 to another NATted network.
To try and debut what was really happening, I opened the console and used the smbtree command to see what nmbd was using for network names. To my surprise, when it tried to resolve the name of my workgroup, it got the IP address of my router (a Comcast address) instead of the address of my SMB master (which is behind a NAT in 192.168.1.0). Clearly, nmbd was trying to look up addresses in DNS rather than using WINS or broadcast.
I did a little digging in smb.conf, and noticed that samba was configured to prefer the /etc/hosts file over both WINS and Broadcast addresses:
# What naming service and in what order should we use to resolve host names
# to IP addresses
name resolve order = lmhosts host wins bcast
So, I edited smb.conf to read:
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
name resolve order = lmhosts wins bcast host
I rebooted (to restart nmbd) and presto, my workgroup showed up, and I can now mount SMB shares. It tends to be a bit pokey on wireless (I have a 900 so it is 802.11G) but certainly fine for copying files off the SSS to my file server.
Hope this helps - TD
Offline
Thank You Technodad!
Your name resolve order shuffle in smb.conf did the trick on my 1000HD (full desktop). My problem was so bad and inconsistent before that simple fix that my file manager would disappear most times that I would try to open Windows Network! I have lurked and read many threads on windows networking on Linux these past days and you got it!
Thanks - Jim
Offline
technodad wrote:
Folks, I had the "No route to hosts" problem on my home network. I didn't want to try the /etc/hosts hack, ...
# What naming service and in what order should we use to resolve host names
# to IP addresses
name resolve order = lmhosts host wins bcast
So, I edited smb.conf to read:
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
name resolve order = lmhosts wins bcast host
Hope this helps - TD
100s of thanks, this solved my issues.
Stan
Offline
Hi...
i've been reading all these info but i can do nothing..
i set up a windows workgroup called inicioms and under windows xp i can see others computers but not the eee and from the eee i can only see the eee inside the inicioms workgroup. I have a 901 with xandros. Im also new in this and right now i have no idea at all of what to do.
I also read the howto:setsamba on wiki but it was worthless. Actually i did that and the computer appeard just once showing the error "not route to host" and after that i was not able to see my xp computer from the eee any more. Any help???...
the xp computer is connected with wire to router while the eee through wireless to the router.
THANKS!! 
Offline
I am trying to get my eee 901 to see my existing Windows network and vice-versa. I changed the work group name on the eee to match the existing Windows network name. I enabled Windows sharing for the My Documents folder on the eee. I can see the eee from my Win XP machine, but I when I click on the asus machine I get an error message. And the My Docs folder is not included in the list of networked folders on the XP machine. I then shared My Home on the eee and was able to open files on the eee using the XP machine ONCE. Next time I tried to open files using the XP machine, I was back to getting error messages.
I gave up on the Windows end and moved over to the eee and started File Manager. I could then see icons in the right pane with the names WORKGROUP and LIBBEY HOME. LIBBEY HOME is my network. When I clicked on that network, I got this error:
Error connecting to DAVID-OFFICE
No route to host
"DAVID-OFFICE" is one of the computers on the Windows network and runs under XP; no reference to the 2nd computer on the network which is a Vista machine.
Based on advice on the wiki, I turned off the firewall on the XP machine. Clicked on LIBBEY HOME - same results.
So.....I decided to try the fix described by technodad. I opened samba/smb.conf in a terminal window and made the changes described in technodad's post, rebooted, reopened File Manager. Now when I click on the Windows Network I see NO network names listed.
Then I reversed the technodad fix and rebooted. I STILL see no network names.
Surely would appreciate suggestions to (a) regain the ability to see the network names and (b) be able to link to the computers on my network. Tnx.
Note: I posted this earlier today in another older, much longer thread and decided to repost here as this thread is current and a lot shorter.
Last edited by pilotdave (2009-05-04 11:07:15 am)
Offline
Update a day later......
The good news: I can now see my network and the other computers on it. And I was able to install a printer attached to one of the windows computers on the eee.
The bad news: I didn't change anything. And all the print files I've sent to the printer cause a lot of clatter from the printer and no printed page output.
Does it happen that things suddenly start working???? Maybe my 901 is haunted.
Offline
1. on windows machine find your local ip address:
goto DOS prompt (win+r / cmd<enter>) and type 'ipconfig', read IPv4 info for one of the Ethernet adapters, should probly be something like 192.168.xxx.xxx or 127.xxx.xx.xx
2. find windows computer name:
win+pause (for vista) and something like win+pause / system properties / computer name (for xp)
3. set it to hosts on eeepc
on eeepc open terminal (ctrl-alt-t)
type 'sudo nano /etc/hosts'
this is like a notepad, you're editing a text file now, include a new line at the bottom (arrow down, enter)
on this new line include
<ip address><space><windows machine name>
for example:
192.168.1.100 DELL-PC
ctrl-o <enter> (to save)
ctrl-x (to exit the nano notepad)
get back to file manager / windows network / workgroup and your pc should be there.
Yeah, I know this is far from perfect, but i couldnt find a better solution yet.
oh, and btw, If u dont have a fixed ip on PC, u should set one (google it).
Last edited by InterestedParty (2009-08-05 1:20:06 pm)
Offline
