No more connections can be made to this remote computer at this time

Here’s a little trick I learned a couple of years ago that managed to pop up again today.

The problem with Microsoft Windows XP/Vista/7 is that you have a limit on how many concurrent connections can be made to the device. Windows XP usually has 10 and Vista/7 has 15.

If you have a small network and happen to have more devices connecting to it, you’ll have to install an operating system that supports more concurrent connections. You could go the *nix route or install one of the server flavours of Microsoft Windows

Or, you can do this:

  1. Click START
  2. Click RUN
  3. Type in: regedit
  4. Click on OK/RUN
  5. Locate and then click to select the following Registry Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  6. In the Edit Menu, click NEW and click DWORD. (If exists, skip to step 8 )
  7. Type MaxMpxCT and press ENTER
  8. Right-Click MaxMpxCt and click Modify
  9. In the Value data box, choose DECIMAL ***
  10. Click OK and close the Registry
*** Note: You can set the number of concurrent SMB commands to a value that is between 10 and 255. The default value is 10 on MS Windows XP
Hope this helps >;]

Multiple vhosts, Apache

One of the most common Apache2 questions I’ve seen on Debian mailing lists is from users who wonder how to host multiple websites with a single server. This is very straightforward, especially with the additional tools the Debian package provides.
There are many different ways you can configure Apache to host multiple sites, ranging from the simple to the complex. Here we’re only going to cover the basics with the use of the NameVirtualHost directive. The advantage of this approach is that you don’t need to hard-wire any IP addresses, and it will just work. The only thing you need is for your domain names to resolve to the IP address of your webserver.
For example if you have an Apache server running upon the IP address 192.168.1.1 and you wish to host the three sites example.com, example.net, and example.org you’ll need to make sure that these names resolve to the IP address of your server.
(This might mean that you need example.com and www.example.com to resolve to the same address. However that is a choice you’ll need to make for yourself).
Since we’ll be hosting multiple websites on the same host it makes a lot of sense to be very clear on the location of each sites files upon the filesystem. The way I suggest you manage this is to create a completely seperate document root, cgi-bin directory, and logfile directory for each host. You can place these beneath the standard Debian prefix of /var/www or you may use a completely different root – I use /home/www.
If you’ve not already done create the directories to contain your content, etc, as follows:

root@irony:~# mkdir /home/www

root@irony:~# mkdir /home/www/www.example.com
root@irony:~# mkdir /home/www/www.example.com/htdocs
root@irony:~# mkdir /home/www/www.example.com/cgi-bin
root@irony:~# mkdir /home/www/www.example.com/logs

root@irony:~# mkdir /home/www/www.example.net
root@irony:~# mkdir /home/www/www.example.net/htdocs
root@irony:~# mkdir /home/www/www.example.net/logs
root@irony:~# mkdir /home/www/www.example.net/cgi-bin

root@irony:~# mkdir /home/www/www.example.org
root@irony:~# mkdir /home/www/www.example.org/htdocs
root@irony:~# mkdir /home/www/www.example.org/logs
root@irony:~# mkdir /home/www/www.example.org/cgi-bin

Here we’ve setup three different directory trees, one for each site. If you wanted to have identical content it might make sense to only create one, and then use symbolic links instead.
The next thing to do is to enable virtual hosts in your Apache configuration. The simplest way to do this is to create a file called /etc/apache2/conf.d/virtual.conf and include the following content in it:

(more…)

No detailed maps found that support routing – Nuvi

I ran into this problem last week.

Here’s the solution:

To install this, please follow the steps below;

Unlock code: They gave the unlock code.

Windows computer:

1) Right click your mouse on the desktop of your computer, then select “New“, then select “Text Document“. This will place a new text document icon on your desktop
2) Double click on the newly created Text Document icon on the desktop to open the text document window
3) Copy the above unlock code into the document.
4) Click “File”, then “Save as
5) In the “Save as” dialogue box, change the file name to gmapprom.unl 
6) Change the “Save as type” to “All files“, then save the document and close it
7) You should see the file “gmapprom.unl” on your desktop as an icon
8 ) Right click on the gmapprom.unl file on the desktop and then select “copy
9) Plug your Garmin device into your computer and then open “My Computer” or “Computer” This will show the devices attached to the computer
10) Double click on the Garmin or Nuvi drive to access the files on the GPS.
11) Right click on the Garmin folder and then select “paste” to past the gmapprom.unl file into the Garmin file folder.
12) Safely disconnect your Garmin device from the computer electronically before disconnecting the cable.
13) Disconnect the USB cable, then power the GPS on…..

Any questions? Drop me a mail.

Install par2cmdline on CentOS 5.x

This has been bugging me for a while.

So, here’s a quick and easy way to do it:

Code:

wget http://garr.dl.sourceforge.net/sourceforge/parchive/par2cmdline-0.4.tar.gz

wget http://sage.math.washington.edu/home/binegar/src/par2cmdline-0.4-gcc4.patch

tar zxf par2cmdline-0.4.tar.gz

cd par2cmdline-0.4

patch <../par2cmdline-0.4-gcc4.patch reedsolomon.cpp

./configure

make

make check

make install # Need to do this as admin

cd ..

Incompatible plugin/extension FireFox 4?

So recently I was faced with a bit of a snag. A user needed a toolbar installed into his FireFox but FF kept on marking it as incompatible.

As usual, browsers like updating their software without caring about the guys who develop the plugins or extensions. This could become quite irritating if you run a lot of them. The best way would be to wait for the developer to bring out a new version that is compatible with the latest version of the browser in question.

However, if you really want that plugin or extension to work, this is how you do it:

FireFox 4.0

1) Open a new tab and type in “about:config” in the address bar.

2) Click on I’ll be careful, I promise! button at the warning prompt.

3) Right click on the window, and select New -> Boolean.

4) Enter extensions.checkCompatibility.4.0 as the preference name.

5) Set its value to False.

6) Proceed to install plugin/extension in question.

PLEASE NOTE: It’s important to understand that not all extension will work perfectly in new version of Firefox, especially when it’s been tagged as incompatible.

Questions?

\