Virtual OS.

[BoomAM]

Hi.
Im currently running a heavily optimised version of XP Pro in a virtual machine, under Vista64, with the purpose of using it as a print server on our domain, and nothing more. The host machine, running Vista64, is not on a domain.

I have it setup, and apart from the occasional graphical glitch, runs very smoothly, and is handling the two test printers fine, with very little CPU time & memory usage.

Is it feasible for me to keep this running as a print server 24/7, serving upto 30 printers? Or would it be better as a normal XP install?

Thanks in advance all. .

 

[Burnsy2023]

THere's nothing wrong with running a VM 24/7, but you do realise you can only have 10 concurrent connections with XP Pro, making 30 printers a bit much for it

Burnsy

 

[BoomAM]

THere's nothing wrong with running a VM 24/7, but you do realise you can only have 10 concurrent connections with XP Pro, making 30 printers a bit much for it

Burnsy

Is that the same connections limit as with what you get with Torrents?
If so, i'll just apply that patch that'll up it to whatever i want.

 

[Burnsy2023]

Is that the same connections limit as with what you get with Torrents?
If so, i'll just apply that patch that'll up it to whatever i want.

Not sure, I run all my (legal) torrents off a 2003 server

Burnsy

 

[BoomAM]

Not sure, I run all my (legal) torrents off a 2003 server

Burnsy

Appears to be.
I ran the EvilID Patch, and it is limited to 10 connections aparentely.
So i upped it to 1000. . I'll see how it goes. .

 

[Uhtred]

No. There's a limit in xp pro for 10 connections and it's different to the torrent issue. This is hard wired into xp for the very reason you're trying to use it for, they don't want it being used as a server. There is no way around it.

 

[mdjmcnally]

I think they have done this Windows 2000 as some clever jokers worked out the registry entries to make Win2K Professional act like Win2K Server, and sold on as a Server yet only paying Microsoft for the Pro version.

 

[BoomAM]

No. There's a limit in xp pro for 10 connections and it's different to the torrent issue. This is hard wired into xp for the very reason you're trying to use it for, they don't want it being used as a server. There is no way around it.

Well google searching leads it to being the same issue. .
You increase the connections for torrents by modifying the limits in the tcpip.sys file, the same file thats used for all IP connections from XP.
So logic would dictate its the same 'issue'.
Can you post some information on the thing your on about please? .

 

[Uhtred]

Well google searching leads it to being the same issue. .
You increase the connections for torrents by modifying the limits in the tcpip.sys file, the same file thats used for all IP connections from XP.
So logic would dictate its the same 'issue'.
Can you post some information on the thing your on about please? .

There you go

http://support.microsoft.com/kb/314882

 

[BoomAM]

K3

From what i can tell from that, it is the same TCP/IP limits as on torrents?

Luckily ive only installed XP/Updates/Papercut/2 printers upto now.
So i might leave that running and create a 2nd VM with Server 2K3, ready to go at a moments notice.

Will any version of Server2K3 do? Or does it have to be a specific version?

Will Vista64 do as a host OS? Or should i consider changing it?

Thanks again everyone. .

 

[csmager]

The numbers are the same, but the limits are certainly not the same thing.

The 10 connection limit you're talking about is a limit on TCP/IP outgoing connections. This was introduced in SP2 to help with viruses spreading, and limits the setting up of outoing connections to 10 per second. There's no actual limit to the amount of connections.

The 10 inbound connection limit is hard coded into non-server versions of Windows to prevent them being used as servers.

 

[NathanE]

Personally I've never run into the 10 incoming connections limit. Most Windows PC's will be listening on way more than just 10 ports.

I think it's just a licensing clause.

 

[Burnsy2023]

Personally I've never run into the 10 incoming connections limit. Most Windows PC's will be listening on way more than just 10 ports.

I think it's just a licensing clause.

It's not just a licensing issue, I've had it many times when I've tried to access a shared filestore on an XP workstation.

Burnsy

 

[BoomAM]

Will any version of Server 2003 do?

 

[Uhtred]

It's not just a licensing issue, I've had it many times when I've tried to access a shared filestore on an XP workstation.

Burnsy

I've had it a few times on an xp workstation which is setup as a render server for 3d studio max

 

[Uhtred]

Will any version of Server 2003 do?

Yup, standard will do fine

 

[Hodders]

Or if you don't want to pay M$ try thinking about putting linux in the Virtual machine and running shared printers with Samba.

Could save loads of cash !

 

[Burnsy2023]

Or if you don't want to pay M$ try thinking about putting linux in the Virtual machine and running shared printers with Samba.

Could save loads of cash !

But can be a pain in the ass, especially if you have so many printers.

Burnsy

 

[bledd]

The 10 inbound connection limit is hard coded into non-server versions of Windows to prevent them being used as servers.

yup

its not the 4226 issue, it's different, can't get around it

either use a linux box as a print server, or get a ms server os


-4226 patches the outbound, but it's legal because it doesn't convert an xp box into a server one, its the inbound connections that'll sting you

if you read that kb article, you can lower the 'keep connected' limit to say 1 minute (maybe even 0.5 minutes), to help overlapping connections

 

[BoomAM]

Im just making a VM now with Server 2K3 in, im a bit stuck at the licensing mode screen.
The two options are:

Per Server. Number of concurrent connections : xxxx
Each connection much have its own Client Access Licence.

And:

Per Device or Per User.
Each device or user must have its own Client Access Licence

Any ideas?