Recommended Posts

Well from there I see 8 connections to 139, and then see those connections to 10160.. Your running quickbooks on this server I think? Those are more connections that I do believe also count against your limit.

Looks like 13 inbound connections to me.

From this statement in the article "This limit includes all transports and resource sharing protocols combined."

From all transports, that would look like your over the limit to me.

edit: Im not sure if they count or not, to be honest I don't have not had much experience with this limit, since nobody in their right mind would use XP as a file server if you have more than say 2 or 3 users in a VERY SMALL setup.. Like HOME!! Companies would run SERVER OSes -- shoot its not like you don't have the money -- your spending $24K a year on backups ;)

Any customers I have done business with that are small ma and pop shops -- the reason they brought me in was to get their networks up to speed over a home setup ;) Ie a SERVER based os with a central userbase ;)

With the number of clients you have your going to have issues with this limit until you graduate from a HOME setup.

Edited by BudMan

Also we turn off Windows Firewall it interferes with a lot of things. Just a suggestion. Its not going to help in this case just something to add. And there's nothing anymore I can say or anyone else on here for that matter, Thats not been said 1000 times before. Upgrade to another OS that doesnt limit connections. XP Pro was designed to be a client itself connecting to a server, Not been a server.

Like I said I don't really have a lot of experience with the 10 connection limit, not for years and years - and it was before XP when dealing back in the day with win3.1, 95 and 98 --- back when the servers were NT3.51 and NT 4 just came out etc.. When companies were just moving away from mainframes to window servers and you the remote locations just running peer to peer networks, etc.

And then small companies I have moved to a server setup.. Yes I have seen quite a few soho setups having the issue -- but when I helped them it was to move them to a true server setup vs peertopeer network.. A peer to peer (just a bunch of workstations sharing - client as your server) is only viable when you have a couple of clients.. Your over that limit since your running into the the connection limit.

Its time you move to a true server OS that does not have the client limit of 10 connections. You can do this by moving to a MS server OS, be it 2k3, 2k8 (better choice than 2k3) or their SBS line (prob best choice for your setup) and then getting the correct amount of cals for your clients. Or you would have to go the linux route which does not have the limit of connections and is not restricted by the MS licensing issues with CALs to connect everything together, etc. I would suggest CC or SME, etc. since they are both designed for ease of use by new admins or even just reg folks that are clueless when it comes to IT.

But from the way I read the article "This limit includes all transports and resource sharing protocols combined." then yes I would assume your connections to quickbooks running on that XP "server" is going to count against your 10 connection limit.

Guess you could move your quickbooks to another client machine that does not share files as well -- but this would be taking 3 steps back vs the 1 step forward you should be taking.

YOU NEED TO MOVE AWAY FROM XP AS "SERVER" -- it works fine for sharing files with your family members in a HOME setup -- but it is not a business class model!! And was never designed to be -- why do you think MS put in the limit in the first place? To prevent its use of how your using it when you should be on one of their SERVER OSes. So they can get more money from you since your a business ;) hehehe

I would REALLY REALLY suggest you take a look at Small Business Server from MS, or take a look at the linux distros designed to be an alternative to SBS, like CC or SME. Sure you could go the 2k8 route -- but SBS would be a better fit for your company and the limited skill set of their IT ;)

I am willing to help you no matter which one you choose to go with.. But you NEED TO MOVE OFF XP as your "server"!!!

Its not possible for something to get messed up if you bring it up on a new server, and then copy your files over to the new machine.. You wont be touching the current setup in any way.. it will be a NEW SERVER, with a copy of your files.. Once you have it working and prove to your boss.. Then you can shut down the old xp server.

And I suggest you go with a SERVER class machine vs desktop hardware.. Entry level cost will not be that much more than a desktop but will support RAID for your data drives, and possible dual power supplies, etc.

The ability to hot swap drives out in case of failure with no down time, etc. and no need to recover data from your backup. Which since its online could take quite some time! Even if they shipped you the data on media or a hdd, etc.

I am really curious how many drives -- if just one, etc. are in your xp server. Could you post a screen shot of disk manager.

example

post-14624-1257955027_thumb.jpg

BTW there is NO way to fix the issue without moving away from XP -- there is no way to remove that limit in XP. You can try the autodisconnect time set to a very low number - that might help a bit.. But it is not a fix.

Edited by BudMan

Yeah thats fine for a TEST, but your going to need to do something -- so I would ORDER a NEW SERVER.. And then you can decide what OS to put on it after ;)

Dell has stuff preloaded with SBS on it -- so that might be a good option for you as well ;)

I have not worked with the current versions of quickbooks, I am not sure if they have a linux version - pretty much doubt it. So that might be a roadblock to going the linux route. But I they had a online version (which they do) -- you could always go that route ;)

If it was just shared files -- it would be no big deal.. But looks like your running a copy of the quickbooks on the server. If this is a requirement to run on the server - then your going to be have to go the windows route.. Or you could leave it where its at, and just use linux as your File Server, etc.

I have not worked with the current versions of quickbooks, I am not sure if they have a linux version - pretty much doubt it. So that might be a roadblock to going the linux route. But I they had a online version -- you could always go that route ;)

If it was just shared files -- it would be no big deal.. But looks like your running a copy of the quickbooks on the server. If this is a requirement to run on the server - then your going to be have to go the windows route.. Or you could leave it where its at, and just use linux as your File Server, etc.

Edited by BudMan

Well I just did a lookup on dell for a T300 with 4 2TB hot swap drives in raid 5 setup, a UPS and dual power supplies with a license for SBS standard and 15 cals, with 3 years NBD onsite support and remote help setting up SBS, etc. and was in the $7k range.

You could prob lower that cost by not going with hot swap and or dual power, and no ups and not getting the remote sbs help, etc. But that seemed very reasonable for a entry level server with that amount of space and all the MS licensing, etc.

If you going to make the move to a server, then I would HIGHLY suggest you get the features that make a server hardware worth it, dual power, hot swap drives, etc. So I would tell you boss your looking at like a $8 to 9K budget!!

edit: If you post a screen shot of your current xp servers disk manager we can see what hard drive space you have and how it being utilized, etc. This determine how much hard drive space you need to get started with, etc.

That cost can fluctuate a lot -- all depends on what exactly your looking for.. If your Boss would ok say a $10 budget you come in well under budget and gets some great entry level hardware! Plus lots of features like 3 years on site 4 hour response, etc.

Edited by BudMan
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!