Can connect to smb://192.168.0.112/share but not smb://NYS/share

Can connect to smb://192.168.0.112/share but not smb://NYS/share

Post by Ric » Thu, 13 May 2004 06:23:07



In Konqueror I get an error if I try to browse the windows network.  
The error is that the network is unreachable.

However while at the smb:// prompt I can type
smb://192.168.0.112/ShareName and pull up a windows share on this
machine fine.  However if I try and enter smb://NYW/Sharename to
connect to the same share it just hangs (NYW is the computer at
192.168.0.112)

I am not sure if this is an issue with my samba config file(the server
side of samba works fine, I can access the linux shares from windows
fine) or if this is an error with my network configuration.

I think this might be a netbios issue.  If I ping "NYW" I get "unknown
host NYW."  However if I ping "NYW.JJ.COM" I get a response.  I am
thinking that I need to resolve that first.  Is that correct?  If so
how do I fix this so that it either appends my domain name to all DNS
lookups or uses netbios to find the machine.

I included a copy of the top of my smb.conf just in case the problem
lies there.

Rich
--------------
# smb.conf is the main Samba configuration file. You find a full
commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SuSE
# Date: 2004-04-06
[global]
workgroup = JJ
interfaces = 127.0.0.1 eth0
bind interfaces only = yes

map to guest = Bad User
security = server
password server = NYS
server string = Samba Serv
domain master = no
local master = no
restrict anonymous = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto

[homes]
comment = Home Directories
valid users = %S
read only = no
msdfs proxy = no
browseable = no

[users]
comment = All users
read only = no
inherit permissions = yes
veto files = /aquota.user/groups/shares/
msdfs proxy = no

[groups]
comment = All groups
path = /home/groups
read only = no
inherit permissions = yes
msdfs proxy = no

[pdf]
comment = PDF creator
path = /var/tmp
printable = yes
print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u '%u' -z
%z
create mask = 0600

[printers]
comment = All Printers
path = /var/tmp
printable = yes
create mask = 0600
browseable = no

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers

force group = ntadmin
create mask = 0664
directory mask = 0775

 
 
 

Can connect to smb://192.168.0.112/share but not smb://NYS/share

Post by Alex Harsc » Thu, 13 May 2004 15:25:36



> In Konqueror I get an error if I try to browse the windows network.
> The error is that the network is unreachable.

> However while at the smb:// prompt I can type
> smb://192.168.0.112/ShareName and pull up a windows share on this
> machine fine.  However if I try and enter smb://NYW/Sharename to
> connect to the same share it just hangs (NYW is the computer at
> 192.168.0.112)

> I am not sure if this is an issue with my samba config file(the server
> side of samba works fine, I can access the linux shares from windows
> fine) or if this is an error with my network configuration.

> I think this might be a netbios issue.  If I ping "NYW" I get "unknown
> host NYW."  However if I ping "NYW.JJ.COM" I get a response.  I am
> thinking that I need to resolve that first.  Is that correct?  If so
> how do I fix this so that it either appends my domain name to all DNS
> lookups or uses netbios to find the machine.

> I included a copy of the top of my smb.conf just in case the problem
> lies there.

> Rich
> --------------
> # smb.conf is the main Samba configuration file. You find a full
> commented
> # version at /usr/share/doc/packages/samba/examples/smb.conf.SuSE
> # Date: 2004-04-06
> [global]
> workgroup = JJ
> interfaces = 127.0.0.1 eth0
> bind interfaces only = yes

> map to guest = Bad User
> security = server
> password server = NYS
> server string = Samba Serv
> domain master = no
> local master = no
> restrict anonymous = no
> preferred master = no
> max protocol = NT
> ldap ssl = No
> server signing = Auto

> [homes]
> comment = Home Directories
> valid users = %S
> read only = no
> msdfs proxy = no
> browseable = no

> [users]
> comment = All users
> read only = no
> inherit permissions = yes
> veto files = /aquota.user/groups/shares/
> msdfs proxy = no

> [groups]
> comment = All groups
> path = /home/groups
> read only = no
> inherit permissions = yes
> msdfs proxy = no

> [pdf]
> comment = PDF creator
> path = /var/tmp
> printable = yes
> print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u '%u' -z
> %z
> create mask = 0600

> [printers]
> comment = All Printers
> path = /var/tmp
> printable = yes
> create mask = 0600
> browseable = no

> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers

> force group = ntadmin
> create mask = 0664
> directory mask = 0775

Hi,

are you using SuSE9.1? If so, there is a bug in the Yast module which
configures the smbclient. In this case, open yast>network>sambaclient and
enter a WRONG workgroup name. This will make you able to browse the Windows
shares in konqueror.
Else:
try smbclient -L 192.168.0.112
and see what your box thinks, the Netbios name of NYS is.

Regards, Alex

 
 
 

Can connect to smb://192.168.0.112/share but not smb://NYS/share

Post by Jan Geertsm » Sat, 15 May 2004 02:29:27



> In Konqueror I get an error if I try to browse the windows network.  
> The error is that the network is unreachable.

> However while at the smb:// prompt I can type
> smb://192.168.0.112/ShareName and pull up a windows share on this
> machine fine.  However if I try and enter smb://NYW/Sharename to
> connect to the same share it just hangs (NYW is the computer at
> 192.168.0.112)

> I am not sure if this is an issue with my samba config file(the server
> side of samba works fine, I can access the linux shares from windows
> fine) or if this is an error with my network configuration.

> I think this might be a netbios issue.  If I ping "NYW" I get "unknown
> host NYW."  However if I ping "NYW.JJ.COM" I get a response.  I am
> thinking that I need to resolve that first.  Is that correct?  If so
> how do I fix this so that it either appends my domain name to all DNS
> lookups or uses netbios to find the machine.

> I included a copy of the top of my smb.conf just in case the problem
> lies there.

> Rich

The netbios names mapped to ip, can be set in the file /etc/lmhosts
otherwise NYW needs to be resolved by a broadcast over the network, and
this is a bit tricky and depends on you other systems too.
setting the domain to jj.com should help to ping NYW
oww and Alex's "smbclient -L localhost" should show you the workgroup
and who is the master on your network.

goodluck jan

 
 
 

1. From:192.168.0.101 TO:192.168.0.xxx VIA:192.168.2.1 ?

Hi,

My home network is configured as follows:  an iMac G3 gets the
Internet connection from dial-up (!) and shares it through its en0
interface on 192.168.2.1 (a static, pre-defined setting on MacOS X
10.4 for sharing an Internet connection).  en0 also has an IP of:
192.168.0.101 as shown below:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::20a:27ff:feab:3692%en0 prefixlen 64 scopeid 0x4
        inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255
        inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
        ether 00:0a:27:ab:36:92
        media: autoselect (100baseTX <full-duplex>) status: active
        supported media: 10baseT/UTP 10baseT/UTP <full-duplex>
100baseTX 100baseTX <full-duplex> autoselect autosel

From en0, a crossover cable goes into a DLink DI-624 router on its WAN
connector.  DI-624 (192.168.0.1) then gives dynamic IPs from
192.168.0.2- 192.168.0.255.  Computers are all able to share their
resources and to go on the Internet.

The problem is that the iMac G3 cannot communicate with the other
machines on 192.168.0.x and I'd like to know if there is a way around
it?

Thanks.

2. DOS overwriting Linux

3. SMB shares will not share on samba

4. How to get lisp to work in emacs with Slackware 1.1.2?

5. SMB, printing over smb, kcmshell smb fail on Red Hat 7.3

6. can't modify migrated openldap accounts

7. Using 192.168.0 versus 192.168.1

8. Apache/Rotate log problems...

9. 192.168.0.0 vs. 192.168.1.0

10. Browsing 192.168.0.23 returns 192.168.0.11, why?

11. Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?

12. NAT Interface 192.168.1.x External 192.168.1.x Possible?

13. Routing Linux 192.168.10.x network to Dlink router on 192.168.1.x network