Vonage and DSL connections

If you have a Vonage system and you use DSL internet connection and you want multiple phones to work you run into problems with inside/outside wiring.

If you just have one phone that you want connected to Vonage then everything will work out fine. Its when you plug the Vonage Router via the Telephone cable into the phone jack/biscuit you get a busy signal from the phone.

This is because with voltage running through the pair your Vonage system will send a busy signal to the tele set.

To fix this you need to send the voltage through a separate pair on the jack and have the rest of the house set to the other set.

WARNING: NID's come in all shape and sizes. It would be best to research the particular NID you are working on before continuing. Most telephone companies use Red,Green,Black,Yellow wires for working pair. This is not a hard set rule and may be different in your area. I take no responsibility for any injury you may sustain or device's you may break in the process.

For simplicity sake I will use the Red and Green pair as the current pair in use with Black and Yellow as the second pair. The pictures I'll use are random ones I've gotten from the Internet.

On the NID outside the building you will see Red and Green attached to the NID Posts. This picture uses the Red and Blue wires for a live connection.


Looking at this picture you see that Black is twisted to White and Yellow is twisted to Green. The Black and Yellow are the colors from the Telephone company the Green and White is from the installation cable.

The first thing to do is remove the live connection from the NID posts. Unplug the RJ11 connection as the picture shows. I like to mark my wires with masking tape just for reference, because you never know what can come up while your working these. Untwist the ground pair (Yellow, Black) mark them and let hang.


You will now connect the Red and Green that was originally connected to the NID posts to the pair that the Yellow and Black were originally on. Basically just switching the wiring connections.

I recommend using Scotchlok's from 3M to connect your wires instead of twisting them together, but if your in a pinch ~ twist and cap the connections.



Here is a link to Digikey to purchase Scotchloks.

You now should have a Black and Yellow pair to connect. Wrap those on the NID posts the Red and Green were on and head back inside to your wall jack.

At the wall jack you need to remove the Red and Green pair and place the Black and Yellow pair on. So if Red and Green are on the 1 and 2 connects place the Black and Yellow pair on the 1 and 2 and the Red and Green on the 3 and 4.

You now have electricity going to that jack from the NID on the Black and Yellow pair. You can plug in your DSL connection. Turn on the Modem and get sync. This will allow you to get an Internet connection for your Vonage system and computer. You can test this by plugging in a phone to the jack and you should get a busy signal.

All the other phones in the house will be on the Red and Green pair and have no electricity going to them. So when you pick up another phone in the house you will hear no busy signal or dial tone just yourself breathing into the phone.

This is where you must make a decision. You can either run a telephone cable to a non charged outlet or you can wire up a dual jack wall plate.

Here is a crappy picture of the reverse side of a dual jack plate.

I prefer the dual jack method. This way you have a live DSL connection and a dead Vonage connection all in one spot.

To do it just connect the Red and Green pair to the 1 and 2 connects on the plate back. just as all the others in the house were/are. All wall plates are wire color coded to make things simpler.

I can only recommend that you test continuity with a tone tester or at least a voltmeter before you plug your phone in. Also make sure you close up your NID box outside to protect if from the weather once you are finished.

This may seem confusing while reading it, but once you get into it you will see very quickly what is going on. You are just taking voltage from one set of wires and putting it on another then ending that connection on the other end.

I've run into problems with older house wiring that this will just not work due to other IW issues. I cannot stress enough that color scheme and NID types vary all across the world and this blog post is by no means an end all solution to the DSL Vonage problems. If you continue to have problems you can also check on the Vonage forums.

JS

Telnet in Vista

What happened to Telnet on the Vista OS?????

Telnet is a great application for basic remote administration of computers. Sadly in Vista though it is turned OFF by default. This only adds to the frustration that is the Vista Albatross.

To turn it on you have to get to Programs and Features in the Vista complex. To get here do this:

Start Pearl > Control Panel > Programs and Features > Turn Windows features on and off (Left Hand Side of Window on bottom) > Telnet Client

Enable it by placing a check mark beside it and click OK and/or Close X all the way out to the desktop. Now go to the Run command and type in telnet.

A telnet session will open allowing you to connect to a remote host device.

Frustrating at first, but easy to remedy in the end...

JS

HyperTerminal Alternatives

When consoling into a router you have generally use some type of program to view the internals of the router. For Cisco routers I used to use Hyperterminal. It is a free program and is included on all Windows OS pre Vista.

You can find it under the Programs || Accessories || Communications || Hyperterminal

If you would like Hyperterminal on your Vista OS you can still get HyperTerminal from Hilgraeve, the company that created it, but you will have to purchase the Personal Edition. Link Here

One thing comes to mind when thinking about Hyperterminal. That is the burning, dizzying sensation I get from looking at black on white text for over two hours.

As great as Hyperterminal is or was there are alternatives out there for the Windows and Linux systems.

Tera Term:

This product was created in 1996 by T. Teranishl for the Windows 3.1/95/NT/ it supported Telnet, SSH and serial port connections. The new version picked up where the older one left off and is still free with a ton of extended options.

You can customize Tera Term to look how you would like. I prefer the Green text on Black background ala the Matrix code.

Real Term:

For Linux I prefer Real Term. It looks a lot like a tty connection, but has a GUI at the bottom of the screen that allows for serious configuration and testing. It can be used for far more serious stuff than just a simple COM connection. I have never used it though for anything more than a tool to get into a Cisco router.

These are just two products from many that are out there that I prefer. I am sure there are better tools out there so do a web check and see what you can find and let me know.

JS

Making your own Butt Set

My beautiful Butt Set broke on me while on site one day and I had to make one on the fly to get the job done this is what I did....

To make your own Butt Set, Linemans Headset, or Beige Box you will need:

A land line phone (not a cordless phone)
Two alligator clips
Soldering Iron and Solder
Scissors or wire cutters

Remove the cord from both ends of the phone.

I prefer to use the straight cord with the RJ11's and not the curly cord with RJ11's. It just gets all tangled and creates an unruly mess.

Cut one end of the cord and peel back the vinyl/plastic coating exposing the wires bare with the scissors or wire cutters.

Split open the wire end/open end of the alligator clips so you will have room to drop solder onto the wires and have a clear view of what you are doing. Scrap the open end of the clip with your Scissors to remove any coatings that are put on the clip at the manufacture leaving bare metal to bare metal connection between the wire and clip.

Place the Green wire onto the end of the alligator clip and drop a little bit of solder on it making a clean connection. Let it cool.... Be careful the clip connection is delicate and can break easily.

Now do the same with the Red wire.

Color code is not really an issue just use two wires from the cord and solder them onto the alligator clips. I try to keep them color coordinated for detail and simplicity. These will be connected to the posts later for call outs.

Now that the clips have been added to the wires plug the other end into the phone set. Make sure the phone is on Tone not Pulse.

You now have a working Butt Set and to test it you can either go to a 66/100 block, open up your phone Biscuit or go to a NID splitter and connect the one clip to one post and the other clip to the other post and make calls.

I didn't go into great detail or add pictures to this because Butt Sets can be used illegally. If you have any type of Telco experience you will understand this tutorial without any further explanation.

Vonage and Multiple Phones

Vonage is a great service. It works with just about every existing phone set up there is. Well.... almost.

I've been on some calls and seen some pretty crazy stuff that was unfixable. Usually it's the inside wiring that needs to be replaced or some rouge phone that won't work, because it was installed oddly.

Some of the easier calls I get are when a customer has multiple phones and only one is ringing through Vonage.

This is a very easy fix.

First you have to make sure that at least one phone is working with Vonage. That will make sure the electricity is off the NID and disconnected from the telephone pole and the number was ported on Vonage's end. If you don't hear any static or a busy tone or any other strange issues then you can assume all is well.

You will need:

Phone Line Splitter
2 Telephone Cords

Use a telephone line splitter and plug it into a wall jack where your old phone used to be when you had a Telco carrier.

Plug one phone cord into one side of the splitter and run that to the telephone that was plugged into your Vonage router/ATA.

Plug another phone cord into the other side and run that to the Vonage router/ATA where the working phone was plugged in at.

Working Diagram:

After it set up you can do a test call to 1-800-444-4444 and you will get a read back from MCI about what number you are calling from.

This seems like a no brainer and to regular telco guys in the field this is day one stuff, but I can't count how many calls I get that are all fixed with this set up. I just keep in mind that this is the stuff I get paid to know not the customer and I always explain to them what I did and how it works when I am finished.

If you want more in depth discussion about Vonage's Services and fixes for complex or baffling problems with the Vonage Service go to the Vonage Forum. Here you will find other field techs and intelligent people with WAY more experience than me that can answer just about every question you will have.

JS

Wireless Setup Extended...

I want to expand upon the previous post of the wireless setup.

When I stated that you should use the same SSID that was for the simplicity of network identification. If you have a Public and Private network make one named Private so you know when setting up the AP's that it needs to have access to all things company shared. Mark the other network Public to keep it Internet accessible only. It's all about ease of installation and documentation.

Speaking on ease of installation another thing that helps is keeping all of your devices within the same block or row on your switch. It will be easier a year down the road when you are looking at documentation when problems occur and it will be easier for everyone when you are finishing the installation and go to jack all the ports.

I've done installs where the switch had every other port configured to VOIP then every other port configured to computers and 4 ports in the left and right block dedicated to the printers with two ports configured for trunking. What a mess this makes. It is so confusing to the installers running data lines and to any future network admins reading your documentation. Before you know it you have a spaghetti mess of cables, everyone is confused and the install doesn't look professional.

Some would say a set up like that is for security purposes so if someone gets in they will not know where they are at. I agree to an extent, but really, if some hacker gets into your router/switch you failed. It wouldn't matter anyways - if they have gotten this far then they will know the difference in set up on port configurations to get to the proper devices.

Anyways enough of that stuff. Here are my recommendations for wireless AP setup:

Step 1: Test your switch by connecting into it with a cable and see if DNS, DHCP, etc... is set up correctly and you can get out to the Internet.

Step 2: Plug in your WAP and test it with any of the tools mentioned before or even your Windows Network Finder application. Verify it is running and the SSID is what you set it to.

Step 3: Do some testing with the encryption turned off. Make sure you can access file shares or what ever it is that you want the client to do when this is fully functional. This will keep things simple and easier to trouble shoot if a problem arises.

Step 4: Add PSK, WEP, or WPA authentication and connect with a simple Pre Shared Key. Check all file shares and verify Internet connectivity.

Now that you see everything works finish up and set up your AP for proper security authentication to lock it down. Finalize the network for whatever your organization will need for security and take the AP to the desired location in the building and add it to the network permanently.

Ideally you would want to do this in a lab setting, but in most cases (at least for me) it is done on the fly in a production environment after hours.

JS

Outlook and the wrong MAPI

After installing a trial offer of Microsoft Office 2007 you have the option of purchasing a copy, use the current copy in limited form, or uninstall it.

If you try to reinstall Office 2000 or Office 2003 over the copy of Office 07 then start Outlook you will get a warning pop up stating that you are using the wrong version of the MAPI32.dll file.

First thing to do is remove MS Office 07 from the Add/Remove Programs applet. After this you have two options of getting this fixed.

Option 1:

Go to C:\winnt\system32 or C:\windows\system32, double-click Fixmapi.exe program.

If you can't find the program and don't want to take the time to search for it try -

Option 2:

Find the MSMAPI folder. It should be located at C:\Program Files\Common Files\System\MSMAPI and should contain a folder called 1033.

Rename the MSMAPI folder to MSMAPI.old.

Close all the windows and start Outlook again.

I used C:\ as the primary drive for this example. If you cannot find the folders where the example stated then do a search for them and you should be able to find them.

JS

Wireless Network Setup and Channel Crossing

When you have a large area that will be covered by multiple AP's (access points) some strange things can happen. Interference is a big one. You can get interference ranging from microwaves all the way up to brick walls.

One thing to keep in mind is what type of wireless are you setting up. A\B\G\N (N is not yet released) are the flavors that are out there. I won't get into the specifics of the data bits or ranges, but it is good to know that B\G\N can work together or are cross compatible and backwards compliant. What is important are the channels they work on. For both B\G you get three clean channels from each those being 1,6 and 11.

Before installing the framework and have a working Internet connection it is a *great* idea to map out where you will install the AP's. I made the mistake of not mapping one time... never again. Start mapping out/site survey with your laptop and the free program Netstumbler. See if there are any other networks in the area what the SSID's are and what channel's they are operating on. Speaking of SSID's I recommend keeping them all the same for your network.

Depending on what type of wireless protocol you use, encryption level, outside interferences and other wireless networks in range you can map out the full network and install it in no time at all. Honestly the hardest thing about setting this up are the data runs from your framework.

Just for simplicity sake I will start with channel 1 on the first AP using 802.11g standard and no interference. Set your first AP 125ft - 150ft from your framework configured on channel 1. From that point map your next cell 125ft - 150ft away and use channel 6 then for the third AP use channel 11. Never crossing the same channels.

All of this changes when you have multiple flooring schemes and firewalls (the real brick and mortar kind) in the way. The point I'm making is that if you have all three AP's on say channel 6 they will cross each other and cause network connectivity issues/drop outs and disruptions. You should never have two AP's crossing each other on your network or others that are on the same channel.

After you have everything installed and working do another site survey and verify all of your AP's are on different channels, overlapping, the SSID's are the same, everything is encrypted and signal strength is strong. Store that data for future changes that may come about.

If you want a really good wireless networking tool that is far more advanced than Netstumbler I suggest Kismet and Cain and Able. I absolutely love both of those tools, but offered Netstumbler for ease of use and graphical depictions.

J

SBS Wizards won't come up

So this week was pretty busy. From my last post I was in a server closet rebuilding a network and as I was updating SBS Premium 2003 with service packs I updated my blog.

After I was finished with the updates I continued with the process of adding users and computers, configuring reports and backups as is typical with the SBS To Do List. Well, well, well.... wouldn't ya know it - none of the wizards worked.

This wasn't the only problem with the install I also had issues with Exchange not installing or some of the other Support Tools. So the first thing I did was to reinstall the Server Tools/Console.

To reinstall the Server Tools do this:

Place Disk 1 in CD player and either through autoplay or by drilling down to the setup.exe file choose the Set Up Windows Small Business Server on the SBS Splash Screen.

It will run through it's processes and end up on the Welcome to Microsoft Windows Small Business Server Setup page. Click Next three times until you are at the Setup Requirements page.

Here you will click on the down arrow next to the Server Tools list and choose the Maintenance option. This will open up the secondary options. Next to Administration
click the down arrow and choose Reinstall.

Click Next twice and then Finish. Once it is done it will ask you to restart the computer go ahead and log on as Administrator to finish the install. Try the wizard again.

In my case it didn't work for the wizards. So I went ahead and switched the DEP settings to Turn on DEP for all Windows Programs and Services only. This has happened to me a couple times and it soooooooooo frustrating to have Microsoft break their own equipment with Service Packs and Upgrades, but it is not that uncommon with them.

To turn on DEP as stated above:

Go to My Computer, right click and choose Properties. Click on the Advance tab and click on the Performance Settings button. Choose the Data Execution Prevention tab and choose Turn on DEP for all Windows Programs and Services only.

Restart the Computer. Log on as Administrator and try the wizards again.

Both these steps worked for me with the last one being what allowed for the wizards to function properly again. I was able to finish the install and get the clients back into the network properly with a User Migration from the //servername/connectcomputer set up tool.

DO NOT, DO NOT, DO NOT add users and computers like you do in Windows Server 2003 from the AD. If you do the first thing you will notice is authentication problems, next you will see your Default Domain Policy is not being recognized by the clients, due to no authentication within the directory. With SBS you MUST use the wizards for everything.

J

Windows Install Stuck at 31 Minutes

I am writing this from a server closet on a Sunday night. I know I will not have anytime tomorrow for a blog update so I'll get to it right now.

If you have ever done a Windows installation of any type you know that every once in a while you will get a frozen install. One of these day's Microsoft will realize that it is OK to install a bare application system and add the rest later as most if not all Linux installs do. Anyways.....

If you see on the left side of the screen something like:

Setup will complete in approximately: 31 minutes and you have a green bar at the bottom saying Installing Network Components or something and it hasn't moved in like 4 hours. There are some things you can do as Windows installs.

To get a better look at what is being installed press Shift + F11. This will pop up a installation window with better information as to what is being installed and what is really going on.

Another thing you can do is bring up a command prompt with Shift+F10. Depending on where you are in the installation you will be defaulted to the C:\Windows\System32> prompt. If you are in something like C:\Windows\System32\inetsrv do a folder change with the ( ../ ) command and come back a folder or two if need be.

From the System32 folder you can now open things like Task Manager (taskmgr.exe) and get to a GUI for visible files and folders. From the Task Manager you can also see what is taking so long in the processes tab and maybe stop the process to finish the install. Here you will find the errorlogs and other files that could help you with troubleshooting your installation.

Well back to work for me I have a long night ahead.

J

Gmail, Vista and Remote Tools

The other day I posted about switching your Gmail account to a secured connection. If you have the Gmail notifier program running also, it will not work with HTTPS unless you add a registry key/value.

Here are the steps directly from Google on making both the HTTPS connection and Gmail notifier work properly:

1. Download http://www.google.com/mail/help/downloads/notifier_https.zip
2. Open up the folder.
3. Double-click on the file called notifier_https.reg to install it.
4. Click 'yes' when you're asked to confirm if you want to add the
information to the registry.
5. Restart the Notifier.

There are two files in that download and they come compressed or zipped. You can run it from the zipped folder without unpacking it into another folder. The first file is the one you want to use.

Vista and Remote Log In:

You cannot remotly log into Vista Home Premium and you cannot *Upgrade* to Vista Business from VHP for the log in capabilities. It is considered a downgrade going from VHP to VB. You have to upgrade to Vista Ultimate to have the ability of remoting into the machine. I figured this out the hard way at 4 A.M. 13 hours into a very long day.

There is a hack that someone created pre Vista SP1. It worked great then MS plugged that hole and the second release of the hack didn't work so well. If you want to attempt to use that hack google Vista Home Premium Remote Hack and it will turn up.

If you would still like to remote into your VHP computer without adding hacks or spending the extra $$$$$ for Vista Ultimate try LogMeIn.

It is a free service for one computer account and offers a ton of other options if you would like to buy. It has a slick interface and the ease of use is off the charts.

You will have to go to the site and install the software onto the computer you would like to connect to. LogMeIn will add this computer to the account and then you can connect to your computer from any place that has an internet connection.

For those people out there who are not the most computer savvy LogMeIn offers support files to download if you would like more information on how to use the software.

I've also used LogMeIn's Hamachi a long, long time ago. It worked as a secure VPN tunnel that was needed while I replaced a router and allowed for production to continue while I waited for my new router to come in and get configured for the sites VPN.

J

Loopback Plug's (T1 and Ethernet)

The other day I was installing a router and switch that needed to be trunked to a preexisting switch and a new firewall.

There were two T1 lines that needed to be routed before the VLAN's could be configured. Well the one T1 was not working and I had to trouble shoot what was going on. In doing so I created loopback plugs on the fly to test the ports for connectivity.

Loopback plugs are not only great for loopback tests, but they can save a little bit of time to see if a port is working without consoling in. That was one part of the trouble shooting was to see if the T1 module on the router was operational. I plugged in the loopback plug and the status was green. With the cable coming from the jack to the router it was red.

In the end it was an ISP issue. They inadvertently crossed the tip and ring set and it was an easy fix.

To make a T1 loopback plug do this:

Cut about 1 foot cord of twisted pair and strip off the casing that holds all the pairs together. Usually it's blue, grey, yellow or green. Untwist on paired color. I like to use the dark colors just so I can see where they are going in the RJ45 end.

Get a RJ45 end. The slots are numbered with the clip facing down towards your feet 1 - 8.

Insert one wire into slot 1 and the other wire into slot 2.

Insert slot 1's other end into slot 4 and slot 2's into slot 5 and terminate or crimp the end.

So the short description is 1 to 4 and 2 to 5 and you will have about 6 inches of wire hanging out. I put masking tape on these wires just for easy handling when removing it from the port. I would label it also for future use.

To make an Ethernet Loopback Plug do this:

Follow the exact same steps above. The only thing that changes is the pin count.

Place a wire end into slot 1 and another into slot 2.

Take slot 1's end and place it into slot 3 and take slot 2's and place it into slot 6.

So the pin count is 1 to 3 and 2 to 6. Crimp, tape and label.

Remember: A T1 loopback plug is for T1 ports it will not work with Ethernet ports and vice versa.

These are very easy to make and will save you a little bit of time and money in the long run.

J

Exchange, ESEUTIL and the Dirty Shutdown

It is pretty easy to tell when your Exchange server bit the dust. Nobody is getting emails and your ear is ringing from the everyone letting you know this. You get to the Mailbox Store and Public Folder Store and they are unmounted with a big red X covering them. You right click and mount the volume only to be denied.

This is when you have to check for a dirty shutdown and corrupt files in the Exchsrvr folder.

I am forewarning you though. This tip sometimes has the ability to make things worse due to file scrape and deletion. MS support will not like to hear you did this this trick that was created by them. So make sure you have TWO backup copies of the files we are going to work with. So if the first one dumps and you need MS support you can use the second copy and they will be none the wiser.

Here is what to do if you cannot mount your stores:

Find the location of all the important files:

C:\Program Files\Exchsrvr\MDBDATA

Stop all the MSExchange Services on the server then copy the folder MDBDATA to the desktop. Inside this folder is the store files.

From the same location as the MDBDATA folder copy the bin folder and paste it to the local C:\ this will make is much easier to run the eseutil tool from the command prompt.

Now start a command line session and get to the bin folder and use the eseutil tool:

C:\bin\eseutil /p "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
C:\bin\eseutil /p "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"

This will check the database integrity and repair any problems it may find. If you want a real in depth definition of what is going on look on the Microsoft Web Site or google eseutil.

It will give you a running percentage of the check status on the command line screen. You may also get prompted as to whether or not you really want to do this. As long as you have a second copy of your MDBDATA file you will be OK.

Now that the scans are finished delete the .log and .chk files located in the C:\Program Files\Exchsrvr\MDBDATA one by one. Resist the temptation of selecting them all and deleting. You will run into a problem and won't be able to delete them. At least this is my experience.

Now run a defrag on the pub1.edb and priv1.edb files with the commands:

C:\bin\eseutil \d "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
C:\bin\eseutil \d "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"

Once this is complete go back to your Exchange Services and restart them. Then go back to your Mailbox Store and Public Folder Store and remount them. Send out some test emails and pray for the best. If you get to the point where you will need to call MS support you can copy the files from the original MDBDATA folder from the desktop back into the one you were working on at anytime.

I hope this helped somebody out there. It took me about three days to figure this out, but once I knew it I never forgot it and I've used it more than once.

J

Gmail SSL, bad start, and stress induced coma's

Wow..... What a day.

Started off late and it set the tone for the day. Cell phone died right in the middle of a tech support call with a spectacular customer of mine. I was on the road and didn't have my charger with me.

Got on site to another spot and was 5 minutes late. I thank the Lord for understanding people.

While on site I remoted into my other customers server only to find that Active Directory was destroyed due to a power surge and a dirty shutdown. They were dead in the water and I was 100 miles away. In the end I got them up to a working state, but not how I would like to have left it by any means.

It just got better from there.... At one point I swear my brain shut down and I went into a coma or was that auto pilot?

Anyways on to the good stuff:

If you own a Gmail account I highly recommend you turn on the SSL in the settings. Back in August of 2008 Some ingenious technological aficionados showed the world that it was very easy to hack Gmail accounts. Especially if you surf on an unencrypted network like the one at your coffee shop or the airport.

I won't go into great detail about it, but if you are interested here is a link:

http://www.hungry-hackers.com/2008/08/gmail-account-hacking-tool.html

To turn on SSL for your Gmail account do this...

Log into your Gmail account and go to settings (upper right hand corner)
Scroll down until you see Browser Connection
Choose Always Use HTTPS
Click on save button and log back in

I'm bringing this up because I was on an unencrypted network today and was thinking "What if the computer I was using had a key logger? What if my Gmail got cracked.. Well at least I got half of it covered with SSL"

This brief thought came between my stress induced coma and my coffee fueled awakening.

J

Cisco Login Banners

One thing you see a lot when working with routers and switches are the banners at the top of the page or window when you telnet or console into them.

Some of the funnier things I've see where:

Warning! You are about to enter the Matrix. There is still time to take the Blue pill and disconnect from this madness.

another one I remember:

Incorrect passwords will result in a virus being uploaded into your computer. Please type carefully...

Password:

and the oh so simple:

I do not like you. Go away.

If you ever wanted to add a banner to your router or switch it is a simple thing to do. You must use delimiter character such as # or $ before and after the message. This character (*) can out line your text for some extra flavor.

After consoling into the device and enabling it type:

(Example)
router#config t
router(config)#banner motd #
**********************************
This is where you put in your message
**********************************#

After some playing around you'll get the layout correct and have yourself a very witty banner for all to see in no time.

J

First Post and Random Thoughts...

Hi,

This will be my first post for this blog. I am setting this up to possibly help others out there with some of the everyday odd things I come upon in my travels and possibly save other some time, stress and money.

My passion is computer networking on a small scale. I am not interested in large corporate networking models and how they interact across the globe. I've worked and learned in those environments and it does not fulfill my curiosity as does the small networking environments do.

I enjoy working with small business owners in creating networks that rival some of the larger industries I've worked with. Securing the network and making a work of art from pure chaos. I find fulfillment in repairing home users computers and being able to explain what happened, how it was fixed and how to avoid it in the future.

In my blog I intend to post information about everything from Cisco Routers and Switches all the way down to thermal paste for your computers processor. The only rhyme or reason to my posting will come from what I had been doing that day. If one day I am configuring a Cisco or Adtran Switch I will probably blog about it and if on the next day I am uninstalling McAfee I might blog about that.

I assume most who start blogging feel the same as I do now. I am not too sure how this is going to work, but I'm not afraid to try....

J