Justin Allen
2005-Sep-07 06:53 UTC
[Samba] Cannot Authenticate to Samba Shares after switching laptop from wired to wireless nic.
I have a laptop that I need to be able to connect to my samba shares with its wired connection and its wireless connection. It works fine when connecting from the wired ethernet connection but it stops working once I disable the wired connection and connect to the wireless network (both networks are on the same subnet). The IP address for the wired connection is 192.168.1.112 <http://192.168.1.112> the IP for the wireless connection is 192.168.1.111 <http://192.168.1.111>. The following is from my smb.conf file: [global] passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* obey pam restrictions = yes write list = tjc1027 passwd program = /usr/bin/passwd %u allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> dns proxy = no netbios name = FANGORN writeable = yes delete readonly = yes printing = cups workgroup = MIDDLE_EARTH os level = 1 printcap name = /etc/printcap security = user max connections = 20 max log size = 2000 directory mode = 757 log file = /var/log/samba/%m.log guest account = tjc1027 smb passwd file = /etc/samba/smbpasswd load printers = yes socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 force directory mode = 757 encrypt passwords = yes public = yes wins support = true server string = FANGORN wide links = no force create mode = 757 force user = tjc1027 create mode = 757 pam password change = yes [linux] path = /stuff/linux force directory mode = 757 force create mode = 757 force user = tjc1027 create mode = 757 max connections = 5 directory mode = 757 allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> [documents] path = /stuff/documents force directory mode = 757 force create mode = 757 force user = tjc1027 create mode = 757 max connections = 5 directory mode = 757 allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> The two shares listed above are configured in the exact same way as all other shares on the system. One strange thing I have noticed is that even though the above two are configured exactly the same when I browse to documents it gives me a username and password dialog but when I browse to linux it just gives me a message saying: //fangorn/linux is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The specified network name is no longer available. Yet this same thing works fine on all other systems on the network when I am logged in and works fine from this system when I am using the wired interface. I also noticed that in the logs the 192.168.1.111<http://192.168.1.111>(the wireless interface) log is empty and the 192.168.1.112 <http://192.168.1.112> (the wired interface) log is as follows, yet it seems to work fine from 192.168.1.112 <http://192.168.1.112>. I have also tried switching the IP addresses between the wired and wireless but I get the same behavior no access from the wireless side. [root@FANGORN samba]# cat 192.168.1.112.log [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/11 21:41:39, 0] lib/access.c:check_access(328) [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/11 21:41:39, 1] smbd/process.c:process_smb(1084) [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/11 21:41:39, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/11 21:41:39, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer [2005/07/11 21:41:39, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/15 14:47:12, 0] lib/access.c:check_access(328) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/15 14:47:12, 1] smbd/process.c:process_smb(1084) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/15 14:47:12, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/15 14:47:12, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer [2005/07/15 14:47:12, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/27 20:26:01, 0] lib/access.c:check_access(328) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/27 20:26:01, 1] smbd/process.c:process_smb(1084) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/27 20:26:01, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/27 20:26:01, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 22: ERRNO = Connection reset by peer [2005/07/27 20:26:01, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [root@FANGORN samba]# cat 192.168.1.111.log [root@FANGORN samba]# Any help is greatly apprciated I have been working on this problem for months and have not found the answer yet I was hoping the new version of samba would fix it but no such luck. I have also tried another wireless card with the same configurations and had the same results. I do not have another wired card to try. Both interfaces have 192.168.1.5 <http://192.168.1.5>(fangorn's IP address configured for wins. Also the laptop client is Windows XP Professional SP2 (I know I wish it didn't have sp2 but it came with it). The server (fangorn) is Redhat 9.0 with Samba 3.020. Thanks, Justin
Justin Allen
2005-Sep-07 21:07 UTC
[Samba] Cannot Authenticate to Samba Shares after switching laptop from wired to wireless nic.
First of all I appologize if this is a double post I accidentally sent it yesterday before signing up for the list so I don't know if it went through or not. I have a laptop that I need to be able to connect to my samba shares with its wired connection and its wireless connection. It works fine when connecting from the wired ethernet connection but it stops working once I disable the wired connection and connect to the wireless network (both networks are on the same subnet). The IP address for the wired connection is 192.168.1.112 <http://192.168.1.112> the IP for the wireless connection is 192.168.1.111 <http://192.168.1.111>. The following is from my smb.conf file: [global] passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* obey pam restrictions = yes write list = tjc1027 passwd program = /usr/bin/passwd %u allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> dns proxy = no netbios name = FANGORN writeable = yes delete readonly = yes printing = cups workgroup = MIDDLE_EARTH os level = 1 printcap name = /etc/printcap security = user max connections = 20 max log size = 2000 directory mode = 757 log file = /var/log/samba/%m.log guest account = tjc1027 smb passwd file = /etc/samba/smbpasswd load printers = yes socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 force directory mode = 757 encrypt passwords = yes public = yes wins support = true server string = FANGORN wide links = no force create mode = 757 force user = tjc1027 create mode = 757 pam password change = yes [linux] path = /stuff/linux force directory mode = 757 force create mode = 757 force user = tjc1027 create mode = 757 max connections = 5 directory mode = 757 allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> [documents] path = /stuff/documents force directory mode = 757 force create mode = 757 force user = tjc1027 create mode = 757 max connections = 5 directory mode = 757 allow hosts = 192.168.1.11 <http://192.168.1.11>, 192.168.1.22<http://192.168.1.22>, 192.168.1.111 <http://192.168.1.111>, 192.168.1.112 <http://192.168.1.112> The two shares listed above are configured in the exact same way as all other shares on the system. One strange thing I have noticed is that even though the above two are configured exactly the same when I browse to documents it gives me a username and password dialog but when I browse to linux it just gives me a message saying: //fangorn/linux is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The specified network name is no longer available. Yet this same thing works fine on all other systems on the network when I am logged in and works fine from this system when I am using the wired interface. I also noticed that in the logs the 192.168.1.111<http://192.168.1.111>(the wireless interface) log is empty and the 192.168.1.112 <http://192.168.1.112> (the wired interface) log is as follows, yet it seems to work fine from 192.168.1.112 <http://192.168.1.112>. I have also tried switching the IP addresses between the wired and wireless but I get the same behavior no access from the wireless side. [root@FANGORN samba]# cat 192.168.1.112.log [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/11 21:41:39, 0] lib/access.c:check_access(328) [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/11 21:41:39, 1] smbd/process.c:process_smb(1084) [2005/07/11 21:41:39, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/11 21:41:39, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/11 21:41:39, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer [2005/07/11 21:41:39, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/15 14:47:12, 0] lib/access.c:check_access(328) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/15 14:47:12, 1] smbd/process.c:process_smb(1084) [2005/07/15 14:47:12, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/15 14:47:12, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/15 14:47:12, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer [2005/07/15 14:47:12, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected [2005/07/27 20:26:01, 0] lib/access.c:check_access(328) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0 <http://0.0.0.0>) [2005/07/27 20:26:01, 1] smbd/process.c:process_smb(1084) [2005/07/27 20:26:01, 0] lib/util_sock.c:get_peer_addr(1000) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 <http://0.0.0.0> [2005/07/27 20:26:01, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2005/07/27 20:26:01, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 22: ERRNO = Connection reset by peer [2005/07/27 20:26:01, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [root@FANGORN samba]# cat 192.168.1.111.log [root@FANGORN samba]# Any help is greatly apprciated I have been working on this problem for months and have not found the answer yet I was hoping the new version of samba would fix it but no such luck. I have also tried another wireless card with the same configurations and had the same results. I do not have another wired card to try. Both interfaces have 192.168.1.5 <http://192.168.1.5>(fangorn's IP address configured for wins. Also the laptop client is Windows XP Professional SP2 (I know I wish it didn't have sp2 but it came with it). The server (fangorn) is Redhat 9.0 with Samba 3.020. Thanks, Justin