Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to access to SuseLinux7.3 server from Win98 Client

Status
Not open for further replies.

65

Technical User
Feb 5, 2002
47
US
Hi,

I've currently set up a LAN (1 Suse Linux7.3 server and the other is Win98 client). Everything is up and running smoothly. The IP network connectivity works fine when using ping command. However, When I tried to log on my client then access to the server is denied.

One more thing I wanted to mention it to you is:
when I tried listing the shares available on my server by issuing this command:

smbclient -L denver

(denver is my hostname)

then the error message appeared:

added interface ip: 192.168.0.1 bcast = 192.168.0.255 nmask = 255.255.255.0
session request to denver failed (not listening for calling name)
session request to *SMBSERVER failed (not listensing for calling name)


my samba configuration is

security = user
encrypt passwords = yes

Please help.

Thanks in advance
th
 
You may want to post the entire [global] section of your smb.conf file. Also, have you read the docs that come with SAMBA? I'm not sure where Mandrake puts the SAMBA docs, but under RH 7.2, they are in /usr/share/doc/samba-2.2.2

There is some good information in those doc's about properly setting up SAMBA. Bruce Garlock
bruceg@tiac.net
 
Hi,

I imagine that is because 'denver' may be the tcp/ip hostname but is not set as the netbiosname. You would need to have a line like this in your /etc/samba/smb.conf (or wherever smb.conf is on Suse) :

netbios name = denver

Then restart the samba service..

To check if its lisening for connections you can do (as root)

# /usr/sbin/lsof -i TCP:139

You should see samba listening on that port.

Hope this helps
 
Hi ifincham,

Thanks for your response. I do appreciate it.
I did assign netbios name = denver

and follow your instruction to check if its lisening for connections

# /usr/sbin/lsof -i TCP:139

smbd 15914 root 10u IPv4 159985 TCP *:netbios-ssn (LISTEN)

It does not work.

Hi Bruce,

Thanks for your reply. I do appreciate it.
I wanted to post my entire global section but it is very time consuming to type them all in. I did try to copy smb.conf file from my samba server to a floppy disk ,but was unable to view it on my Wins XP. Please help me how to transfer smb.conf file so I can be able to post the global section.

Thanks

Lenka
Thanks for your help.
 
Hi,

Sounds odd because samba is clearly listening as it should on tcp port 139. Does it make a difference if you explicity add the IP address that samba is on :

smbclient -L -I 192.168.0.2

Also, presumably you set up the smbpasswd file ?

Regards
 
Hi,

As you suggested, I did replace denver with samba server ip address
smbclient -L 192.168.0.1

(denver is my hostname)

then the error message appeared:

added interface ip: 192.168.0.1 bcast = 192.168.0.255 nmask = 255.255.255.0
session request to 192.168.0.1 failed (not listening for calling name)
session request to 192 failed (not listening for calling name)
session request to *SMBSERVER failed (not listensing for calling name)

Knowing that both the share and user nodes require the smbpasswd file, which contains the LanManager and NT password hashes for each user who will be accessing the Samba server. So, I did assign smb passwd file : etc/samba/smbpasswd (this is a correct path on my system).

Please direct me whatelse I need to do.

Thanks alot

Lenka
 
HI
Here is my global section setup

# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2002/02/22 16:01:17

# Global parameters
[global]
workgroup = COLORADO
netbios name = DENVER
encrypt passwords = Yes
map to guest = Bad User
passwd program = /bin/pwd
username map = /etc/samba/smbusers
password level = 10
username level = 10
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
character set = ISO8859-15
domain logons = Yes
os level = 64
preferred master = True
domain master = True
dns proxy = No
kernel oplocks = No
valid users = glewis
printing = lprng

[homes]
comment = Home Directories
read only = No
create mask = 0640
directory mask = 0750
browseable = No

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

Thanks
Lenka
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top