I recently purchased a Windows Vista laptop and it worked great, well as soon as I bumped it to 2 gigs of RAM.   I was able to use the laptop at home and at one of my offices, both were on comcast cable.  I then took the laptop to the warehouse which was on Windstream DSL and to my surprise it would hardly cerf the net because my dsl was so slow.  No mater what page I went to some of the page would show up but it would never load an entire page.  I knew right then that it was most likely an MTU problem.  So I did some research and found that Vista tries to make guesses on what it should set your MTU settings for each connection to.  I disabled this and set my MTU manually to 1430 and walla everything worked like a champ.  Here is what I did…

1. You must get into a command prompt as Administrator.  To do this…

• Click Start and type cmd in the Search box. This should produce a list consisting of one entry: the shortcut to the Windows Command Processor, cmd.
• Right-click the cmd shortcut and choose Pin to Start Menu.
• Click Start again. Right-click the Command Prompt shortcut you just added to the Start menu and choose Properties.
• Click the Advanced button and click to select the Run as administrator check box.
• Click OK to save your changes.         

2. You must tell vista not to autotune itself and to abide by your MTU setting to do this at the cmd prompt type….

netsh int tcp set global autotuninglevel=disabled

3. And finally you must list set the MTU to each interface you want to change.  At the cmd prompt type….

netsh interface ipv4 set subinterface “Local Area Connection” mtu=1430 store=persistent

If you just want to see what your MTU settings are or find other interface names you can run….

netsh interface ipv4 show subinterfaces

Hope this Helps! 

Chris Edwards

Class C
Mask	Notation	Subnets	Hosts
255.255.255.0	/24	1	256
255.255.255.128	/25	2	128
255.255.255.192	/26	4	64
255.255.255.224	/27	8	32
255.255.255.240	/28	16	16
255.255.255.248	/29	32	8
255.255.255.252	/30	64	4
255.255.255.254	/31	128	2
255.255.255.255	/32	256	1
Class B
Mask	Notation	Subnets	Hosts
255.255.0.0	/16	2	65,536
255.255.128.0	/17	2	32,768
255.255.192.0	/18	4	16,384
255.255.224.0	/19	8	8,192
255.255.240.0	/20	16	4,096
255.255.248.0	/21	32	2,048
255.255.252.0	/22	64	1,024
255.255.254.0	/23	128	512
255.255.255.0	/24	256	256
Class A
Mask	Notation	Subnets	Hosts
255.0.0.0	/8	1	16,777,216
255.128.0.0	/9	2	8,388,608
255.192.0.0	/10	4	4,194,304
255.224.0.0	/11	8	2,097,152
255.240.0.0	/12	16	1,048,576
255.248.0.0	/13	32	524,288
255.252.0.0	/14	64	262,144
255.254.0.0	/15	128	131,072
255.255.0.0	/16	256	65,536

The “terminal monitor” command directs your cisco to send debugging output to the current session. It’s necessary to turn this on each time you telnet to your router to view debugging information. After that, you must specify the specific types of debugging you wish to turn on; please note that these stay on or off until changed, or until the router reboots, so remember to turn them off when you’re done.

Debugging messages are also logged to a host if you have trap logging enabled on your cisco. You can check this like so:

        sl-panix-1>sh logging
        Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
            Console logging: level debugging, 66 messages logged
            Monitor logging: level debugging, 0 messages logged
            Trap logging: level debugging, 69 message lines logged
                Logging to 198.7.0.2, 69 message lines logged
        sl-panix-1>

If you have syslog going to a host somewhere and you then set about a nice long debug session from a term your box is doing double work and sending every debug message to your syslog server. Additionally, if you turn on something that provides copious debugging output, be careful that you don’t overflow your disk (“debug ip-rip” is notorious for this).

One solution to this is to only log severity “info” and higher:

        sl-panix-1#conf t
        Enter configuration commands, one per line.  End with CNTL/Z.
        logging trap info

The other solution is to just be careful and remember to turn off debugging. This is easy enough with:

        sl-panix-1#undebug all

If you have a heavily loaded box, you should be aware that debugging can load your router.  The console has a higher priority than a vty so don’t debug from the console; instead, disable console logging:

        cix-west.cix.net#conf t
        Enter configuration commands, one per line.  End with CNTL/Z.
        no logging console

Then always debug from a vty.  If the box is busy and you are a little too vigorous with debugging and the box is starting to sink, quickly run, don’t walk to your console and kill the session on the vty.  If you are on the console your debugging has top prioority and then the only way out is the power switch.  This of course makes remote debugging a real sweaty palms adventure especially on a crowded box. Caveat debugger!

Also, if you for some reason forget what the available debug commands are and don’t have a manual handy, remember that’s what on-line help is for. Under pre 9.21 versions, “debug ?” lists all commands. Under 9.21 and above, that gives you general categories, and you can check for more specific options by specifying the category: “debug ip ?”.

As a warning, the “logging buffered” feature causes all debug streams to be redirected to an in-memory buffer, so be careful using that.

Lastly, if you’re not sure what debugging criteria you need, you can try “debug all”. BE CAREFUL!  It is way useful, but only in a very controlled environment, where you can turn off absolutely everything you’re not interested in.  Saves a lot of thinking.  Turning it on on a busy box can quickly cause meltdown.

This information is reposted from http://www.faqs.org/faqs/cisco-networking-faq/section-9.html

I had a heck of a time finding out how to convert a UNIX time stamp in Crystal Reports.  My company has a ecommerce package that stores all sales date in a UNIX time stamp format.  Which means it stores the time and date by storing the number of seconds since 1/1/1970.   So here is the formula I came up with…

dateadd (“s”,{order.date}-18000, #1/1/1970#)

dateadd function does the trick,  the “s” is for seconds, order.date is the table that contains the unix time stamp, -18000 is -5 hours from UTC in seconds because im in the Eastern Time Zone and 1/1/1970 is the base date for dateadd to add the other argument to.

Hope This Helps!

Chris Edwards

If you want to copy Putty configuration from a Windows computer to another same version Windows computer, here is what to do:

1. On a model computer, configure Putty to your desire, save and test it to make sure it works the way you want it to.
2. Start/Run/regedit to run regedit tool
3. Browse to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys
4. Delete all values under this key EXCEPT the (Default) value
5. Right click on HKEY_CURRENT_USER\Software\SimonTatham and select Export, then save it as “setup-putty.reg” to a location that you want
6. Copy setup-putty.reg and the Putty.exe files to a machine that you want to copy Putty configuration to
7. On this new computer, double click on setup-putty.reg to import Putty configuration
8. Upon successful configuration import, run Putty.exe. You should see all Putty configuration there. You can safely delete setup-putty.reg since you only need to run it ONCE on each new computer that you want to use Putty with tthe same configuration.