Okay thats what I was thinking. I use cpanel myself and it looked like I had to add the ip from the remote site.
"Change the security settings on server B to allow incoming mysql traffic from server A's IP."
Of course I don't really have way to test that now. But very helpful anyway.
At least for the next move.(Shudder)

You can disable the security feature to 'not show' the sql error by setting "show_errors" to 1 in libs/mysql.inc.php

Well Giz every time I have mentioned that setting. Everyone beats me up.(Including you) LOL.
So I don't suggest it anymore.

I'll post back with the results (maybe this weekend?) when I get this moved.

Thanks for the help.My wife wonders why I won't move anywhere that doesn't have fibre (or at least 10Mbps U/D) to the home internet. I just use it and my home server for various and sundry things like this WAY too often.

I'll have to try the security setting one of these days once I'm done with this. I'm assuming that means that I could have seen the error that UBB was generating instead of the generic one - right?

Well what it does is display the real error message in the browser instead of showing the generic message you got. In lieu of turning on the error log. But then everyone including guests can see the error. Including paths,querys, ETC
So that's why everyone says don't do it. But it does work for debugging problems. Just need to remember to turn it off when done.

Yup - exactly what I needed. Good to know for future reference.

I doubt anyone would have jumped on you for mentioning it to me. We are talking about a test system connecting (or not connecting in this case) to another system that hadn't been placed in production yet.

But what do I know? I'm new here.

All I know is it works especially when a admin has not turned on error logs prior and gets the same message you got. At least they can ftp to the file and change the setting to see the real error.

Well, I reccommend against using it, and recommend ONLY using the MySQL logging option, but if you don't have a forum setup to use a mysql server you can't really error test...

But I highly recommend that you disable the option once you're done playing with it; you don't need your users seeing error messages that could potentially contain sensitive information about your server(s)

And I agree 100% Giz.
In fact when I use this feature I am usually in a rush to turn it off as quickly as I can.
But it is a very useful tool when needed.
I hope we keep this in version 8.

Well, in summary, I completed the move on Friday night. Everything went as planned.

Frankly, I was surprised at the speed of the DNS updates. Within a few minutes, my home bind instance was cranking out the updated info. I still went through the motions and updated the "old" machine to access the new database (and included a warning on the board that any attachments weren't going to carry over if you uploaded to the "old" machine after the cutover to the new machine - I wasn't in the mood to setup rsync just for that.)

The only issue I had (have actually) is that mail alerts suddenly aren't working - and they were prior to the refresh of the db and the uploads directory. I'll have to start a new thread on that one...

Anyway, thanks for the help. Mission accomplished.