Network setup advice needed

[Wild1]

OK, I need some help from the experts on my network configuration setup as networking is my weak suit.

I want to setup my system for the greatest possible security and eliminate any unneeded protocols. I have 2 computers on a wired LAN with a router. I also have a printserver to share printers. I rembember reading somewhere to unbind the TCP/IP protocol from file and print sharing and maybe from Client for MS Networks also. Is this correct? Is it recommended to unbind it for all the connections? I have a 1394 connection and a Local area connection.

Also, what protocols are needed / recommended? Currently I have the following setup

Connection Properties for LAN adapter
Client for MS Network
File & print sharing for MS networks
QoS packet scheduler
NWLink NetBIOS
NWLink IPX/SPX/NetBIOS comptabile transport protocol
Internet Protocol (TCP/IP)

Connection Properties for 1394 adapter
Client for MS Network
File & print sharing for MS networks
Internet Protocol (TCP/IP)


Local Area Connection Bindings
File & Print Sharing for MS Network
NWLink IPX/SPX/NetBIOS comptabile transport protocol enabled
TCP/IP Disabled
Client for MS network
NWLink IPX/SPX/NetBIOS comptabile transport protocol enabled
TCP/IP Disabled

1394 Connection Bindings
File & Print Sharing for MS Network
TCP/IP enabled
Client for MS network
TCP/IP enabled

The IPX protocol was added when the printserver was installed. Do I need/want this?

Thanks for any input!

 

[lansalot]

The IPX protocol was added when the printserver was installed. Do I need/want this?

Not sure - can you move over a little to the left as I can't quite read the model of the printserver from where you're sitting and it wouldn't be accurate to say without it....

That said, most print servers speak TCP/IP these days, so I wouldn't personally have the NW stuff installed. Most likely, your software just installed it to cover all the bases. Check your printerserver documentation and if it supports tcp/ip, remove the nw/ipx stuff.

All you should need is:
TCP/IP
MS File & Print Sharing
QoS is up to you

That's it.

If your PCs are close enough together, you could consider networking them over firewire. This will only work if you have only two PCs as there aren't any firewire 'routers' that I know of so a direct cable could be used. That will give you 480mbps instead of the 100mbps your typical router/switch will give you. Of course, if you're on gigabit, ignore that advice.

edit: of course, you would still have them UTP'd into the router for internet connectivity, a little tweak of the hosts file so when they talk to each other direct they do it through firewire and you're off.

 

[Wild1]

Originally posted by: lansalot

The IPX protocol was added when the printserver was installed. Do I need/want this?

Not sure - can you move over a little to the left as I can't quite read the model of the printserver from where you're sitting and it wouldn't be accurate to say without it....

Let me slide a little further over then, can you read it now?.....OK then I read it for you. It says Linksys Etherfast 2 Port Printserver with 4 Switched ports, Model EFSP42.

The manual is cryptic about the requirements saying both should be installed. But I found an area which said: When used with Windows, the printserver uses TCP/IP...when operating under Netware5.x, it uses IPX/SPX for communication.

I don't know what Netware is so I assume I don't have this. True?


If I remove IPX, how do you unbind the File & print sharing from the TCP/IP. Don't I need at least one protocol? Would adding a different protocol be better?

 

[lansalot]

Don't unbind file/print sharing from TCP/IP unless you have no need for file/print sharing between your two PCs.

Just remove IPX and any NWLINK - you don't have Netware and don't need it. Leave the ones I said and all will be well.

 

[Wild1]

Originally posted by: lansalot

The IPX protocol was added when the printserver was installed. Do I need/want this?

All you should need is:
TCP/IP
MS File & Print Sharing
QoS is up to you

Lansalot, you didn't have Client for MS Network in your list, Is it recommended to remove this also? From both the 1394 and the Network adaptor?

 

[JackMDS]

Eliminating Unused protocols is not so much a security issue (most of them do not Route to the Internet to begin with), it is more a way to achieve stable smoother Network.

On a regular system TCP/IP should be all that is needed.

However I usually add NetBEUI to the Network and bind it together with TCP/IP to File and Printer Sharing.

Link to: Set NetBEUI as a Sharing Protocol in WinXP.

Having NetBEUI in parallel to TCP/IP is an ?insurance policy? that local sharing would keep working even if some thing ?Trashed? TCP/IP, and it works faster then TCP/IP by itself.

NetBEUI might add a form of security as described on this page: Link to: An easy way to Disconnect/Connect the Internet and Keep your LAN and File Sharing a Live.

:sun:

 

[Wild1]

Originally posted by: JackMDS
Eliminating Unused protocols is not so much a security issue (most of them do not Route to the Internet to begin with), it is more a way to achieve stable smoother Network.

On a regular system TCP/IP should be all that is needed.

However I usually add NetBEUI to the Network and bind it together with TCP/IP to File and Printer Sharing.

Link to: Set NetBEUI as a Sharing Protocol in WinXP.

Having NetBEUI in parallel to TCP/IP is an ?insurance policy? that local sharing would keep working even if some thing ?Trashed? TCP/IP, and it works faster then TCP/IP by itself.

NetBEUI might add a form of security as described on this page: Link to: An easy way to Disconnect/Connect the Internet and Keep your LAN and File Sharing a Live.

:sun:

Jack, Thanks for the links. I am going to install NetBEUI as suggested. One ? though: binding both NetBEUI and TCP/IP for File & print sharing sounds good for stability but I also want want the security benefit of unbinding TCP/IP from file and print sharing. Any comments on the tradoff of binding TCPIP vs unbinding it for F&PS. Is the added stability of binding both protocols that significant?

 

[lansalot]

Look, just stay away from NetBEUI please. It's a bastard invention that should never have taken off and has no use. It's a protocol that is being dropped in future releases from Microsoft, along with IPX apparently.

You won't find it in any professional environment - and keeping it around "in case tcp/ip gets trashed" is an excuse I've never heard of.

Up to you however. If you are under the impression that your PC will be more stable with it (along with the extra resources it will take) then go for it.

Remember, in this instance: less is more.

 

[JackMDS]

Originally posted by: lansalot
Look, just stay away from NetBEUI please. It's a bastard invention that should never have taken off and has no use. It's a protocol that is being dropped in future releases from Microsoft, along with IPX apparently.

You won't find it in any professional environment - and keeping it around "in case tcp/ip gets trashed" is an excuse I've never heard of.

Up to you however. If you are under the impression that your PC will be more stable with it (along with the extra resources it will take) then go for it.

Remember, in this instance: less is more.

LOL

It always work, I do not remember one time that a discussion that includes the word NetBEUI will not include at least one Post with the ?Common Nonsense Anti NetBEUI Slogans?.:shocked:

?Being dropped in future releases?.

Hmm?guess No one should use Windows 2000 because the Support for it will be dropped in the near future too.:thumbsdown:

?Along with the extra resources it will take?.

Hmm... Beside the few KB (Kilo Byte) the it takes to keep the core protocol on the Hard Drive, what other resources known to you it takes?:thumbsup:

For few years I am waiting for some one that would explain in Technological terms (as oppose to emotion terms). What is Worng in Using NetBEUI for SAMLL NETWORK?

:sun:

 

[lansalot]

Hmm... Beside the few KB (Kilo Byte) the it takes to keep the core protocol on the Hard Drive, what other resources known to you it takes?

It may take a few KB on disk, but I'm sure you're aware (being an MVP) that once a program loads it may make all kinds of demands on system resources? Because a file is 5kb on disk doesn't mean that is all it will consume once loaded.

There's nothing particularly wrong in using only NetBEUI on your small network I guess except that:

it's non-standard
you *need* tcp/ip for internet connectivity, so why have both?

As for win2k support - if you have the choice now you should be taking XP for client or win2k3 for server. It makes no sense to start out afresh on becoming-obsolete products if you have a choice.

edit: and why on earth an MVP in Networking would recommend NetBEUI AND TCP/IP on the same machine - even in a small network - is mystifying. Why not add IPX as well - just in case? Did you notice that NetBEUI isn't available on a standard XP install and has to be pulled off the CD from the valueadd folder? I guess MS have good reasons for sticking it in the sidelines like that...

 

[Slowlearner]

TCP/IP works best with static IPs within a server/client setup. In a peer to peer LAN with mixed OSs (XP, 2000, 98 etc) with dynamic addressing, it is almost impossible to get a network working without some tinkering. Most people asking for help in this forum are trying to share a broadband connection and occasionally share some files across a LAN, and if you look at Microsoft's own forums on networking every second question relates to this issue, although its dropped off a bit lately. Microsoft's own help files and networking suggestions were useless if not downright confusing. If were not for helpful suggestions from people like JackMDS, Tim Higgin's original site and other MVPs like Steve Winograd at their forums, many of us would still be tinkering and fuming. Adding Netbuei is a painless fix without any serious drawbacks.

I manage mixed network with every OSs under the Sun in use, and I find Netbuei to be a lifesaver.

 

[lansalot]

Shame on you that you need that lifesaver then.

With a properly configured WINS master browser or DNS set up, browsing becomes painless.