This really does sound like a name resolution problem. I'm pretty sure that Samba looks at DNS first and then tries the NetBIOS broadcast. If DNS returns a different IP address for bubba than you're expecting that's because your resolving in the wrong domain.

Do you have your own DNS? What kind of network are you on? Work? Home? Public? Private?

Jeremy wrote:
What should I look for in /etc/hosts. Also the main reason I'm doing
this, is to because lin-neighborhood, xfsamba, and nautilus all seem to
look up network computer names through netbios, and netbios isn't
working. I can look at anyone on the network through IP address. The
problem comes in domain name resolution. I can try binding my ip
address, but if I shut down the outside network, it still has problems. I found at the ip address smbclient trys to resolve to, is
anything.com. ????


Jeremy

On Mon, 2003-03-10 at 22:56, Michael Torrie wrote:

On Mon, 2003-03-10 at 09:59, Jeremy wrote:

:

All I can think of is to check the allow & deny statements in your
smb.conf file.  If you aren't allowing the correct hosts, then you'll
get a Connection refused error, I would just allow ALL to test it
out(see if this really is the problem)...


Here is my smb.conf file.


# Global parameters
[global]
workgroup = CONTINENTAL
netbios name = HOMER
server string = Jeremy's computer
security = SHARE
encrypt passwords = Yes
map to guest = Bad Password
null passwords = Yes
os level = 0
[Home]
comment = home
path = /home/jkwest
guest ok = Yes
Besides, If I kill my internet connection, then why does it work. Where smbclient getting the 204.228.229.168 ip address???

Hmm. This sounds like samba is not binding to your outside ip address, but the name bubba is resolving to the outside address. Check /etc/hosts. Also when using smbclient, trying using -I to specify a specific ip address to access.

Michael



Jeremy


I have researched this problem till I'm sick of it, and hope that

someone on this list has fixed this problem before.

If I type smbclient -L "bubba" I get this:

added interface ip=192.192.192.13 bcast=192.192.192.255
nmask=255.255.255.0
added interface ip=216.222.61.18 bcast=216.222.61.255
nmask=255.255.255.0
error connecting to 204.228.229.168:139 (Connection refused)
Error connecting to 204.228.229.168 (Connection refused)
Connection to bubba failed

If I type smbclient -L 192.192.192.11 I get this:

added interface ip=192.192.192.13 bcast=192.192.192.255
nmask=255.255.255.0
added interface ip=216.222.61.18 bcast=216.222.61.255
nmask=255.255.255.0
session request to 192.192.192.11 failed (Called name not present)
session request to 192 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)

If I delete my default route to the internet, so that I have no gw in
my ip routing table, and type smbclient -L "bubba",
then I get this:

added interface ip=192.192.192.13 bcast=192.192.192.255
nmask=255.255.255.0
added interface ip=216.222.61.18 bcast=216.222.61.255
nmask=255.255.255.0
Got a positive name query response from 192.192.192.11 (
192.192.192.11 )
Password:

and then I get the list of shares, yada, yada, yada.

Okay, what is the problem?????? Does anyone have any suggestions? I'll attach my smb.conf file if needed.

Thanks


____________________
BYU Unix Users Group http://uug.byu.edu/
___________________________________________________________________
List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list



____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list


____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to