Bug 35149 - smbpasswd as user times out
Summary: smbpasswd as user times out
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: samba
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-08 00:36 UTC by Mike Chambers
Modified: 2007-04-18 16:32 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-04-08 05:07:29 UTC


Attachments (Terms of Use)
samba config file incase needed (11.57 KB, text/plain)
2001-04-08 00:38 UTC, Mike Chambers
no flags Details

Description Mike Chambers 2001-04-08 00:36:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)


When running the command smbpasswd as user, it times out and doesn't let 
you change password.

Reproducible: Always
Steps to Reproduce:
1.smbpasswd
2.old pass, hit enter
3.new pass, hit enter
4.confirm pass, hit enter
	

Actual Results:  [reddawg@homer reddawg]$ smbpasswd
Old SMB password:
New SMB password:
Retype new SMB password:
timeout connecting to 127.0.0.1:139
unable to connect to SMB server on machine 127.0.0.1. Error was : code 0.
Failed to change password for reddawg

[reddawg@homer reddawg]$ rpm -q samba
samba-2.0.7-35

Expected Results:  Should let you change password and accept it.


Also having problems connecting to samba from win2000 machine.  Using same 
smb.conf file from RH 7 that worked, now doesn't let you connect to the 
workgroup.  Just mentioned as maybe they are related problems.

Comment 1 Mike Chambers 2001-04-08 00:38:00 UTC
Created attachment 14883 [details]
samba config file incase needed

Comment 2 Bill Nottingham 2001-04-08 01:48:25 UTC
Do you have the firewall set up?

Comment 3 Mike Chambers 2001-04-08 05:04:52 UTC
Yes I am running iptables and port 139 is blocked but only for INPUT, not 
internal.

Comment 4 Mike Chambers 2001-04-08 05:07:25 UTC
Ok, I took out port 139 from iptables and that fixed it.  That should only 
block incoming traffic not internal though shouldn't it?

Comment 5 Bill Nottingham 2001-04-08 20:25:36 UTC
It depends; if you don't explicitly specify to have everything on localhost
accepted, it will also block localhost.


Note You need to log in before you can comment on or make changes to this bug.