URL Best Practices

URL Best Practices
Do’s
1. Whenever possible, use YourBrandName.com.
2. If .com is not available, use YourBrandName.net.
3. If .com and .net are taken, find a new brand name. Seriously.
4. Use YourSlogan.com when running an integrated media campaign.
5. Use subdomains when driving people deeper than your homepage — e.g. Product.YourBrandName.com. The eye is trained to look for a domain and ignore everything that comes afterwards so slashes don’t work.
6. CapitalizeTheFirstLetterOfEachWord and/or UseDifferentColorsOrBoldToHelpEachWordStandOut

Don’ts
1. Don’t use acronyms, abbreviations, or numbers unless your brand is widely known as such.
2. Don’t use YourProduct.com or YourCategory.com as a replacement for YourBrandName.com. They should only be used as a supplement.
3. No-hyphens/or slashes.
4. Don’t include www (aka dubs) when displaying your URL. We know to go to the World Wide Web to find you.
5. Don’t include http://. If your audience isn’t web savvy enough to know where to type the URL, you shouldn’t have a website.
6. don’tusealllowercase (canyoureallytellwhereonewordendsandthenextbegins?)
7. DITTOFORALLUPPERCASE
8. Don’t
Stagger
Words
On
Separate
Lines
9. Don’t bury your URL at the bottom of an ad. I’m the only nerd running around with a 10x zoom lens to find URLs.

Limited Connectivity problem in LAN connection.

After installing Windows XP Service Pack 2, you may receive
the following error message in the System Tray.

Local Area Connection:

This connection has limited or no connectivity. You might not be able to access the Internet or some network resources. For more information click this message.

“This connection has limited or no connectivity. You might not be able to access the Internet or some network resources. “

Solutions to the problem are varied, however most of the solutions found on the web just mask the problem by simply guiding the user through turning off this notification. Now this solution may work great for systems that are showing a false positive error, but what if the system genuinely has lost its local area connection or the connection is unstable, what then?

One possible answer involves a bug in Service Pack 2 of Windows XP dealing with a loss of network connectivity for workstations that use Microsoft’s L2TP-based virtual private networking (VPN) client to connect to servers that are connected to NAT-based networks. However, this bug seems to appear in situations that are not associated with VPNs either.

If patching Windows XP for this bug does not fix the problem, read through the list below of other causes and fixes. You may have to reinstall your firewall, rebuild the configuration in your router, drop your connection speed from 100Mbps to 10Mbps, or assign static IP addresses to your computers in the network to resolve this issue.

 

How do I know if my system is affected by this bug?

If you have installed Windows XP Service Pack 2 and are experiencing any of the following symptoms, this bug is affecting your system.

• After installing Windows XP SP2, your network connection reports a problem with “Limited or No Connectivity”

• You have trouble connecting to the Internet or your local area network after installing Windows XP Service Pack 2.

• Your network connection gets stuck “Acquiring IP Address”

What Steps Can I Take to Fix This Problem?

If you are receiving this error, you should run the Microsoft patch (KB884020) for it. Follow the instructions below to do this. Alternatively, you can download a zip file with the patch, registry file, and instructions by clicking here.

1) Download the patch from Microsoft’s site
2) Run the update to install it
3) Run this short Registry fix to complete the update. Type the following lines in Notepad and save the file as FixReg.reg on your desktop, then double click on it to install into your registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IPSec]
“AssumeUDPEncapsulationContextOnSendRule”=dword:00000002

4) Reboot your computer

If you experience the error message again, reboot your computer first. In most cases this will solve many connectivity issues that are not associated with this SP2 bug.

My Connection Works, Can I just disable the warning message?

If your local area connection is working properly and you simply want to disable the warning message follow these steps.

1) Open Control Panel
2) Open Network Connections and Right Click on the Local Area Connection and click on Properties
3) Uncheck the following option on the General Tab

“Notify me when this connection has limited or no connectivity”

4) Click OK and close the Network Connections window

What If Installing this Patch Doesn’t Help?
Other Causes For This Problem

If you are still experiencing this error message even after running the patch shown above, you may be experiencing one of several problems shown below:

1) Your Network or DSL router may have bad or missing information. Powercycle your router and/or rebuild the configuration in your router.

2) Double-check your cabling to the computer. Make sure you have the correct type of cabling, straight-through CAT 5 or possibly a crossover cable and try another cable or test the cable to make sure its working properly.

3) Check your network card to make sure its configured correctly and working properly. Many times setting the network card to 10Mbps/Full Duplex will solve this issue. To do this, open Control Panel, System, Device Manager. Go to the properties of the Network card, click on the Advanced tab and find the Link Speed and Duplex section. Change it from Auto Detect to 10Mbps/Full Duplex.

4) Check and test your firewall. Your firewall, especially if its a software firewall like ZoneAlarm, Black Ice, Norton Firewall or something else could be blocking the connection. Disable your firewall and test the connection. You may have to resolve the problem by even uninstalling and reinstalling the firewall.

5) Check your IP address assignments and workgroup settings in the computer for accuracy. Statically assign IPs to the computers in your network.

6) Reset your TCP/IP stack by downloading and running WinsockXPFix.exe a Visual Basic program designed to fix corrupted TCP/IP issues, host file problems and a variety of other connectivity issues.

Note :

In most of the time, You just remove network cable and connect once again. It will work fine.

Regards,

P.Raveendran.

Folder Lock

Hi All,

Many people have been looking for an alternative way to lock folders without the use of any software. So, here you go.

Open Notepad and copy the below code and save as locker.bat. Please don’t forget to change your password in the code it’s shown the place where to type your password.
Now double click on locker .bat
First time start, it will create folder with Locker automatically for u. After creation of the Locker folder, place the contents u want to lock inside the Locker Folder and run locker.bat again.

cls
@ECHO OFF
title Folder Locker
if EXIST “Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}” goto UNLOCK
if NOT EXIST Locker goto MDLOCKER
:CONFIRM
echo Are you sure u want to Lock the folder(Y/N)
set/p “cho=>”
if %cho%==Y goto LOCK
if %cho%==y goto LOCK
if %cho%==n goto END
if %cho%==N goto END
echo Invalid choice.
goto CONFIRM
:LOCK
ren Locker “Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}”
attrib +h +s “Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}”
echo Folder locked
goto End
:UNLOCK
echo Enter password to Unlock folder
set/p “pass=>”
if NOT %pass%== type your password here goto FAIL
attrib -h -s “Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}”
ren “Control Panel.{21EC2020-3AEA-1069-A2DD-08002B30309D}” Locker
echo Folder Unlocked successfully
goto End
:FAIL
echo Invalid password
goto end
:MDLOCKER
md Locker
echo Locker created successfully
goto End
:End

Regards,

P.Raveendran

jazzezravi@gmail.com

+919941414834.