First, Circuit City made the recommendations so....where are they when the shite hits the fan?
Stupid recommendations made by inexperienced doodle-do's. (speaking solely of Circuit City)


(First problem)

[Connection limit by OS ]

Computers that run Windows NT Workstation 4.0, Windows 2000 Professional, and Windows XP Professional are licensed for a maximum of 10 concurrent client incoming sessions.

Computers that run Windows XP Home Edition are licensed for a maximum of 5 concurrent client incoming sessions. All logical drive, logical printer, and transport level connections combined from a single computer are one session.

[How a session is counted ]
Typically a computer does not have multiple sessions to another computer. But there are exceptions.
For example, computer A is running a service under another user context than the logged-on user, and that service creates a logical connection to computer B. The logical connection can result from file shares, printers, serial ports, and also from communication between computers using named pipes and mail slots.

[Multiple connections can count as ONE session ]
All logical drive, logical printer, and transport level connections combined from a single computer are considered to be one session;therefore, these connections only count as one connection in the ten- connection limit.
For example, if a user establishes two logical drive connections, two Windows sockets, and one logical printer connection to a Windows XP system, one session is established. As a result, there will be only one less connection that can be made to the Windows XP system, even though three logical connections have been established.

[Time limit on dead connections ]
Any file, print, named pipe, or mail slot session that does not have any activity on it will be automatically disconnected after the AutoDisconnect time has expired; the default for this is 15 minutes. Once the session is disconnected, one of the 10 connections will be available so that another user can connect

[Configuring AutoDisconnect time ]
You can configure the AutoDisconnect time by running the following command from a command prompt:
net config server /autodisconnect:time_before_autodisconnect
Specify the time in minutes.

[Listing current active sessions ]
To receive information about active sessions on the computer that is running the server service, type the following command:
net session
Count the number of open sessions to see if the session limit of 10, or 5 in the case of Windows XP Home Edition, is already reached. Typically there is only one session per remote client.

If there is more than one session from a remote client, view the User name context on the remote client that has set up more than one session:
• View all the services that are running, and find out if one is running under the user context of the username shown in the session table.
• Look for scheduled tasks that are running in a logon script and are using a different user account then the one logging in.
• Look for rows where the User name column is empty and examine the idle time.
A session that has an empty user context is a null session.

Temporary null sessions are usually caused by IPC$ connections as the first step in establishing a connection. They stay active for 30 seconds to 90 seconds.

[Disconnecting client sessions manually ]
Note To disconnect client computer sessions, use the following command:
net session /delete \\computername
This command disconnects all sessions from that computer and closes all open files. This command may cause data loss if open files that have not been saved are closed.

[Solution to first problem ]
Either return to Win NT 4, inform management of the connection limitation, or buy Windows SBS. Why not standard Windows server? Cause SBS costs the same or less and provides many more features. Note that you cannot buy and install SBS properly in a couple days time. (MS Access is not your problem here)


(Second problem)
Printers:
With limited time, as you seem to be in, I would examine naming the Linksys printserver and ports with the OLD information.
The Print server name as decided upon by the user (YOU) when inside the printserver can be set as:
ps3423rfglsf3or
and printers can be named:
HP1010

[Solution to the second problem ]
What does change, in this scenario, is how you setup the printers.

Here's the basics:
1) Setup the print server with the name "ps3423frglsf3or" at such and such IP address from within the print server setup screen.
2) Don't use the silly "print server" software to enable printing control, I never do!
3) Know what the print server port identifier is for the actual physical ports the printers are connected to, as in 9100, 9101, if the ports are named remember the port names.
4) On the computers, setup a new port for the existing printers using the "Add port", Select "Standard TCP/IP port", then click on "new port" button, click next and put in the IP address of the print server but name it "ps3423frglsf3or". If the port has a number, enter it in the "Raw" section. If the port has a name, enter it in the "LPR" Queue section. (sometimes you have to check "enable byte counting", sometimes not)
5) Check next, next, next or save, save, save. Wait a 20 seconds for XP to digest this and try a print page from within the print driver general dialog screen.
6) If setup correctly this should work, now try printing a check or whatever from the program.

PM me with contact information if you want to talk ear to ear.

Any moral support you get helps, I know.


Edit: Here's a link for messing with the TCP connection limitation in SP2: http://www.speedguide.net/read_articles.php?id=1497