May 10, 2010

i7 Hackintosh with Snow Leopard - Round One

Filed under: Network Admin — Tim @ 1:40 am

Apple knows how people think, work, and play. I’ve always admired the sheer usability of Macs. I make a living in the PC world, however, so I never had the time, inclination, or money to jump in to the world of Jobs. But after getting my feet wet with a virtual machine of Snow Leopard, I was left wanting more. What I found as I delved deeper into the community known as OSX86, was a way to get the Mac experience on PC hardware.

After a failed attempt to install OSX on a laptop, my desire to see Snow Leopard on my desktop intersected with the parting out of my old workstation. Ebay was kind, so I returned the favor by purchasing tried and trusted hardware for my PC/Mac, as follows:

The compatible important stuff:

  • 2.66GHz Intel Quad-Core i7 920
  • NVidia GeForce 9800 GTX (XFX branded)
  • Gigabyte GA-EX58-UD5

The other stuff

  • Antec P183 Case
  • Antec CP850 Power Supply
  • Kinston SSDNow V Series 64GB SATA Solid State Drive
  • Noctua NH-U12P SE1366 for Intel LGA 1366 4 Dual Heat-Pipe CPU Cooler

Stay tuned for the build, install, testing and conclusion!

TC

February 16, 2010

Going Google: in more ways than one

Filed under: Network Admin — Tim @ 5:55 pm

So Google has announced it’s plans to test “ultra high-speed broadband networks” in “one or more trial locations” in the US, and the (high) band(width) wagon is already getting crowded!

 Google wants to do this fast, so the more cooperative the municipality comes across, the better the chances are they will be selected.

 Google mentioned “bandwidth-intensive killer apps” and you can bet the communities that are chosen will get to see some of them.

Here are some of the interested parties:

Seattle, WA  -  Columbia, MI  -  Duluth, MN - Madison, WI

October 7, 2009

Good Food/Bad Food for Men

Filed under: Network Admin — Tim @ 3:08 pm

From Dr. Oz:

5 to avoid:

High Fructose Corn Sweetener
Sugar
Enriched White Flour
Trans-Fat, Hydrogenated anything
Saturated Fat

GOOD FOODS

Antioxidant Rich Food:
Tomatoes, Broccoli, Red/Kidney/Pinto Beans
Blueberries
Artichokes
Dried Prunes

Omega 3 Foods:
Fish
Ground Flax Seed
Walnuts (12)
Salmon
Scallops
Soybeans
Squash

Fiber Rich Foods
Lentils
Black Beans
Peas
Raspberries
Pine Nuts
Oatmeal
100% Whole Grain

Olive Oil

And take a multivitamin, 2500 units or less Vitamin A, no iron.

December 12, 2008

New Blackberry Storm: eWeek Got it Dead On

Filed under: Network Admin — Tim @ 10:16 am

The eWeek review of the Blackberry Storm is right in line with my experience so far. Overall I’m happy with the device, but it could be faster (especially the accelerometer) and have iPhone like scrolling.

We’ll see if it improves with software updates!

TLC

December 4, 2008

It DOES Work!

Filed under: Network Admin — Tim @ 9:37 am

Regarding the BBS I installed: it took a little configuring but it does work well. Apache is fast and phpBB3 is an excellent package.

TLC

October 21, 2008

Creating a Simple Knowledge Base using WAMP & phpBB3

Filed under: Network Admin — Tim @ 8:07 am

I wanted a way to store support information in a way that makes it available from any PC, is searchable, and easy to manage.

I THINK this will work. On a Windows XP workstation I installed Apache, MySQL and PHP using the WAMP installer, then installed phpBB3. I like that phpBB3 can be customized, and I have used it in the past. Even if I am the only one to use it, it will be a great repository for me!

TLC

August 19, 2008

Network Boot with Windows Server 2003

Filed under: Network Admin — Tim @ 10:57 am

This is a quick guide how to set up a password protected network boot menu without using windows RIS. This is handy for booting various network boot disks for machine imaging and maintenance.

First off you’ll need the following:

1. A copy of PXELinux
2. Some floppy disk images (or winimage to create some)
3. A bit of time and patience

Now First you have to configure your DHCP server:

  1. Open the DHCP control panel from administrative tools.
  2. Expand the server you are wanting to configure. Expand the “Scope” folder. Right click on “Scope Options” and select “Configure Options”.
  3. Put a check mark in “013 Boot File Size” and enter the file size in 512 octet blocks. Example, your boot image file is 12.8 KB (kilobytes) or 13204 bytes. Divide the file size in bytes by 512 (13204 / 512). And round the number up. Enter the resulting number (26) in the text dialog that is enabled when you put a check in 013. If your using the pxelinux downloaded off this page then 26 is the correct value to enter.
  4. Put a check mark in “043 Vendor Specific Info” and enter the following binary value: 01 04 00 00 00 00 ff.
  5. Open a command window and type the following:
    c:\>netsh
    netsh>dhcp
    netsh dhcp>server \\server_name
    netsh dhcp server>add optiondef 60 ClassID String 0
    netsh dhcp server>set optionvalue 60 STRING PXEClient
  6. Put a check mark in “066 Boot Server Host Name” and enter the IP address of the server.
  7. Put a check mark in “067 Bootfile Name” and enter the name of the boot image file /tftpboot/pxelinux.0.
  8. Right click on the server name in the DHCP control panel, go to all tasks, and select “restart”.
  9. Go back to scope options and verify that all the information is there. You should see the five entries on the right. They should look like this:013 Boot File Size Standard 0x18
    043 Vendor Specific Info Standard 01 04 00 00 00 00 ff
    060 ClassID Standard PXEClient
    066 Boot Server Host Name Standard Server IP address
    067 Bootfile Name Standard /tftpboot/pxelinux.0

If any of the options do not match these, double-click on the option and change the value. More than likely option 060 will be wrong. Change it so it looks like above.

Now configure the TFTP Server as I outlined in the previous post.

You can now finally set up the acutal boot process:

  1. Extract the contents of the pxelinux arcive into c:\windows\tftpd\tftpboot\
  2. tftpd\tftpboot\
  3. In c:\windows\tftpd\tftpboot\pxelinux.cfg\ tftpd\tftpboot\netboot.img on the server once the password password has been entered. More menu items can easily be added by adding more blocks and changing the label and the image filename.

Once all this has been done its time to test it out, if you have everything set up correctly when you network boot a machine on your lan your should be presented with a small password protected menu that lets you boot your floppy disk images quickly and easily!

TFTP by Microsoft. Free, but Shy

Filed under: Network Admin — Tim @ 10:23 am

If you have only the occasional requirement for a TFTP server or a simple requirement that will require little ongoing administration and you’re running Windows, it’s most likely Microsoft have already provided you with all you need - they’ve just hidden it from you. This how-to guide explains how to get your free TFTP Server up and running.

Take a look at Wikipedia’s article on TFTP for more information.

Remember that TFTP is simple protocol and insecure protocol. If you have sensitive information or configurations to move across your network you should look at a more appropriate mechanism, such as SSH.

Finding the TFTP server daemon

The file you need, “tftpd.exe“, may already be installed on your system in the “%SystemRoot%\system32\dllcache” directory.

If it’s not already there Windows 2000 Professional, Windows XP, Windows 2000 Server and Windows Server 2003 (and perhaps some others) all come with the software. You’ll find a file called “tftpd.ex_” in the “i386” directory on the installation CD, a compressed version of what you need. You can use the command “expand D:\I386\TFTPD.EX_ %SystemRoot%\system32\dllcache” to extract the file to its usual home.

Installing the TFTP service

The following script uses the native XP/2003 “sc.exe” and “reg.exe” commands to install the TFTP Server as a Windows Service.

If you’re running Windows 2000 you’ll need to get the same commands from the Windows 2000 Resource Kit (see Q251192) and the Windows 2000 Support Tools (see Q301423) or use “instsrv.exe” command (see Q137890) and “regedit.exe” tools instead.

mkdir “C:\windows\tftpd\tftpboot”
copy “%SystemRoot%\system32\dllcache\tftpd.exe” “c:\windows\system32\tftpd.exe”
sc create TFTPd binPath= “%SystemRoot%\system32\tftpd.exe” start= auto DisplayName= “TFTP Server”
reg add HKLM\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters /v “Directory” /d “C:\Windows\tftpd”

Configuring the TFTP service

The TFTP Server takes its configuration from the Windows Registry. There are five keys you need to worry about, one of which (”Directory”) was created above and specifies the where the TFTP Server finds its files on disk. The remaining four keys are listed here.

  • The “Masters” key contains a list of client IP addresses that are permitted to write files.
  • The “Clients” key contains a list of client IP address that are permitted to read files.
  • The “Readable” key contains a mask of acceptable filenames that can be read.
  • The “Writable” key contains a mask of acceptable filenames that can be written.

The following script configures a read-only TFTP server that will serve any filename to clients with IPs in the
 192.168.110.* range.

reg add HKLM\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters /v "Masters" /d ""
reg add HKLM\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters /v "Clients" /d "192.168.110.*"
reg add HKLM\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters /v "Readable" /d "*"
reg add HKLM\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters /v "Writable" /d ""

And the Regedit script here does exactly the same thing.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTPd\Parameters]
“Masters”=”"
“Clients”=”192.168.0.*”
“Readable”=”*”
“Writable”=”"

Managing the TFTP service

The TFTP Server can be started and controlled just like any other Windows Service - from the MMC Services GUI, using “sc start TFTPd”, “sc stop TFTPd”, “net start TFTPd”, “net stop TFTPd” and so on.

If the machine hosting the TFTP Server has a local firewall you might need to add the appropriate rule to allow inbound UDP connections to port 69 (see IANA Well Known Ports).

August 12, 2008

Wow…Been Busy? Me too.

Filed under: Network Admin — Tim @ 2:43 pm

It’s been extremely busy in both secular and personal life. Finishing a college course, budget time, moving to Hyper-V and virtualization.

I’ll get back to posting though, I miss the therapeutic effect!

TLC

June 6, 2008

SonicWALL NSA 4500 & Global VPN Client Connection Problems!

Filed under: Network Admin — Tim @ 3:46 pm

Replaced the “old” SonicWALL with the new one. I decided to do the setup manually to refamiliarize myself with the configuration, and all went well except for remote connectivity!

The Enhanced OS is complicated and powerful, but once you get it in place it just works. Now I’m back in that place, but not after a call to support.

My client would connect and even allow drive mappings and Outlook connectivity but very sporadically. I could ping and get a single reply, then nothing.

Outlook would connect and then drop.

First I logged an online support session. Then I called support. Turns out that the guy that called me on the online session was more competent than the direct phone support rep! Phone Guy had me pinging servers on my LAN from the Global VPN Client (remote) and he was watching the packets fly by on the SonicWALL. He concluded that there must be a switch on the network messing things up. “Au Contrare!” I said. “It worked fine with the old SonicWALL.” He maintained his stand, and I let him off the hook, knowing I would get another call.

Online Guy called me, and he had it figured out in 20 minutes. We did a number of things to clean it up, which I summarize below!

Under Network Objects: 

Created a network group object that included our two LAN interfaces: (X0 Subnets & X3 Subnets,) Called it VPN Networks. When exporting the VPN config file, choose this network object as the connect to item.

Under VPN:

In the VPN Configuration
On the Client TAB:
Client Connections section; Virtual adapter settings are DHCP Lease, Allow Connections to: SPlit Tunnels.
The setting that I changed was the “Set Default Route as this Gateway,” by clearing the check box. Since we are not allowing Internet access through the LAN this is not configured.
On the Advanced TAB:
Cleared the check box: Require Authentication of VPN Clients via XAUTH

 > DHCP over VPN, click configure, and unchecked the box “Use Internal DHCP Server (this means the one in    the SonicWALL), Since we are passing the request to our internal (LAN network) DHCP server.

 > Advanced, Cleared the checkbox “Ignore DF(Don’t Fragment) Bit”

Re-export the config file, being sure to choose the new object. Don’t forget to save your config!

TLC

Newer Posts »