@Evo: From what I've gather after reading his comments 2 times... The mac is the client machine he want's connected to his network machine.. :P He just seems to be a bit confused of what actually happens when he runs those commands
@jddancks: What actually happens is that the SOCKS proxy is your personal mac machine (don't worry, the connection still gets routed via ssh on your workplace machine -- that's what the -D option does) and that's why you need to enter --proxy-server=socks://localhost:8888"
(like Evo2 already told you to)...
It only seems weird because you're confusing the actual ssh connection with the socks proxy connection... You should think of them as two different things..
Basically, when running:
ssh -D 8888 email@example.com:22
you are instructing your local
(so, only localhost) machine to listen to incoming SOCKS4 or SOCKS5 connections on port 8888 that gets forwarded to firstname.lastname@example.org:22
You will get connected and you need to keep this connection active (exiting will close the connection)
You then need to instruct your browser to connect to this localhost
There is no need to run any kind of special command on the server side..