Cannot map network drive to \\bubba\home\jesperw

[jesperw]

Hi Folks,

I am getting error messages ie "access denied" when I am trying to create a drive mapping to \\bubba\home\jesperw, even though I see the home folder in "network".

I have no problems mapping to \\bubba\storage. I am using Win Home Premium x64.

Any solutions or where to start looking?

[Ubi]

the log files?

[Cheeseboy]

Hi,

I haven't got any windows machines to test this with, but here is my assumption:
You will have to click the "connect as other user" link when mapping your drive, and then specify WORKGROUP\jesperw, and then give your bubba password.

If that fails, some log information will help us help you, as Ubi indicated.
You can view the logs from the web interface. Log in as Administrator, then click 'Settings', then 'Logs', then scroll down the dropdown until you find 'log.all' under 'samba'. Scroll to the very bottom and you should see the errors that your failed login attempt has produced.

HTH,

Cheeseboy

[jesperw]

Thanks folks!

Suddenly and magically, Bubba2 accepted my mappings. Bubba was up and running all night and was working this morning. When I came home this afternoon, Bubba did not hand out IP-adresses to LAN-computers and I had to force shutdown. Has been shutting down for 4 hrs now.

Do I dare pull the plug or shall I wait further?

[Cheeseboy]

If you issue the poweroff command or similar on the command prompt, it will never shut down completely.
There is a thread somewhere on these fora about that. The web interface should shut it down though.

You will have to pull the plug sooner or later, hoping for the best...

[jesperw]

Pulled the plug and it seems that my information is untouched, i think. Bubba does not show up in network neighbourhood anymore, so I cannot browse files.

I cannot figure out what is wrong, if it is my config or what, but I think Bubba2 is running sluggishly. Could this be a faulty HD that is causing this? Bubba server never crashed...

[Cheeseboy]

Pulled the plug and it seems that my information is untouched, i think. Bubba does not show up in network neighbourhood anymore, so I cannot browse files.

As I don't know anything about your setup, these suggestions are only that (from guessing):
On your windows machine, launch cmd.exe and:

Code: Select all

ipconfig /release
ipconfig /renew
ipconfig /flushdns

If it still fails, please give us a full description of how your system is setup (i.e. what role the bubba plays in your network).

As to the performance issue, you will have to give us a lot more information than that, and preferably in a separate post.

Best regards,

Cheeseboy

[jesperw]

Thanks Cheeseboy!

Restarted Bubba2 through the web interface, but still didnt show up in "Network Neighbourhood". Tried the suggested ipconfig commands, but without luck. Still cannot map and not visible in "Network".

Running Win 7 Home Premium on a WLAN with a Dlink DIR-655, which used to be the DHCP-server. Now I have introduced Bubba2 as DHP-server. Telia ADSL connected to WAN with a LAN-cable between Bubba2 and LAN-port on DIR-655. Using Bubba as DHCP, server and firewall.

On my PC i am running Telia Internet Security (I guess that is a branded version of F-Secure, but not sure) as firewall on PC and antivirus.

Pls, pls let me know if I have left out any crucial information. All help is dearly appreciated!

[jesperw]

I have also made sure that both Bubba2 and my PC is in the workgroup: WORKGROUP.

[Ubi]

try

Code: Select all

nmblookup -M -
nmblookup -M WORKGROUP

[jesperw]

Hi Ubi,

Tried it in a DOS-window and it did not work, so I used Putty to connect to Bubba. Was not able to log in as admin with Putty, so I logged on as "myself". I really dont understand the response, but I guess this is a way for Bubba to connect to the workgroup? Still not visible in Windows Explorer.

jesperw@bubba:~$ nmblookup -M -
Usage: [-?] [-?fMRSTrAV] [-?fMRSTrAV] [-?|--help] [--usage] [-B|--broadcast BROADCAST-ADDRESS]
[-f|--flags] [-U|--unicast STRING] [-M|--master-browser]
[-R|--recursion] [-S|--status] [-T|--translate] [-r|--root-port]
[-A|--lookup-by-ip] [-d|--debuglevel DEBUGLEVEL]
[-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
[-V|--version] [-O|--socket-options SOCKETOPTIONS]
[-n|--netbiosname NETBIOSNAME] [-W|--workgroup WORKGROUP]
[-i|--scope SCOPE] <NODE> ...
jesperw@bubba:~$ nmblookup -M WORKGROUP
querying WORKGROUP on 192.168.10.255
192.168.10.1 WORKGROUP<1d>
jesperw@bubba:~$

Have I done anything wrong? Anything else I can try?

[jesperw]

Ubi, about the log files, which one do you want?

[jesperw]

Just to be on the safe side, I issued the nmblookup commands as SU as well, but it did not help.

[Ubi]

kinda bizarre that this command works perfectly on my B3. Maybe these alternatives help:

Code: Select all

nmblookup -M "-"
nmblookup -M -- -

then if that gives any output, also add the -R and -S switch (read the man page for nmblookup to see what they do

Another trick that sometimes works is this

Code: Select all

smbclient -L you.windows.machine
smbclient -L your.bubba

and yet another is simply

Code: Select all

findsmb

it should tell you for each machine what it's workgroup is and what it's master browser is.

The log file is in /var/log/samba/

[jesperw]

Hi again Ubi,

First of all: a big thanks for spending time and knowledge on this matter. I am not experienced in Linux and have average+ networking skills, so please bare with me if I am not 100% with you at all times.

I tried the 2 last commands, with this result:

Code: Select all

bubba:/home/jesperw# smbclient -L MINHP-DATOR
bash: smbclient: command not found
bubba:/home/jesperw# smbclient -L bubba
bash: smbclient: command not found
bubba:/home/jesperw# findsmb
bash: findsmb: command not found
bubba:/home/jesperw#

The nmblookup generated this:

Code: Select all

bubba:/home/jesperw# nmblookup -M "-"
Usage: [-?] [-?fMRSTrAV] [-?fMRSTrAV] [-?|--help] [--usage] [-B|--broadcast BROADCAST-ADDRESS]
        [-f|--flags] [-U|--unicast STRING] [-M|--master-browser]
        [-R|--recursion] [-S|--status] [-T|--translate] [-r|--root-port]
        [-A|--lookup-by-ip] [-d|--debuglevel DEBUGLEVEL]
        [-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
        [-V|--version] [-O|--socket-options SOCKETOPTIONS]
        [-n|--netbiosname NETBIOSNAME] [-W|--workgroup WORKGROUP]
        [-i|--scope SCOPE] <NODE> ...
bubba:/home/jesperw# nmblookup -M -- -
querying __MSBROWSE__ on 192.168.10.255
192.168.10.121 __MSBROWSE__<01>
192.168.10.1 __MSBROWSE__<01>
bubba:/home/jesperw# nmblookup -M -- - S
querying __MSBROWSE__ on 192.168.10.255
192.168.10.121 __MSBROWSE__<01>
192.168.10.1 __MSBROWSE__<01>
querying S on 192.168.10.255
name_query failed to find name S#1d

I was getting desperate, and change my workgroup name on Bubba to MSHOME, and suddenly it appeared. MSHOME is NOT the workgroup name on my PC. Can this change trigger a restart of some services on Bubba?