XP Pro hangs with 4 users

[glasseigne]

I'm running 4 XP Pro workstations. 1 is running double duty as a
workstation and file server. As long as 3 or fewer people are
connected, no problems. However, once the 4th person joins, the file
server machine will lock up 1 to 4 times a day. Suggestions? Thoughts?
TIA.

 

[Malke]

I'm running 4 XP Pro workstations. 1 is running double duty as a
workstation and file server. As long as 3 or fewer people are
connected, no problems. However, once the 4th person joins, the file
server machine will lock up 1 to 4 times a day. Suggestions? Thoughts?
TIA.

1. You don't have enough RAM in the pseudo-server.
2. You are running into the concurrent inbound connections limitations.

http://support.microsoft.com/?id=314882

5 for XP Home
10 for XP Pro/Tablet/MCE
49 for SBS 2000
74 for SBS 2003
Unlimited for full Server O/Ses

To solve #1, add more RAM. Since I don't know anything about the computer I
can't be more specific.

To solve #2, either replace XP Pro with a real MS server operating system
or, if the machine only acts as a file server (doesn't need to run Windows
programs) you could use Linux.

Malke

 

[AJR]

By "lock" do you mean total non-access and reboot is required - you are not
receiving warnings about exceeding connections?
Have you verified that the computer is not performing another function or
accessing is being attempted other than file access?

 

[Guest]

Possible RPC virus on the computer that joins? (and server not patched for
this vulnarability) Just a thought.

 

[glasseigne]

Malke,

Thanks for the ideas. I don't think it is a RAM issue. The machine has
2 gig. I should have been clearer. It's not just a file server, it is
also used as a client by a user.

Also, I don't think it's a concurrent connections issue because I never
get a message about maximum number of connections. The "server" works
fine locally, but will not display or respond from the other machines.
It either has to be rebooted or you can drop all the connections and
then it's good to go again.

Any other ideas?

 

[glasseigne]

AJR,

As I responded to Malke, I don't think it's a concurrent connections
issue because I never get a message about maximum number of
connections. The "server" works fine locally, but will not display or
respond from the other machines. It either has to be rebooted or you
can drop all the connections and then it's good to go again.

Yes, I'm sure another application or service is no locking a file
because the other machines cannot even browse the folder once the
"server" locks.

Any more thoughts?

 

[Malke]

Malke,

Thanks for the ideas. I don't think it is a RAM issue. The machine has
2 gig. I should have been clearer. It's not just a file server, it is
also used as a client by a user.

Also, I don't think it's a concurrent connections issue because I never
get a message about maximum number of connections. The "server" works
fine locally, but will not display or respond from the other machines.
It either has to be rebooted or you can drop all the connections and
then it's good to go again.

Any other ideas?

It is a very bad idea to use a workstation as a file server. Server machines
should never be touched by users. There is no way for me to know why your
machine is locking up without looking at it. See if there are any clues in
Event Viewer - Start>Run>eventvwr.msc [enter]

Can you identify what is running on the pseudo-server when it locks up? Is
this machine used on the Internet? What is your network hardware, both on
the workstation and the local area network itself?

Aside from the amount of RAM in the system, what are the hardware specs on
the pseudo-server? A cheap eMachines box is not going to be reliable doing
combination duty as a workstation and a server. Even a lower-end server
will have better, more stable hardware.

The practical answer to your problems is to 1) get a qualified computer
professional on-site to check out what is really happening; 2) buy a
low-end server with either an MS operating system on it or Linux and use it
as a file server; 3) make sure there is a working backup system in place. I
understand that wasn't the magic answer you wanted, but it will serve your
business better in the long run.

This article I wrote about "Common Mistakes Made by Small Business Owners"
may be of use to you:
http://www.elephantboycomputers.com/page3.html#4-28-06

Malke

 

[glasseigne]

Yea, I know it's not a great situation, but sometimes it's reality. I'm
in the middle a server consolidation and move, and it just has to be
for a while.

Also, assuming I'm not a qualified computer professional is very
presumptuous. I have over 20 years of experience. Everyone gets stuck
sometimes and looks to others for suggestions.

Malke,

Thanks for the ideas. I don't think it is a RAM issue. The machine has
2 gig. I should have been clearer. It's not just a file server, it is
also used as a client by a user.

Also, I don't think it's a concurrent connections issue because I never
get a message about maximum number of connections. The "server" works
fine locally, but will not display or respond from the other machines.
It either has to be rebooted or you can drop all the connections and
then it's good to go again.

Any other ideas?

It is a very bad idea to use a workstation as a file server. Server machines
should never be touched by users. There is no way for me to know why your
machine is locking up without looking at it. See if there are any clues in
Event Viewer - Start>Run>eventvwr.msc [enter]

Can you identify what is running on the pseudo-server when it locks up? Is
this machine used on the Internet? What is your network hardware, both on
the workstation and the local area network itself?

Aside from the amount of RAM in the system, what are the hardware specs on
the pseudo-server? A cheap eMachines box is not going to be reliable doing
combination duty as a workstation and a server. Even a lower-end server
will have better, more stable hardware.

The practical answer to your problems is to 1) get a qualified computer
professional on-site to check out what is really happening; 2) buy a
low-end server with either an MS operating system on it or Linux and use it
as a file server; 3) make sure there is a working backup system in place. I
understand that wasn't the magic answer you wanted, but it will serve your
business better in the long run.

This article I wrote about "Common Mistakes Made by Small Business Owners"
may be of use to you:
http://www.elephantboycomputers.com/page3.html#4-28-06

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

 

[Malke]

Yea, I know it's not a great situation, but sometimes it's reality. I'm
in the middle a server consolidation and move, and it just has to be
for a while.

Also, assuming I'm not a qualified computer professional is very
presumptuous. I have over 20 years of experience. Everyone gets stuck
sometimes and looks to others for suggestions.

I'm sorry your feelings were hurt. It was not intentional. Since you didn't
*tell* me anything about you, your computer, your company, or your
situation, there was no way for me to know your skill level. Good luck in
your endeavors.

Malke