You must have Forge installed on your client if you want to join a server with Forge.
Make sure you start with a clean jar when you install Forge. It looks like you may have installed Optifine previously.
This is a JVM bug:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000001cf67dc2, pid=4928, tid=6968
#
# JRE version: 7.0_09-b05
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [atio6axx.dll+0x187dc2] atiPS+0x1307c2
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Weltall\Desktop\Minecraft\Manager\instances\1.4.5\minecraft\hs_err_pid4928.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
I don't think there's anything the Forge team can do about this.
This should go in the Modder Support forum, but I will help anyway.
Poke around with ILibrarySet and RelaunchLibraryManager. Your mod will need to be a so-called "coremod" for this to work (i.e. it implements IFMLLoadingPlugin).
So... the problem here is that you can't connect to a dedicated server hosted on the same machine as your client?
Also, please post both the client and serve logs.
You should be able to safely ignore these stacktraces. It probably means that Metallurgy was checking if another mod was installed or not (probably for a compatibility module or something) and didn't find it. The stacktrace shouldn't even really be logged in the first place.
2012-11-18 23:08:46 [sEVERE] [ForgeModLoader] This version of FML is built for Minecraft 1.4.5, we have detected Minecraft 1.4.4 in your minecraft jar file
Get Forge 6.3.0.378.