LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 06-01-2009, 07:04 AM   #1
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Rep: Reputation: 16
samba smbclient -L gives NT_STATUS_BAD_NETWORK_NAME


I have two headless RedHat Kernels each running Samba, but I can only get one to work correctly!
This one works:
Code:
root@ecm # testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[dev]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        workgroup = SCORPION2
        security = SHARE

[dev]
        comment = ecm dev user folder
        path = /home/dev
        read only = No
        guest ok = Yes


root@ecm # smbclient -L //ecm
Password: <none>
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Sharename       Type      Comment
        ---------       ----      -------
        dev             Disk      ecm dev user folder
        IPC$            IPC       IPC Service (Samba 3.0.33-3.7.el5)
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Server               Comment
        ---------            -------
        ECM                  Samba 3.0.33-3.7.el5
        TG                   Samba 3.0.33-3.7.el5

        Workgroup            Master
        ---------            -------
        RRDSL                CRAWD11514
        SCORPION2            ECM
And this one not :
Code:
root@tg# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[dev1]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
        workgroup = SCORPION2
        security = SHARE

[dev1]
        comment = tg dev user folder
        path = /home/dev
        read only = No
        guest ok = Yes


root@tg # smbclient -L //tg
Connection to tg failed (Error NT_STATUS_BAD_NETWORK_NAME)


root@tg # smbclient -L //localhost
Password:<none>
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Sharename       Type      Comment
        ---------       ----      -------
        dev1            Disk      tg dev user folder
        IPC$            IPC       IPC Service (Samba 3.0.33-3.7.el5)
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Server               Comment
        ---------            -------
        TG                   Samba 3.0.33-3.7.el5

        Workgroup            Master
        ---------            -------
        SCORPION2


root@tg # smbclient -L //ecm
Password:<none>
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Sharename       Type      Comment
        ---------       ----      -------
        dev             Disk      ecm dev user folder
        IPC$            IPC       IPC Service (Samba 3.0.33-3.7.el5)
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]

        Server               Comment
        ---------            -------
        ECM                  Samba 3.0.33-3.7.el5

        Workgroup            Master
        ---------            -------
        RRDSL                CRAWD11514
        SCORPION2            ECM
What I notice is that the smbclient Master doesnt show any items on tg?!

Any clues?
 
Old 06-02-2009, 03:02 AM   #2
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
I have posted this in the Network Forum as well here. As I am unsure if this is a Network issue, or a Samba Server issue.
 
Old 06-02-2009, 03:04 AM   #3
billymayday
Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Short term bumping and double posting are both no-nos.
 
Old 06-02-2009, 03:07 AM   #4
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
Yep, sorry, thought that it might be ok as I am really unsure if it is a networking issue or a samba issue.

If you or an admin wants to, these bump/comment posts can be deleted.
 
Old 06-02-2009, 04:10 AM   #5
chitambira
Member
 
Registered: Oct 2008
Location: Fife
Distribution: RHEL, Centos
Posts: 373
Blog Entries: 1

Rep: Reputation: 49
you need, in smb.con (G)
Quote:
netbios name = hostname
 
Old 06-02-2009, 04:58 AM   #6
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by chitambira View Post
you need, in smb.con (G)
Code:
netbios name = hostname
Thanks, but I don't have a netbios name field setup on the one that works?
And I thought that if netbios name was not defined it would use the hostname (which is set as I want)?

Anyway, I tried this out, and it didnt help!

Cheers, Ian.
 
Old 06-02-2009, 07:23 AM   #7
chitambira
Member
 
Registered: Oct 2008
Location: Fife
Distribution: RHEL, Centos
Posts: 373
Blog Entries: 1

Rep: Reputation: 49
# ping tg
# dig tg
# ls -al /home/dev

Do you have any samba users on this server???
(smbpasswd -a <username>)

smbd.log ???
 
Old 06-02-2009, 09:10 AM   #8
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
"dev" folder does exist:
Code:
root@tg # ls -al /home
drwxr-xr-x  6 root root   4096 Dec 27 03:46 .
drwxr-xr-x 24 root root   4096 Dec 27 00:01 ..
drwxrwxrwx  3 dev  dev    4096 Dec 27 03:46 dev

root@tg # ls -al /home/dev
total 56
drwxrwxrwx 3 dev  dev  4096 Dec 27 03:46 .
drwxr-xr-x 6 root root 4096 Dec 27 03:46 ..
-rw-r--r-- 1 dev  dev    33 Dec 27 03:46 .bash_logout
-rw-r--r-- 1 dev  dev   176 Dec 27 03:46 .bash_profile
-rw-r--r-- 1 dev  dev   124 Dec 27 03:46 .bashrc
-rw-r--r-- 1 dev  dev   515 Dec 27 03:46 .emacs
drwxr-xr-x 4 dev  dev  4096 Dec 27 03:46 .mozilla
Try connecting locally :-
Code:
root@tg # smbclient //tg/dev1
Password:<none>
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]
Server not using user level security and no password supplied.
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
The smdb.log file gets updated :-
Code:
root@tg # cat /var/log/samba/smbd.log
[1975/12/27 03:55:51, 0] smbd/service.c:make_connection_snum(1003)
  '/home/dev' does not exist or permission denied when connecting to [dev1] Error was Permission denied
Note : the log file does not change when try to access via windows!?

Connect to the other samba server ok :-
Code:
root@tg # smbclient //ecm/dev
Password:<none>
Domain=[SCORPION2] OS=[Unix] Server=[Samba 3.0.33-3.7.el5]
Server not using user level security and no password supplied.
smb: \> ls
  .                                   D        0  Mon Jun  1 17:42:01 2009
  ..                                  D        0  Mon May 28 08:58:07 2001
  fwpackages                          D        0  Mon Jun  1 17:42:05 2009
  .bashrc                             H      124  Mon May 28 08:58:07 2001
  .zshrc                              H      658  Mon May 28 08:58:07 2001
  .mozilla                           DH        0  Mon May 28 08:58:07 2001
  .bash_profile                       H      176  Mon May 28 08:58:07 2001
  .bash_logout                        H       33  Mon May 28 08:58:07 2001

  61757 blocks of size 32768. 3272 blocks available
From the other server, try connecting, 1. via hostname :-
Code:
root@ecm # smbclient //tg001/dev1
Connection to tg001 failed (Error NT_STATUS_BAD_NETWORK_NAME)
2. via IP:-
Code:
root@ecm # smbclient //192.168.0.20/dev1
Error connecting to 192.168.0.20 (No route to host)
Connection to 192.168.0.20 failed (Error NT_STATUS_HOST_UNREACHABLE)
"dig" did not work straight-off, and I didnt search for it.
(I know the date is wrong!)

Last edited by IanVaughan; 06-02-2009 at 09:13 AM.
 
Old 06-02-2009, 10:08 AM   #9
chitambira
Member
 
Registered: Oct 2008
Location: Fife
Distribution: RHEL, Centos
Posts: 373
Blog Entries: 1

Rep: Reputation: 49
from ecm, do;
# ping tg
# ping tg.ipadd.re.ss
# nslookup tg

it looks like tg is not known in the dns. (is your name resolution working ok?)
OR is there is something blocking access to tg from ecm? (iptables??)

Again I will ask, are there any samba users on tg??? (do # smbpasswd -a root lets see)

Lastly, do you have selinux ON on tg? (# setenforce 0)
 
Old 06-02-2009, 11:19 AM   #10
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
ok, many thanks for sicking with me on this....

Typed this, and added a password.
Code:
smbpasswd -a root
host can see itself!
Code:
root@tg # ping tg
PING tg (192.168.0.20) 56(84) bytes of data.
64 bytes from tg (192.168.0.20): icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from tg (192.168.0.20): icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from tg (192.168.0.20): icmp_seq=3 ttl=64 time=0.023 ms

--- tg ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.023/0.027/0.033/0.004 ms
But the hostname might not be in /etc/hosts, remote host cannot ping by hostname :-
Code:
root@ecm # ping tg
ping: unknown host tg
But can see it!:-
Code:
root@ecm # ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=0.360 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=0.362 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=0.349 ms

--- 192.168.0.20 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.349/0.357/0.362/0.005 ms
Never seen this before, but did it anyway :
Code:
root@tg # ping tg.ipadd.re.ss
ping: unknown host tg.ipadd.re.ss

root@tg # ping ecm.ipadd.re.ss
ping: unknown host ecm.ipadd.re.ss
nslookup gave a interesting response :-
Code:
root@tg # nslookup tg
;; connection timed out; no servers could be reached

root@tg # nslookup ecm
;; connection timed out; no servers could be reached


root@ecm # nslookup tg
;; connection timed out; no servers could be reached

root@ecm # nslookup ecm
;; connection timed out; no servers could be reached
Both servers could not resolve themselves or each other!

Now things get interesting!
Code:
root@tg # iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     icmp --  anywhere             anywhere            icmp any
ACCEPT     esp  --  anywhere             anywhere
ACCEPT     ah   --  anywhere             anywhere
ACCEPT     udp  --  anywhere             224.0.0.251         udp dpt:mdns
ACCEPT     udp  --  anywhere             anywhere            udp dpt:ipp
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ipp
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:ssh
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited


root@ecm # iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
When I see "firewall", I start seeing lightbulbs!
But still need help to ensure this is the issue. Ie how to turn off.

I ran the setenfource, I need to read up on selinux and this. I dont think it was ever ran on "ecm" server.
Code:
root@tg # setenforce 0

Before your post I had done some other research, some of which might be of use/interest! :-

findsmb can only see ecm host :-
Code:
root@tg # findsmb
                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.0.1     CRAWD11514    +[RRDSL] [Windows 5.0] [Windows 2000 LAN Manager]
192.168.0.10    ECM           +[SCORPION2] [Unix] [Samba 3.0.33-3.7.el5]


root@ecm # findsmb
                                *=DMB
                                +=LMB
IP ADDR         NETBIOS NAME     WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.0.1     CRAWD11514    +[RRDSL] [Windows 5.0] [Windows 2000 LAN Manager]
192.168.0.10    ECM           +[SCORPION2] [Unix] [Samba 3.0.33-3.7.el5]
The shares listed, on not-working host, shows the share :-
Code:
root@tg # net -l share -S tg
Password:

Enumerating shared resources (exports) on remote server:

Share name   Type     Description
----------   ----     -----------
dev1         Disk     tg dev user folder
IPC$         IPC      IPC Service (Samba 3.0.33-3.7.el5)
Even via IP, the share is there:-
Code:
root@tg # net -l share -S 192.168.0.20
Password:

Enumerating shared resources (exports) on remote server:


Share name   Type     Description
----------   ----     -----------
dev1         Disk     tg dev user folder
IPC$         IPC      IPC Service (Samba 3.0.33-3.7.el5)
From the other server/host, its own shares are listed fine :-
Code:
root@ecm # net -l share -S ecm
Password:

Enumerating shared resources (exports) on remote server:


Share name   Type     Description
----------   ----     -----------
dev          Disk     ecm dev user folder
scorpion2    Disk     scorpion2 drive
IPC$         IPC      IPC Service (Samba 3.0.33-3.7.el5)
But from the remote server/host, it cannot find the hostname (might be hosts as above)
Code:
root@ecm # net -l share -S tg
Unable to find a suitable server
It can ping this IP, but when trying the list the shares :-
Code:
root@ecm # net -l share -S 192.168.0.20
Password:
Could not connect to server 192.168.0.20
Connection failed: NT_STATUS_HOST_UNREACHABLE
Listing the users on the share :
Code:
root@tg # net -l user -S ecm
Password:

User name             Comment
-----------------------------
dev

root@tg # net -l user -S tg
Unable to find a suitable server

root@tg # net -l user -S localhost
Password:

User name             Comment
-----------------------------
dev
nobody

Ok, some more lookup stuff :-
Code:
root@tg # nmblookup ecm
querying ecm on 192.168.0.255
192.168.0.10 ecm<00>

root@tg # nmblookup tg
querying tg on 192.168.0.255
name_query failed to find name tg

Code:
root@tg # nmblookup -A 192.168.0.20
Looking up status of 192.168.0.20
 TG              <00> -         B <ACTIVE>
 TG              <03> -         B <ACTIVE>
 TG              <20> -         B <ACTIVE>
 SCORPION2       <1e> - <GROUP> B <ACTIVE>
 SCORPION2       <00> - <GROUP> B <ACTIVE>

 MAC Address = 00-00-00-00-00-00


root@tg # nmblookup -A 192.168.0.10
Looking up status of 192.168.0.10
 ECM             <00> -         B <ACTIVE>
 ECM             <03> -         B <ACTIVE>
 ECM             <20> -         B <ACTIVE>
 ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
 SCORPION2       <1d> -         B <ACTIVE>
 SCORPION2       <1e> - <GROUP> B <ACTIVE>
 SCORPION2       <00> - <GROUP> B <ACTIVE>

 MAC Address = 00-00-00-00-00-00


root@ecm # nmblookup -A 192.168.0.10
Looking up status of 192.168.0.10
    ECM             <00> -         B <ACTIVE>
    ECM             <03> -         B <ACTIVE>
    ECM             <20> -         B <ACTIVE>
    ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
    SCORPION2       <1d> -         B <ACTIVE>
    SCORPION2       <1e> - <GROUP> B <ACTIVE>
    SCORPION2       <00> - <GROUP> B <ACTIVE>

    MAC Address = 00-00-00-00-00-00

root@ecm # nmblookup -A 192.168.0.20
Looking up status of 192.168.0.20
No reply from 192.168.0.20

root@ecm # ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=0.553 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=0.230 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=0.172 ms

--- 192.168.0.20 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.172/0.318/0.553/0.168 ms




root@tg # smbstatus
Samba version 3.0.33-3.7.el5
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------

No locked files


root@ecm # smbstatus
Samba version 3.0.33-3.7.el5
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------
dev          3742   crawd11514    Tue Jun  2 15:54:44 2009
scorpion2    3742   crawd11514    Tue Jun  2 15:45:02 2009

No locked files
again, thanks for sticking with me! (so far!)

Last edited by IanVaughan; 06-02-2009 at 11:20 AM.
 
Old 06-02-2009, 11:38 AM   #11
chitambira
Member
 
Registered: Oct 2008
Location: Fife
Distribution: RHEL, Centos
Posts: 373
Blog Entries: 1

Rep: Reputation: 49
There obviously is one factor preventing it to work, BUT you have SEVERAL PROBLEMS within your infrastructure which might make troubleshooting very difficult.

One thing that I noted is that you got a firewall ON on tg, but OFF on ecm, turn it off on tg by;
Quote:
# iptables -F
# service iptables stop
then check report back before we move on to next step.
Quote:
root@tg # ping tg.ipadd.re.ss
was supposed to be;
Quote:
root@tg # ping tg.ipadd.re.ss
(meaning)
root@tg # ping 192.168.0.20
sorry for the confusion.
 
Old 06-02-2009, 12:03 PM   #12
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
Thumbs up

It works! Damn who-ever enabled the firewall!
So so many thanks to you chitambira

Disable firewall :
Code:
root@tg # iptables -F
root@tg # service iptables stop
Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: filter                    [  OK  ]
Unloading iptables modules:                                [  OK  ]
Check:
Code:
root@tg # iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Pings, from TG :-
Code:
root@tg # ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=0.030 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=0.018 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=0.015 ms

--- 192.168.0.20 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.015/0.021/0.030/0.006 ms

root@tg # ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 192.168.0.10: icmp_seq=1 ttl=64 time=0.297 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=64 time=0.257 ms
64 bytes from 192.168.0.10: icmp_seq=3 ttl=64 time=0.387 ms

--- 192.168.0.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.257/0.313/0.387/0.058 ms


root@tg # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:DE:4B:E6:20
          inet addr:192.168.0.20  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::200:deff:fe4b:e620/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16246 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11179 errors:0 dropped:0 overruns:0 carrier:0
          collisions:393 txqueuelen:100
          RX bytes:1935367 (1.8 MiB)  TX bytes:2273984 (2.1 MiB)
          Memory:80260000-80280000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2224 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:234015 (228.5 KiB)  TX bytes:234015 (228.5 KiB)

From ECM:-
Code:
root@ecm # ping 192.168.0.20
PING 192.168.0.20 (192.168.0.20) 56(84) bytes of data.
64 bytes from 192.168.0.20: icmp_seq=1 ttl=64 time=0.303 ms
64 bytes from 192.168.0.20: icmp_seq=2 ttl=64 time=0.163 ms
64 bytes from 192.168.0.20: icmp_seq=3 ttl=64 time=0.189 ms

--- 192.168.0.20 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.163/0.218/0.303/0.061 ms

root@ecm # ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 192.168.0.10: icmp_seq=1 ttl=64 time=0.015 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=64 time=0.015 ms
64 bytes from 192.168.0.10: icmp_seq=3 ttl=64 time=0.015 ms

--- 192.168.0.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.015/0.015/0.015/0.000 ms

root@ecm # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:00:DE:4B:E7:38
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::200:deff:fe4b:e738/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11318 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:13 txqueuelen:100
          RX bytes:1600751 (1.5 MiB)  TX bytes:900793 (879.6 KiB)
          Memory:80160000-80180000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:821 errors:0 dropped:0 overruns:0 frame:0
          TX packets:821 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:95402 (93.1 KiB)  TX bytes:95402 (93.1 KiB)
Then from the Windows machine, typed in hostname "\\tg" and share "dev1" showed up!

Quote:
Originally Posted by chitambira
sorry for the confusion
No problemo.


Ok, so now it working, but I still have "SEVERAL PROBLEMS within your infrastructure", would you like to help more to tell me what these are?
I would guess that there are better ways of doing things!
 
Old 06-02-2009, 12:24 PM   #13
chitambira
Member
 
Registered: Oct 2008
Location: Fife
Distribution: RHEL, Centos
Posts: 373
Blog Entries: 1

Rep: Reputation: 49
Glad that you figured it out
Some issues to think about:
-You definately need DNS service in your infrastructure.
-You will do well with a DC
-You will need to figure out how your samba users will be organised (ldap or smbpasswd)
-For security, you will need to disable guest access, meaning when you now have a 'domain', you can then do security = domain
 
Old 06-02-2009, 12:30 PM   #14
IanVaughan
Member
 
Registered: Jun 2009
Location: Brighton, UK
Posts: 49

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by chitambira
Glad that you figured it out
Me? Its all down to you!

Quote:
Originally Posted by chitambira
You definately need DNS service in your infrastructure.
You will do well with a DC
1. No idea how to set one (DNS / DC) up (and thats not a question for you or for here!)
2. Dont know why?


As for access, its a private network, all access is granted!

If you have any links for future reading for me, that would be great!
And perhaps your see a new post one day re DNS/DC setup! lol

Cheers, Ian
 
  


Reply

Tags
samba, smb, smbclient


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
samba & NT_STATUS_BAD_NETWORK_NAME wlfdgcrkz Linux - Software 10 05-19-2009 09:55 AM
samba: NT_STATUS_BAD_NETWORK_NAME sohmc Linux - Networking 7 12-21-2007 11:49 AM
Samba Returns NT_STATUS_BAD_NETWORK_NAME ldmcclatchey Linux - Networking 9 09-25-2007 08:37 AM
smbclient gives NT_STATUS_BAD_NETWORK_NAME - but works with konqueror checkmate3001 Linux - Server 0 09-22-2007 03:00 PM
NT_STATUS_BAD_NETWORK_NAME after Samba 3.0.23 patrokov Slackware 3 07-16-2006 11:56 PM


All times are GMT -5. The time now is 04:41 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration