netbios over tcpip. To host or LM host?

[chachdogg]

1) So Is it ok to have netbios running on tcpip if I am hidden from the internet

1) What would be the fastest way to share out a database over the LAN? TCPIP with static ip's with the same LM hosts file on each pc? I am sick of trying to access a computer name and have it not find it. I disabled netbios over tcpip and now can't find any pc without an ip address. Will The LM hosts will fix this? or is it the Hosts file?:confused:

[BipolarBill]

Modify the HOSTS file with IP and name entries for each PC on your LAN and you won't need NETBIOS. Frankly, I would use NETBIOS if I was behind a firewall or router.

How to share a database depends on your OS and the application. Share the folder it lies in first. Set access permissions. Use the ODBC tool in Control Panel or Administrative Tools to configure database access.

[chachdogg]

I meant speedwise. not permission wise. I have it shared out but there is a small delay when a user across the lan uses it. I was trying to minimize any extra overhead with multiple protocols or computer names. Just IP. That is why Iwould like to use the hosts deal.

thanks.
What is the difference with the hosts vs the lm hosts?

[Midknyte]

hosts file is for DNS (host name to IP)
lmhosts is for NetBios name to IP
I don't think either would help you much in this scenario.

adding protocols will slow down the network, not speed it up. Netbeui is especially "noisy" and has a lot of overhead. just use tcp/ip.

do you have the database on a server? Make sure the server has a static IP. All the others should be dhcp. Static IPs are hard to manage and will add a lot to your administrative overhead. Do you have a dhcp server or router? do you have a dns server? if you can only connect to other systems by ip, then your dns is not working properly.

It might just be a network bottleneck. Make sure you have a switch, not just a hub.

[chachdogg]

I have
8 computers.
All static ip.
ex 192.168.1.1 -.9
no dns
no wins
homeportal router/firewall
linksys 16 port switch.
There is dhcp available but don't want to use it because of shares that can't afford to go down. The pc with the database is not a server, just a pc. I want to use straight IP because I don't want one pc to one day for no reason not to connect to a share that is by computer name. I don't have dns or wins running. there are no servers. just peer to peer with dsl etc. Can't I just put the static IP's I made in the host or lm host files mapping to pc names and be done? or would I just be good to put netbios over tcpip?

thanks

[Midknyte]

Geez. that is a pretty skimpy network. if you don't have a server, then you shouldn't use the host workstation for anything, but the database. if you have someone working on the host workstation, it will slow down the network access.

no dns and no wins makes it way harder to manage the network, but if it's small, I guess it's ok.

the next best thing would be to use a hosts file. adding another protocol to the network will slow it down.

[chachdogg]

small office.
so the verdict is tcpip with no netbios with static entries in the hosts file on each pc?

[Midknyte]

yep. try that first.

[chachdogg]

my bad. Hosts or LM hosts?

[Midknyte]

you could use either one. I would use hosts frst.

[kwebb]

Yep, either one will work. As already mentioned, by design the hosts file is for domain name to IP and LMHosts is for COmputer name (NetBIOS) to IP but either will work. They both get parsed by the stack. I don't remember the Mneumonic I memorized for the NT4 TCP/IP test but I believe Hosts gets looked at first, though the difference would be beyond human perception. When I got in the business the first thing I was taught was the hosts and I have always used it for NetBIOS resolution woes even though it's not specifically designed for it. A hosts solution is perfect on a network that small with static IP's.

[Logan[TeamX]]

NetBEUI / NetBIOS is a fast, but non-routable protocol. If you wish to employ TCP/IP only, then only modify and use the HOSTS file. Personally, I'd turn off NETBEUI completely, not only because of the overhead, but because it always broadcasts packets, and renders having a switch almost pointless. (Minus the full-duplex bandwidth per node)

Why would having DHCP hurt your shares? Take the time to implement it right, and you reap the benefits of a stable network. Also, if keeping certain IP addresses is a must, and you have a copy of Windows 2000 Server running, use Reservations in the DHCP scope. Bind the reservation to each critical machine's MAC address, and you're set. For low overhead, just use WINS to resolve names if you don't want to use DNS server(s).

[AllGamer]

If you are using TCP/IP i fail the point why you would want NetBeui ancient and buggy protocol in there

it actually slows downs your network if you use both

is best to use TCP/IP + DNS

fast and reliable :t

[Logan[TeamX]]

I agree. I use Win2K + DHCP + Active Directory-integrated DNS servers here at work, beautiful stuff. Of course, this is on a sweet budget. Yours may not have as many zeroes. Adjust to suit your needs :)

Logan

[Midknyte]

He only has a small network with no dedicated server. He probably doesn't have the $$$. Unfortunately, we are all trying to do more with less nowadays. :(

NetBeui is the last resort, quick and dirty protocol. Not something I would use everyday.