SSIS Deployment Question About Conn Strings? Please Help.

Hi everyone:

I have a package(SSIS) that works fine on a local SQL Server. Once I deploy it to the server A, and change the connection strings, it throws the following error:

Error: The AcquireConnection method call to the connection manager "DatabaseName" failed with error code xxxxx.
Error: component "OLE DB Destination"(16) failed validation and returned error code xxxx.

Error: An OLE DB error has occurred. Error Code: 0x80040E4D. Al OLE DB record is available. Source: "Microsoft SQL Native Client" Description: "Communication Link Failure"

Error: Error: An OLE DB error has occurred. Error Code: 0x80040E4D. Al OLE DB record is available. Source: "Microsoft SQL Native Client" Description: "TCP Provider: An existing connection was forcibly closed by the remote host."

Error: Error: An OLE DB error has occurred. Error Code: 0x80040E4D. Al OLE DB record is available. Source: "Microsoft SQL Native Client" Description: "Login failed for user 'username'."

I have confirmed from my Network Engineer that this is not a Network issue. I can connect to the the target sql server from SQL Server A(where the package is running). The only thing that has changed is the connection string. In my package I connect to a local database on the server, and a remote SQL server. The connection to the local sql server works fine from the package. The remote SQL Server connection string is not working, I think. I also noticed that after I enter my password in the conn string, within the VS 2005, after building it, and deploying it on the server, I check back the conn string, and it is no longer there. I have read some posts about it, and I understand that SSIS hides it. What is the work around here? I have never used config files for SSIS, so I would need exact instructions to do that, if that is the way to go. Has someone else ever ran into this error? I have seen some posts on the forum with similar error, but they are not providing any solid answers. In my case, I need to know how to implement either a config file for conn strings, or how to deploy with conn strings which retains password. I can connect to a remote SQL Server from SERVER A utilizing SQL Management Studio, therefore any firewall/port issues are not relevant. I feel the issue is with conn strings, and I need some solid advise on how to implement them especially, where in my case, one of my connections is to a remote sql box, utilizing Sql server authenticaion(which involves use of password). Thanks.

Here is how my current connection string looks like and notice there is no attribute for password:

Data Source=192.1.1.1xxx;User ID=username;Initial Catalog=databasename;Provider=SQLNCLI.1;Persist Security Info=True;