I'm curious why you are not using an "Execute Task" task to run the batch file?

If the executable is waiting for an interactive response, it will appear to hang. We had this issue with executables located on 'untrusted' shares, but I haven't seen it happen with a local cmd.exe call.

Can you log onto the server and run the SSIS package interactively?