Bekijk de volledige versie : No ip after samba
Hi all, i have 2 problems:
my wl-hdd doesn't give connectivity anymore thru wireless. I can connect to the wl-hdd, with wep key, but no ip is assigned. It's important to say that the wl-hdd ip (as well as the other ones) is automatically assigned from my router, and before samba setting up all was working properly.
then samba is working but no writing access is allowed, i can only read.
i followed basic samba guide by jono.
anyone could help me?
Hiya Doc,
1) Make sure you gateway address is set in the IP Config page on the Web admin page.
2) Have you set the access permissions on the hard disk directories. If you do a chmod -R a+w <dir_name> this will allow the files to be written. Also make sure you have no read_only lines in the smb.conf file.
Any further problems, post your smb.conf file and I'll have a look.
Cheers
Ade
Hi Ade
my ip comes from the router, and i can't insert gateway, anyway i tried to set it manually, but nothing changed. No lines with read_only are in the smb.conf.
this is my smb.conf
----
[global]
workgroup = MSHOME
guest account = nobody
security = share
browseable = yes
guest ok = yes
guest only = no
log level = 1
max log size = 100
encrypt passwords = no
dns proxy = noserver string = WL-HDD
[Asus WL-HDD]
path=/opt/windows
writeable = yes
browseable = yes
----
I set chmod -R a+w, but it doesn't fix.
At my first trial to write on samba folder, these lines appear on system log:
19:54:53 smbd[115]: [2006/12/20 19:54:53, 0] smbd/nttrans.c:call_nt_transact_ioctl(2516)
19:54:53 smbd[115]: call_nt_transact_ioctl: Currently not implemented.
what do you think about?
A problem with users under windows xp?
How to reset flashfs to default? So i can repeat my steps and verify...
thanks
Quite right, if you're getting IP automatically you can't assign a router address.
If you telnet into the WL-HDD and do a ping to www.yahoo.com or other address does this work ok? I just trying to understand the set up that you're using.
Have you tried an ipconfig /renew from a dos cmd prompt on your windows PC?
If your WL-HDD gets an ip address from the router but the windows PC doesn't it sounds like it's a windows problem. I used to have my network working this way but changed to fixed addresses so I could open ports for VOIP.
As for the Samba config, I think you need 'encrypt passwords = yes', as this is what windows uses.
What do you get if you do a ls -l /opt/windows ?
Also the line 'dns proxy = noserver string = WL-HDD' should be two lines split after the no, but this might be just a paste error.
I think you can reset the flash via the web interface (System Setup/Factory Default), but have never done it myself. All my resets have been accidental.
I would keep trying with what you've got as you're probably quite close to it working.
Let me know how you get on.
Ade
I can't believe!
I tried with another router after restoring flashfs, but nothing.
Many ideas and trials, but nothing. The ap has given ip once in a while, and as soon as I've changed anything, I lose my ip.
Casually i've just tried with my wrt54g, this one is in my parent's house, and i haven't used it for 3 weeks.
Well, no ip with this one too!!! :mad: :mad: :mad: :mad: :mad: :mad: :mad:
Bored!
Now my nod32 is running, but i think the problem is windows as it is (or as it was born!)
Sorry for any mistakes in my english, but i have had it, and i didn't check the post...
Very strange things...
Now wireless is working, also with wep, but as soon as i change something in smb.conf (like workgroup) i lose the ip. A reboot is useless, and i have to reset the wl-hdd pressing the button on its back for 15 sec (until a led starts flashing), then reload flashfs and WLHDD.CFG, and finally hope and pray.
After robooting windows, the router and the asus, i can fix this.
Windows is working with the other ap (it was a software problem), so the problem is the wl-hdd.
Now samba is working, just added "force user = admin" to my smb.conf, that was missing.
Setting chmod didn't solve the problem, because user permission was changed, but not group and other permission. So i realized how that line could be important!
The last problem is the charset. Longer names are with "~". How can i fix this?
Surprise!
While i was writing last post, my pc lost the ip from wireless suddenly...
:confused:
The mix of wep and samba seems to be the cause of losing ip at renewing after leasing time. Now i'm using wireless with mac address access, and it works.
I've just solved the charset problem, it was an error editing post-boot for automounting, so i've replaced the older line with:
mount -t vfat /dev/discs/disc0/part3 /opt/win