Monday, July 28, 2008

Dell 5310n: error message is 900.00 service RIP software

A few of my users were having trouble with a Dell 5310n printer. The error message on the display was error message is 900.00 service RIP software. When printing large data files, such as a PowerPoint presentation, the printer would error out.

Per Dell's recommendation I configured the virtual printer to not spool the print jobs and send them directly to the printer. This seems to have corrected the issue so far.

Since I have HP printers on the same print server and none of them have had any kind of issue printing the same large files, I starting to think that the problem is due to either bad printer hardware or print drivers from Dell.

Monday, July 21, 2008

Exchange 2007 Mailbox Size Script

Below is a screen shot of my Exchange 2007 mailbox size script. This allows me to quickly view my users mailbox sizes in a nice color coded report.


PowerShell Script to Grant Full Mailbox Access

While testing out a new personal information scanner I discovered a need to grant one AD account full mailbox access to all mailboxes on my Exchange server. Below is the command I used to get the job done.

get-mailbox | select alias | foreach {

Add-MailboxPermission –Identity $_.alias –User myAdminAccount -Accessright Fullaccess -InheritanceType all

}

Wednesday, July 2, 2008

ColdFusion 8 on Windows 2003 64bit

Ran into problems when installing ColdFusion 8 on a Windows 2003 64bit server. Basically, the installer said everything was installed correctly but I was missing half of the ColdFusion files. The installer was ran straight from two different disks with the same result.

After the installation no IIS sites would work correctly. Reinstalling the OS with 32bit to see if that changes anything.

Tuesday, July 1, 2008

Ghetto OpenBSD Firewall\Switch

In an attempt to clear even more stuff off my desk, I created a ghetto OpenBSD firewall\switch. Basically, I added four network cards to an old Dell Precision 350. Loaded OpenBSD on it. Went the standard route when creating a firewall. The five network cards on the system are em0 (External), dc0 (Internal), dc1, sk0, sk1.

echo 'inet 169.xxx.xxx.xxx 255.255.255.252 NONE' > /etc/hostname.em0
echo 'inet 192.168.4.254 255.255.255.0 NONE' > /etc/hostname.dc0

Then I configured the remaining cards.

echo 'up' > /etc/hostname.dc1
echo 'up' > /etc/hostname.sk0
echo 'up' > /etc/hostname.sk1

Configured a Bridge between the Internal card and the three other cards.

echo 'add dc0 add dc1 add sk0 add sk1 up' > /etc/bridgename.bridge0

Using the same NAT rule set I had before (listed below) and with a few crossover cables (had my student assistant work on that portion) I now have a ghetto OpenBSD firewall\switch. Finally, I have a use for all those extra network cards and old systems laying around the office.

PF.CONF

ext_if="em0"
int_if="dc0"
ext_addr="169.xxx.xxx.xxx"

testDomain = "{192.168.4.0/24}"

set skip on lo0
set loginterface $ext_if

nat on $ext_if from $testDomain to any -> $ext_addr

pass in on $int_if all
pass out on $int_if all

block in log on $ext_if all label "Default block in"
block out log on $ext_if all label "Default block out"

pass out on $ext_if proto tcp from $ext_addr to any port { http https } \
flags S/SA modulate state

pass out on $ext_if proto udp from $ext_addr to any port { domain }