Monday, December 22, 2008

FTP7 is a bitch

Here at work we're using GoGrid and their Win2k8 server images don't come equiped with FTP7. I found this out after running into some trouble with FTP6. I looked at some IIS7 sites and some mentioned FTP7 so I thought I'd use that instead.

I started off not knowing much about FTP servers in general but I assumed it'd be easy. To be honest, I think I was a port forward away from getting FTP6 to work before I bailed on it. But that's old news.

A few things to keep in mind: FTP servers come in two flavors, Active and Passive. From what I can tell, Active is a straight forward approach with two TCP ports being forwarded, Port 21 for the initial connection and Port 20 for data communications. Passive's data communications uses a range of ports. If you look up the IPv4 and IPv6 ports with netsh, it should make clear which you're using. You use another netsh command to forward the dynamic port range.

commands:
netsh int ipv4 show dynamicport tcp
netsh int ipv6 show dynamicport tcp

forward port range command:
netsh advfirewall set global StatefulFtp enable

You also have to assign permissions. This part is straight forward and well documented. The tricky part that goes along with permissions is the folder structure. You have to create a 'localuser' directory in 'ftproot' and the user's name in 'localuser'. If you don't do that, you'll get some kind of 'home not resolved' when you try and log in with a client side ftp application.

After understanding all these concepts, it made sense that the system would work and it did.

*Type of FTP
*Choose authentication type
*Create directory structure if necessary
*Forward necessary ports

And that's really it. If a reader out there thinks I should take a deeper look at FTP servers, than please leave a comment. I've got a lot to learn and some experience to gain.

Monday, December 15, 2008

Economic Woes

I'm a subscriber to NPR's Economy podcast. I just finished listening to it and its tone was slightly more depressing than usual. It's segment on the new job environment, full of professionals battling for the same jobs was what bothered me. Although this is nothing new, the twist was the type of job that's on the table: seasonal positions. I don't usually imagine my collegial peers on the sales floor when stopping in Best Buy. But if it was the case that they'd be working there, I'd assume they'd be working for some extra money, trying to make a little ends meat, but according to NPR, that term doesn't apply. They're working there to make a living, competing with other seasonal workers.

Ever since my mother was laid off, I haven't felt secure about my future. Recent talks had always involved plans of me moving out and going to live with my girlfriend someplace in the city. I currently live out in the West Suburbs. But the more I thinking about it, the worse of an idea becomes. This was the plan, leave home and pay someone else money that could be going towards my family's well being. Although the perk is I'd be living somewhere of choosing as opposed to necessity, the sentiment is this is not the right time. I move like that, at this point in time would be selfish.

But, is now the right time? I suppose this is the age old question people in my position have asked themselves. I'd be willing to bet most people aren't at the age of 25 so maybe it is time that's driving my motivation.

Tuesday, December 2, 2008

SF2 HD REMIX - PS3 FIX

Initially, Street Fight 2 HD Remix seemed flawed with the number of disconnects I was coming across. So, considering I love SF2 I set out to find a solution.

I'm an avid gamer, I know about the NAT issues plaguing Halo 3 so I thought this might be caused by something similar. The solution for that is well documented and as soon as I get home, I'll add a few links that will walk you through this, but for now, know that a solution exists.

It turns out that the PS3 also has a NAT Type that needs to configured. After setting up your wireless connection on the PS3, you're shown a screen with your network name and the encryption type your using. But it also includes your NAT Type number. In my case, I had NAT Type 2, which requires you to forward port 443. After I forwarded that port, I only had a single disconnect in about 20 matches.

Google "PS3 nat type 443" w/o quotes and you'll probably find the walkthrough. My problem could also be that I'm using DD-WRT firmware on my Linksys router which shows TX errors, but that's for another post.