SubSonic - FlashPlayer Broken ? ?

Well... forget about banging your head on the wall trying to fix those poor little client machines.  It's not you... It's me...  We've all heard that one before.

But this time, it's true.  Especially when you've hammered down your web-server on a number of occasions, just to see if you could break it...

ok, you ready for the fix?

sudo rm -Rf /var/subsonic/jetty/2169/jsp/org/apache/jsp/WEB_002dINF/jsp

Keep in mind, I'm running mine on a QEMU Virtual Machine that is Ubuntu 11.04 x64 with the most basic of basic installations. No frills people.

I think the cache files got stuck or corrupted at some point during one of my "stress tests"... fun :)

WordPress on Windows 2008 R2 IIS7.5 - FTP update?

Screw that.

I added the folder permissions of Modify, Read & Execute, List Folders, Read and Write on the c:\inetpub\SiteName folder to ServerName\IUSR

tada... :)

Stop whining list

1. FreeNas...


2. Windows 2008 R2 2 node Cluster build


3. IIS 7.5
   
   
   
   1. php.iis.net
   
   
   2. WordPress 3.0 Post Setup
   
   
   3. mySQL - with phpmyadmin
   
   
   
   


4. SQL 2008 R2 Enterprise cluster build
   
   
   
   1. Majority node set with cluster, witness server
   
   
   2. Shared disk with quorum from iSCSI Target from FreeNAS
   
   
   
   


5. Self-Signed certs (SSL)


6. ISA - 443 to 80


7. RDP default port add/change - entry on http://d.patrickoneill.com/?p=83


8. MOSS 2007 to MOSS 2010 upgrade/migrate


9. get patches for Mom's computer :)

How to host multiple web-sites on XAMP

Edit C:\xampp\apache\conf\httpd.conf
- yes... there are more lines in that file, but these are the ones you need to edit... :)

ServerName *:80

#DocumentRoot "C:/xampp/htdocs"

#<Directory />
# Options FollowSymLinks
# AllowOverride None
# Order deny,allow
# Deny from all
#</Directory>

#<Directory "C:/xampp/htdocs">
# Options Indexes FollowSymLinks Includes ExecCGI
# AllowOverride All
# Order allow,deny
# Allow from all
#</Directory> 

Edit C:\xampp\apache\conf\extra\httpd-vhosts.conf
- ok - just kinda follow the logic for each website... and place your web files in the right directory... or else...!

<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot "C:/xampp/htdocs/FolderForWhateverSite"
ServerName www.whatever.com
##ServerAlias www.whatever.com
ErrorLog "logs/error.log"
CustomLog "logs/error.log" combined
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
<Directory "C:/xampp/htdocs/FolderForWhateverSite">
Options Indexes FollowSymLinks Includes ExecCGI
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

Then go to command prompt:

net stop apache2.2 & net start apache2.2

Ever wanna clear your SSL Cert Cache?

certutil -urlcache * delete

Exchange 2007 - sending out 25 blocked somehow?

Since, I'm using an ISP that blocks incoming ports like 80 and 25, etc., I have to work things a little differently. A friend of mine has a small datacenter and he's allowed me to use his SMTP server as a relay as well as his ISA server for proxying. So, for OWA, my ISA rule is pretty much a default Exchange OWA rule out-of-the-box with the only exception being that it's bridged on the back of the rule to port 81 on my router. Then my router forwards all port 81 traffic to my Exchange server.

Now, for some reason, my ISP also blocks port 25 in and out. Ugh,... I know... a total P.I.T.A.!!!

So, what do I do?

I run all my email through my buddy's SMTP server and Exchange via not just port 25 but also port 26. So, his router forwards all traffic from port 25 to 26 to his SMTP server (just a basic SMTP server and not an Exchange server).

So, as long as your recieving smtp server (in my case, my friend's SMTP server out there on the internet) is configured to recieve from you and it's an smtp server you control outside your network, you can fix this issue.

First - make sure your external smtp server can recieve on both port 25 and 26. And that it will allow relay of your public IP along with the domain name your using.

Then in your exchange server, set your send connector's smart-host to the public ip of that smtp server out there.

There isn't an option in the Exchange MMC to use another port other than 25. So, we will need to use the exchange shell command below:

set-sendconnector -identity "yourwackyconnectorname" -port 26

This will allow your exchange box to send your emails out on port 26 instead of port 25