Socket Looking For Netbios Name

Sorry to post something somewhat off-topic here. I posted in
comp.os.ms-windows.networking.misc but got no reply. My problem has
something to do with the brain dead way that microsoft applications deal
with networks. Here is the original post:


I have a server running inside a DMZ with address 192.168.2.4. Clients on
the Internet connect to an adsl modem/router which port forwards the
connection.

A linux router separates the DMZ from the LAN. Clients on the LAN
(network address 192.168.1.0) have been using the public ip address, which
port forwards. But it makes more sense to connect directly using the
192.168.2.4 address. However, I've run into a problem.

When the Windows box connects to the server using the public ip address,
it sends a normal tcp syn packet to start the connection. But when it
uses the private ip address, it first sends the server a netbios-ns query
udp message, gets no reply, and gives up. This happens even though the
client is configured to use an ip address rather than a name. I'm not
sure how to get around the problem.

Thanks

Dan

"Dan N" <(E-Mail Removed)> wrote in message
news(E-Mail Removed) ldomain

> When the Windows box connects to the server using the public ip
> address, it sends a normal tcp syn packet to start the connection.
> But when it uses the private ip address, it first sends the server a
> netbios-ns query udp message, gets no reply, and gives up. This
> happens even though the client is configured to use an ip address
> rather than a name. I'm not sure how to get around the problem.

Are you certain that the DMZ server is listening on both interfaces?

On Wed, 03 May 2006 05:50:09 -0700, ynotssor wrote:

> Are you certain that the DMZ server is listening on both interfaces?

The server only has one interface, 192.168.2.4. Everything else is port
forwarded to it.

The problem is with the client. When it uses the public ip address, it
sends a tcp syn packet to initiate the socket connection. This is what
it should do. But when it uses a private ip address, for some brain-dead
windows reason it thinks that it has to make a query for the netbios name.

Dan

Dan N wrote:
> On Wed, 03 May 2006 05:50:09 -0700, ynotssor wrote:
>
> > Are you certain that the DMZ server is listening on both interfaces?
>
> The server only has one interface, 192.168.2.4. Everything else is port
> forwarded to it.
>
> The problem is with the client. When it uses the public ip address, it
> sends a tcp syn packet to initiate the socket connection. This is what
> it should do. But when it uses a private ip address, for some brain-dead
> windows reason it thinks that it has to make a query for the netbios name.
>
> Dan

Not that I know (because I don't)...so a WAG, to say the least - I'm
on Debian Sarge and I know very little about XPoop, but *perhaps* look
into; /etc/samba/smb.conf and
/usr/share/doc/samba-doc/htmldocs/nmblookup.1.html

you will find within /etc/samba/smb.conf things like this (notice the
"name resolve order") ;
===================
[...]

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host
names
# to IP addresses
; name resolve order = lmhosts host wins bcast

[...]
=====================

hth --atleast as a starting point...

I know MS uses LMHOSTS and HOSTS files and may even be using WINS ...(I
believe that HOSTS file on XP usually resides in system32\drivers\etc
or somesuch) --also MS uses a lookup order as well. In Xpoop, you might
want to use NBTSTAT(?) command or similar, as well as ROUTE (or
similar) to see if using Bcast, etc