name resolution across subnet bounderies

[Bill Moran]

Andreas Schuldei wrote:
> 
> I do get problems with name resolution accross subnet bounderies.
> I have a working and wins server and to demonstrate the problem I
> paste the debug output of

> wins_srv_died(): WINS server 192.168.4.3 appears to be down.

You're WINS server doesn't appear to be working.

> mount /smbhome/
> opts: uid=1000
> opts: gid=1000
> mount.smbfs started (version 2.2.2debian-2)
> added interface ip=192.168.6.2 bcast=192.168.6.255 nmask=255.255.255.0
> resolve_lmhosts: Attempting lmhosts lookup for name Tri-st-s001<0x20>
> getlmhostsent: lmhost entry: 192.168.4.2 TRI-ST-S001
> Connecting to 192.168.4.2 at port 139
> 4873: session request ok
> 4873: session setup ok
> 4873: tconx ok
> smbfs: failed to load nls 'cp437'

This doesn't solve your WINS problems.

> wins_srv_died(): WINS server 192.168.4.3 appears to be down.

Again, the WINS server doesn't appear to be working.

>    wins support = no
>    wins server = 192.168.4.3

This sets this machine to NOT be a WINS server, but get WINS info
from 192.168.4.3. Is that what you intended?
You need to check 192.168.4.3 to find out what's wrong with the
WINS server and correct it. Could there be a firewall blocking WINS
traffic? Can you verify that the WINS server is even started on this
machine? Perhaps a port scan will show whether it's working or not.
The problem appears to be with 192.168.4.3.

-- 
Bill Moran
Potential Technology
http://www.potentialtech.com