Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Dave Hanson who wrote (5241)	1/18/1999 10:56:00 AM
From: Sean W. Smith	Read Replies (1) \| Respond to of 14778

NO Problem, but the info your provided shows the answer..... Here's the deal in laymans terms.... MS Networking which you are trying to use uses the Netbios API. The netbios API allows each machine on the network to have a name. These are the names you are familar with with MS networking. These names have nothing to do with IP Addresses or TCPIP Names. Netbios clascically ran under a non routable protocol called netbeui. When running netbios over IP there must be a machanism for mapping Netbious NAMES to TCPIP Names/Addresses. This is done several ways. 1. LMHOSTS File 2. Broadcast Frames 3. WINS 2. is the default method and won't work on in your case because 1 and 3 are on different IP subnets (Don't ask me to explain how I know but its evident from the material posted). IP Routers don't forward broadcast frames which is the default Netbios/IP Name resolution method. LMHOSTS - is a pain but will solve your problem. WINS - requires NT server and is the best way to handle this issue. I recommend the following solution because it has another huge advantage which is security. Solution: Use netbeui protocol for MS networking instead of TCPIP. Has the following advantages. 1. faster for small lans. 2. virtually no setup required. 3. You can't be hacked from the internet if you only use Netbeui because Netbeui can't travel over the net. 4. No Name mapping is necessary. Just simple Netbios Name to IEEE MAC Address mapping via broadcast frames. Please realize that using TCPIP I and anyone else on the net can access your computer if we know your share password or can spoof a trusted user. This is very dangerous and there are a plethora of hacking tools designed to detect and take advantage of this situation. Were you aware of this???? So here's how to do what you need. 1. Install Netbeui Protocol on all machines. on the bindings TAB on NT make sure only Netbeui is bound to Netbios, Server and Workstation. TCPIP should be diabled on all these services. reboot. you now should have connectivity between the machines and isolated your HD shares from being accessed via others on the internet. You could still have problems with SID or improper user and permissions setup but you defintely have a name resolution problem with the current setup and those will be resolved. good luck, Sean