Total layman with a serious network problem. Cabinet maker with server with Linux OS running Samba in a domain network environment. (5) workstations and (1) networked Gestetner printer, copier, scanner, fax combo. Os's on the work stations are varied: (1) pc on Windows 98, (2) pcs on XP home, (2) pcs on XP pro. One pc with XP Pro is a controller opertating a CNC computerized machine on the shop floor.
A really good IT guy is doing a great favor by hooking us up with a used server and linux OS to save us big time money. Server is this big heavy thing with 4 processors and 4 hard drives we got off e-bay.
The problem is that the work stations run like dinosaurs when connected to the network. To run my major cabinet software I have to unplug from the network to get it to run at normal speed. All appliacations are client resident(if that is the correct term) and not running from the server. Even if I don't use anything off the server, just being physically attached to network drags each pc down. The IT says that the problem is probably the XP home pcs dragging down the network and that they are not designed to run within a domain. Something about Samba will not accept the "token" form the XP home pcs. The suggestion is to buy XP Pro for the two XP home pcs. Is this the best action to take. The IT is coming in a week to fix the system and I want to make sure he has everything he needs. Also I don't want to spend money I don't need to and the headache of removing and reinstalling a pc's OS if I don't have to. Are we giving the IT ingredients for disaster by having XP home. He came to the shop assumong all pcs had XP Pro, but we slipped him a Micky I guess. He networked the whole shop in one day, incuding running wire. His abilities are amazing (He has networked businesses up to 1200 work stations-no slouch). I just don't want to make things harder for him to get the thing running, like writing millions of patches to get our garbage components to work. What is the easiest route to take? Has anyone run a network lilke this with similar ingredients? Thanks for the help,
David
Originally Posted by davidsbc
XP Home can not join a domain at all. Home Edition supports peer-to-peer (workgroup) networking only. Your IT guy is right. Also, if I may ask, why do you want a server for such a small network? Why not just use a basic peer-to-peer network to share resources?
TANSTAAFL
We were networked peer to peer, but I was told that this was not a "real" network, and would not be as secure as a network supported by a server. So, we did the server thing, and now we cannot really use it at all. What is the best action to take at this point. I would prefer to keep the server and get it to run properly. Thanks
David
That's only true when you have many clients with many people accessing your network. Also if you run peer-to-peer, then you risk exposing your network if it's connected to the Internet. As far as I've read from your posts, your network seems to be isolated and clients access are very limited ( a cabinet handyman hacking your network?? Not very likely) but having as much security as possible is a very positive "piece of mind" thing.
CGA (and your "IT guy") was right. XP Home make a lousy network client if more than 2 PCs. I'd just upgrade your network to ALL XP pro since you will only need to buy one more copy for the one running 98 in addition to upgrading your XPHome PCs (unless upgrading would make it almost impossible such as PC's low hardware specs). Your ROI (Return On Investment) would be likely much higher if you do that. By also running only one OS, you will be able to eliminate many protocols that are not necessary such as NetBUEI. Just run a pure TCP/IP network, many be configure your network server to act as router and you should be good.What is the best action to take at this point. I would prefer to keep the server and get it to run properly.
I'd tend to agree with your "IT guy". I know it is easier to said than done when you have to shell out more than 5K for lousy XPs but then again, you will have much more eaiser time managing your network in the long run.
HTH ....
You should be able to run the Task Manager under Windows XP and see what process is consuming the pc's resources when connected to the network. That can help you start troubleshooring the issue.
My crime is that of curiosity. My crime is that of judging people by what they say and think, not what they look like. My crime is that of outsmarting you, something that you will never forgive.
snip...
Not really. You just have to keep everything behind a perimeter firewall and follow best security practices. I have a network here in my lab with around 16 machines in a wireless peer-to-peer setup behind a firewall with no problems.
TANSTAAFL
This may be a bad ethernet cable as well. I have seen this happen when a pc needs to ask for retransmits due to errors.
Posting Permissions
Reply With Quote
Bookmarks