Quote:
Originally posted by aplustech:
<STRONG>First, I'd like to disagree to the last post (no offense) and say that TCP-IP is a very valuable protocol that would make us very lost in many instances if we did not have it.</STRONG>
It's no offense, as i'm pleased to discuss... and I never said TCP/IP isn't valuable... but it's not that efficient (overhead, adressrange ...) so you're right.
Quote:
Originally posted by The bear:
<STRONG>If the server is having problems with DHCP then the computer cannot obtain a user name.</STRONG>
No, it can't obtain an IP-adress - not a username (but still you can set an IP yourself)
<STRONG>If it has a specific address matching the servers first three strings and matching the subnet mask and the network goes down, the workstation can communicate with other workstations if the server goes down (Provding other clients are set-up the same way).</STRONG>
That's only the simplest of the simple setups. TCP/IP adresses consist of 4x8Bits ... and an IP-adress bitwise AND-combined with the netmask equals the network-adress...
If the network-adresses from one another IP matches then they don't need to be routed - if not, they can still be routed to one another by adding for example static routes - that's the way it works...
<STRONG>This is a good way to set-up the network if it is small and managable. If you are setting up a large network and have no way of keeping records of the address's I would suggest seting up the DHCP.</STRONG>
You're right with suggesting DHCP, but you still have to keep record of it and plan carefully in big networks...
<STRONG>NetBEUI - ... Over a 10/100 network this protocol is good.</STRONG>
If you have to route via WAN/VPN/Internet/whatelse you may not use this protocol as it has no Layer3 functionality - only bridging is possible.
TheBear, I hope you don't feel attacked ... I can't see why you want to defend the use of NetBEUI... it's a very proprietary protocol with disadvantages (Scooter: thanks for mentioning the use of NetBEUI with some databases)