Bug 428 - Error 1734 after Upgrade from rc2 to rc3
Summary: Error 1734 after Upgrade from rc2 to rc3
Status: CLOSED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Upgrade (show other bugs)
Version: 3.0.0preX
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-10 00:54 UTC by Heiko Garbe
Modified: 2005-11-14 09:29 UTC (History)
0 users

See Also:


Attachments
smb.conf (2.33 KB, text/plain)
2003-09-10 23:40 UTC, Heiko Garbe
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Garbe 2003-09-10 00:54:32 UTC
After upgrading from Samba3.0rc2 to rc3 on my RedHat9 Linuxbox, I cannot access 
the shares anymore.
Everytime I try to list the available shares on the server via net view 
\\servername, I get the following error: Error 1734: \\servername is not 
accessible. The array bounds are invalid.
The same messages appears, when I try to use the shares with the help of my 
WindowsXP-Explorer.
The only way to get a Connection is: net use x: \\servername\sharename
These problems didn't occur with the prior Release Candidate.
When I upgraded with rpm -Uhv samba3.0.0rc3-1.rh9.i386.rpm no errors were 
listed.
Comment 1 Heiko Garbe 2003-09-10 02:22:24 UTC
Now I notices, that the error I described above only occurs, when I enter the 
term \\servername in the Explorer or when I use net view \\servername.
If I enter the string \\servername\sharename in the Explorer then I get access 
to the share.
Comment 2 Gerald (Jerry) Carter (dead mail address) 2003-09-10 07:22:17 UTC
Can you give me some more details?  If you don't feel
ok with attaching config files, logs, etc... to this report, 
you can send them to me directly.
Comment 3 Heiko Garbe 2003-09-10 23:40:01 UTC
Created attachment 136 [details]
smb.conf
Comment 4 Heiko Garbe 2003-09-10 23:42:25 UTC
I looked at four different log-Files when I try to connect to a share using my 
Explorer and the \\servername syntax. Here's what they say:

log.winbindd
[2003/09/11 08:16:45, 1] libsmb/clikrb5.c:ads_krb5_mk_req(293)
  krb5_mk_req_extended failed (Ticket expired)

log.machinename
[2003/09/11 08:16:45, 0] lib/util_sock.c:get_socket_addr(919)
  getpeername failed. Error was Der Socket ist nicht verbunden
[2003/09/11 08:16:45, 0] lib/util_sock.c:write_socket_data(388)
  write_socket_data: write failure. Error = Die Verbindung wurde vom 
Kommunikationspartner zurückgesetzt
[2003/09/11 08:16:45, 0] lib/util_sock.c:write_socket(413)
  write_socket: Error writing 4 bytes to socket 16: ERRNO = Die Verbindung 
wurde vom Kommunikationspartner zurückgesetzt
[2003/09/11 08:16:45, 0] lib/util_sock.c:send_smb(585)
  Error writing 4 bytes to client. -1. (Die Verbindung wurde vom 
Kommunikationspartner zurückgesetzt)

log.smbd
[2003/09/11 08:16:45, 0] lib/util_sock.c:get_socket_addr(919)
  getpeername failed. Error was Der Socket ist nicht verbunden

log.nmbd
nothing

When I use \\servername\sharename, no errors are generated in the logs and I 
can access the share.
Comment 5 Heiko Garbe 2003-09-15 02:10:04 UTC
Today I upgraded to RC4 and everything is fine.
Thank you.
Comment 6 Gerald (Jerry) Carter (dead mail address) 2003-09-15 07:04:18 UTC
closing out.
Comment 7 Gerald (Jerry) Carter (dead mail address) 2005-02-07 09:06:15 UTC
originally reported against one of the 3.0.0rc[1-4] releases.
Cleaning up non-production versions.
Comment 8 Gerald (Jerry) Carter (dead mail address) 2005-08-24 10:18:54 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
Comment 9 Gerald (Jerry) Carter (dead mail address) 2005-11-14 09:29:26 UTC
database cleanup