Am Freitag 16 April 2010 06:01:06 schrieb Günter Kukkukk:
> Am Mittwoch 24 März 2010 20:06:41 schrieb Volker Lendecke:
> > On Wed, Mar 24, 2010 at 02:51:50PM +0100, christoph.be...@desy.de wrote:
> > > while debugging I observed something 'new' the name resolution works
> > > fine on the samba serv
Am Mittwoch 24 März 2010 20:06:41 schrieb Volker Lendecke:
> On Wed, Mar 24, 2010 at 02:51:50PM +0100, christoph.be...@desy.de wrote:
> > while debugging I observed something 'new' the name resolution works fine
> > on the samba server as long as I browse the server 'directly' on the
> > windows ho
On Wed, Mar 24, 2010 at 02:51:50PM +0100, christoph.be...@desy.de wrote:
> while debugging I observed something 'new' the name resolution works fine
> on the samba server as long as I browse the server 'directly' on the
> windows host (\\printserver)
>
> It is not working when I look into a prin
Hi Volker,
while debugging I observed something 'new' the name resolution works fine
on the samba server as long as I browse the server 'directly' on the
windows host (\\printserver)
It is not working when I look into a printerqueue etc on the windows host,
this goes along whith what I see i
On Wed, Mar 24, 2010 at 12:16:27PM +0100, christoph.be...@desy.de wrote:
> oc course I have I even did put thte one in question in '/etc/hosts' but
> with no result :(
Please send a debug level 10 log of smbd when such a client
connects.
Volker
--
To unsubscribe from this list go to the followi
Hi,
oc course I have I even did put thte one in question in '/etc/hosts' but
with no result :(
[printserver] # grep 131.169.214.117 /etc/hosts
131.169.214.117 zitpcx16179.desy.de zitpcx16179
[printserver] # nslookup zitpcx16179
Server: 131.169.40.200
Address:131.169.40.200#53
On Wed, Mar 24, 2010 at 12:02:47PM +0100, Christoph Beyer wrote:
> by the way nmblookup looks fine, at the same time:
>
> [printserver] /global/spool/samba_logs # nmblookup -T 131.169.214.117
> querying 131.169.214.117 on 131.169.56.255
> zitpcx16179.desy.de, 131.169.214.117 131.169.214.117<00>
>
Oh,
by the way nmblookup looks fine, at the same time:
[printserver] /global/spool/samba_logs # nmblookup -T 131.169.214.117
querying 131.169.214.117 on 131.169.56.255
zitpcx16179.desy.de, 131.169.214.117 131.169.214.117<00>
Come on someone must have an opinion on this ?
cheers
chris
Hi,
I changed the samba version from 3.0.x to 3.5.1 and from that moment
something has changed with the nameresolving. The smbstatus mainly sjopws
IP adresses now:
[printserver] # smbstatus
Samba version 3.5.1
PID Username Group Machine
--
