In OS X Lion Apple changed how you access the TFTP server. Below are the steps for editing the default location of the TFTP server and launching it.
- If you'd like to change the path the TFTP server uses you can create a directory wherever you'd like and name it tftp. If not skip to step 3 but be aware you won't have direct access to the default folder location which is /private/tftpboot
- First let's edit the tftp.plist file to point to the new location
- Open up Terminal
- type sudo nano /System/Library/LaunchDaemons/tftp.plist and press enter
- Type in your password
- Using the arrow keys move the cursor the the <string>/private/tftpboot</string> location.
- Replace the path <string>/private/tftpboot</string> with the location you chose. I put <string>/Users/USERNAME/tftp</string>
- Press control + X and Y to save.
- Load and launch the TFTP server
- In Terminal type sudo launchctl load -F /System/Library/LaunchDaemons/tftp.plist and press enter
- Next type sudo launchctl start com.apple.tftpd and press enter
To confirm it is up and listening type netstat -a -p udp | grep tftp into the Terminal window and press enter. You should see something similar to this...
udp6 0 0 *.tftp *.*
udp4 0 0 *.tftp *.*
If not then the daemon did not start correctly. You may need to check the plist file for any errors.
I got some of my info from The Weezey Geek but felt it wasn't a complete tutorial. I wrote this up to hopefully give people a start to finish guide on editing and starting the TFTP server.
I recently needed to get a screenshot tool and saw the makers of Snagit had a free tool called Jing. After some research I found a comparison between the two.
If you're like me you have a wired and wireless connection at work. When your accessing your server or other network resources you want to make sure your PC uses your wired connection over your wireless connection without having to manually disable the wireless adapter. You can set the order in which the network connections are accessed in Windows XP, Vista or 7.
In Windows Vista or 7
- Click the Start button then Control Panel
- Click View network status and tasks
- Click Change adapter settings in the left side bar
- Press the Alt key to show the file menu and click Advanced then Advanced settings...
- Order your network adapters by using the arrows on the right...
Lately I've had a few users who's PST has gotten corrupt and been unaccessible at the 19GB mark. After doing some research I discovered the default unicode PST size limit in Outlook 2003 and 2007 is 20GB.
By default, .pst files are in the Unicode format in Outlook 2007 and in Outlook 2003. Additionally, the overall size of the .pst files has a limit that is more than the 2-GB limit that is imposed by the ANSI .pst files. By default, the limit for a Unicode .pst file in Outlook 2007 and in Outlook 2003 is configured to be 20 GB.
To resolve this I run scanPST.exe located in C:\Program Files (x86)\Microsoft Office\Office12 in Windows 7 or C:\Program Files\Microsoft Office\Office12 in Windows XP if you have Office 2007. Once that completes you'll have a functioning PST. You can open it in Outlook but it will become corrupt after you start using it again so this isn't an option.
The best way to deal with a large PST is to split it into multiple smaller PST files and access them as needed. A great free tool for this is MailScavator.
First choose your Outlook profile then choose which PSTs you want to work with.
Third you choose where you want the PSTs saved. Fourth you choose the size and how you want to split them.
You can filter what emails you work with by selecting Dates, addresses sent by, received by, or certain text in the message.
Lastly you can logging and choose whether or not you want to move, copy, or scan. I typically move as the original PST is worthless at it's current size. Now click Start and let it works its magic.