Custom Query (292 matches)
Results (46 - 48 of 292)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#178 |
fixed
|
Name resolution with the Samba Client
|
Silvan Scherrer
|
Herwig Bauernfeind
|
Description |
It appears we are wasting quite some time during connection because of several shortcomings of our client:
The default order of attempts to resolve names is according to smb.conf defaults for Samba:
name resolve order = lmhosts wins host bcast
- First attempt: Try to parse lmhosts file. This is usually not there on the client.
- Second attempt: Try the WINS server. This is usually not configured on the client. Requires 1 sec (measured in client log) to find or timeout.
- Third attempt: This should work on any TCP/IP network.
- Fourth attempt: Broadcast, this is slow anyway and a last resort.
This has several implications:
- the order of attempts should be configurable in the client.
- do we have means to automatically determine the WINS server in the network? (DHCP job!), an entry for that can be added the client's smb.conf.
- the presence of a proper LMHosts file does speed up connection in the current situation.
|
#179 |
duplicate
|
Name resolution with the Samba Client
|
Silvan Scherrer
|
Herwig Bauernfeind
|
Description |
It appears we are wasting quite some time during connection because of several shortcomings of our client:
The default order of attempts to resolve names is according to smb.conf defaults for Samba:
name resolve order = lmhosts wins host bcast
- First attempt: Try to parse lmhosts file. This is usually not there on the client.
- Second attempt: Try the WINS server. This is usually not configured on the client. Requires 1 sec (measured in client log) to find or timeout.
- Third attempt: This should work on any TCP/IP network.
- Fourth attempt: Broadcast, this is slow anyway and a last resort.
This has several implications:
- the order of attempts should be configurable in the client.
- do we have means to automatically determine the WINS server in the network? (DHCP job!), an entry for that can be added the client's smb.conf.
- the presence of a proper LMHosts file does speed up connection in the current situation.
|
#180 |
fixed
|
Samba Client 2.1 cannot read smb.conf
|
Silvan Scherrer
|
Herwig Bauernfeind
|
Description |
When using ndpsmb.dll 2.1 (possibly all 3.3 based client plugins) an eventually available smb.conf is not loaded.
The reason ist that the client (unlike the server) reads the file as if it was only CR and not CR/LF.
Workaround: Change smb.conf for the client from CR/LF to CR.
Temporary workaround on source level (created by diver):
in \lib\util_file.c add line 190 add |O_BINARY to the read() instruction.
|
Note:
See
TracQuery
for help on using queries.