Netbios over TCP (or not)

  • Thread starter Thread starter flekso
  • Start date Start date
F

flekso

I'm currently administering a *small* workgroup LAN that uses NETBEUI as its
*primary* protocol and TCP/IP for ICS .

What settings should i choose (under DNS/WINS tab) for the two internet
sharing PC's that must remain visible to other workgroup stations ? They're
the only ones with both TCP and NETBEUI in protocol stack .

Options that came to mind :
[DNS]
Register this connection's addresses in DNS

[WINS]
I have enabled all the options in this tab


All workstations + server run winXP pro .
 
I'm currently administering a *small* workgroup LAN that uses NETBEUI as its
*primary* protocol and TCP/IP for ICS .

What settings should i choose (under DNS/WINS tab) for the two internet
sharing PC's that must remain visible to other workgroup stations ? They're
the only ones with both TCP and NETBEUI in protocol stack .

Options that came to mind :
[DNS]
Register this connection's addresses in DNS

[WINS]
I have enabled all the options in this tab


All workstations + server run winXP pro .
Click to expand...

Unless you installed a separate DNS server application or you have a domain
controller hiding somewhere in the building, you don't have DNS nor WINS
available on your LAN. You can enable both switches but there's nothing behind
them.

Also: the standard XP Pro kit does not *include* NETBEUI, so unless you
downloaded and installed NETBEUI support on your XP Pro clients, they aren't
using NETBEUI.

Without a domain controller, the easiest way to manage your LAN (imho) is to
install (just) TCPIP on all systems, enable Netbios on TCPIP, give all "fixed"
systems legitimate private static IP addresses and provide a known pool for
DHCP to laptops, etc, and build a nice LMHOSTS file to load onto each
system...

/daytripper
 
Unless you installed a separate DNS server application or you have a
domain
controller hiding somewhere in the building, you don't have DNS nor WINS
available on your LAN. You can enable both switches but there's nothing behind

Okay.


Also: the standard XP Pro kit does not *include* NETBEUI, so unless you
downloaded and installed NETBEUI support on your XP Pro clients, they aren't
using NETBEUI.
Click to expand...

Yes it's from the value pack dir on the xp pro cd.
Without a domain controller, the easiest way to manage your LAN (imho) is to
install (just) TCPIP on all systems
Click to expand...

That's the problem, i know that's the best solution generaly. But in this
case there's a db app that's accessed from all over the network and was not
originally designed with that kind of operation in mind (app's folder
contains ~7 thousand of ~1KB files) - so my main problem was load/access
times for clients and i've read couple of topics that mentioned netbeui's
suberiority in that department(lots of small files).

TCP is just for one client/server pair (for ICS). As i said, it's a really
small network.

, enable Netbios on TCPIP, give all "fixed"
systems legitimate private static IP addresses and provide a known pool for
DHCP to laptops, etc, and build a nice LMHOSTS file to load onto each
system...

/daytripper
Click to expand...

It must have something to do with netbios over tcp or LMHOST file maybe.
Checking that out on monday.

Thanks anyhows.
 
Back
Top