Tompkins, Michael
2015-Apr-21 12:37 UTC
[Samba] smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
The problem is that I don't want it to use the IP address, but to use the
hostname.
Regards,
- Mike
?
?
-----Original Message-----
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of Rowland Penny
Sent: Monday, April 20, 2015 10:38 AM
To: samba at lists.samba.org
Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP address for SMB2
but not NT1
On 20/04/15 15:19, Tompkins, Michael wrote:> Second request ...
>
> Thank you in advance ...
> - Mike
>
>
>
> Sent: Friday, April 10, 2015 2:16 PM
> To: samba at lists.samba.org
> Subject: smbclient 4.0.7 resolves host name to IP address for SMB2 but not
NT1
>
> We are having issues with smbclient 4.0.7 not working to clusters, because
it's resolving the host name ( 'default service =
dev3k1.my.domain.com' in smb.conf file ) to an IP address using SMB2, but
does not do it if is uses NT1( our desired behavior ).
>
> Is there a way to turn off resolving the hostname in either the smb.conf
file or as a command line option to smbclient using SMB2/3 ?
>
> Mike
>
>
Have you tried smbclient -I <ip-address of dev3k1.my.domain.com> service
See 'smbclient --help' for more info
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Rowland Penny
2015-Apr-21 12:44 UTC
[Samba] smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
On 21/04/15 13:37, Tompkins, Michael wrote:> The problem is that I don't want it to use the IP address, but to use the hostname. > > Regards, > - Mike > >You posted: Is there a way to turn off resolving the hostname in either the smb.conf file or as a command line option to smbclient using SMB2/3 ? Using '-I' is a command line option that turns off using the hostname. If this is not what you require, then please be a bit more specific! Rowland> > -----Original Message----- > From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny > Sent: Monday, April 20, 2015 10:38 AM > To: samba at lists.samba.org > Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1 > > On 20/04/15 15:19, Tompkins, Michael wrote: >> Second request ... >> >> Thank you in advance ... >> - Mike >> >> >> >> Sent: Friday, April 10, 2015 2:16 PM >> To: samba at lists.samba.org >> Subject: smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1 >> >> We are having issues with smbclient 4.0.7 not working to clusters, because it's resolving the host name ( 'default service = dev3k1.my.domain.com' in smb.conf file ) to an IP address using SMB2, but does not do it if is uses NT1( our desired behavior ). >> >> Is there a way to turn off resolving the hostname in either the smb.conf file or as a command line option to smbclient using SMB2/3 ? >> >> Mike >> >> > Have you tried smbclient -I <ip-address of dev3k1.my.domain.com> service > > See 'smbclient --help' for more info > > Rowland
Tompkins, Michael
2015-May-12 14:07 UTC
[Samba] smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
This is still a lingering problem with SMB2. It uses 2 different functions to
send the Tree Connect Andx Request for NT1 and Tree Connect Request for SMB2.
The both call internal_resolve_name to resolve the hostname, but for NT1 is
passes the hostname through and for SMB2 it uses the IP address. This is the
issue we're trying to address:
http://blogs.technet.com/b/askcore/archive/2009/01/09/file-share-scoping-in-windows-server-2008-failover-clusters.aspx
I'm sure other people had this issue and resolved it. Either the client has
to be told to send the hostname for SMB2, or something on the server has to be
configured differently so it can accept IP addresses for these configurations.
- Mike
?
?
-----Original Message-----
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of Rowland Penny
Sent: Tuesday, April 21, 2015 8:44 AM
To: samba at lists.samba.org
Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP address for SMB2
but not NT1
On 21/04/15 13:37, Tompkins, Michael wrote:> The problem is that I don't want it to use the IP address, but to use
the hostname.
>
> Regards,
> - Mike
>
>
You posted:
Is there a way to turn off resolving the hostname in either the smb.conf file or
as a command line option to smbclient using SMB2/3 ?
Using '-I' is a command line option that turns off using the hostname.
If this is not what you require, then please be a bit more specific!
Rowland
>
> -----Original Message-----
> From: samba-bounces at lists.samba.org
> [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny
> Sent: Monday, April 20, 2015 10:38 AM
> To: samba at lists.samba.org
> Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP address
> for SMB2 but not NT1
>
> On 20/04/15 15:19, Tompkins, Michael wrote:
>> Second request ...
>>
>> Thank you in advance ...
>> - Mike
>>
>>
>>
>> Sent: Friday, April 10, 2015 2:16 PM
>> To: samba at lists.samba.org
>> Subject: smbclient 4.0.7 resolves host name to IP address for SMB2
>> but not NT1
>>
>> We are having issues with smbclient 4.0.7 not working to clusters,
because it's resolving the host name ( 'default service =
dev3k1.my.domain.com' in smb.conf file ) to an IP address using SMB2, but
does not do it if is uses NT1( our desired behavior ).
>>
>> Is there a way to turn off resolving the hostname in either the
smb.conf file or as a command line option to smbclient using SMB2/3 ?
>>
>> Mike
>>
>>
> Have you tried smbclient -I <ip-address of dev3k1.my.domain.com>
> service
>
> See 'smbclient --help' for more info
>
> Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Reasonably Related Threads
- smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
- smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
- smbclient 4.0.7 fails transfer with STATUS_INVALID_PARAMETER and SMB2 but not with NT1
- smb2 vs. NT1
- Samba client doesn't work SMB2 with MAC 0S 10.9.5