Micros 3700 - Tapi error

[Serenitee]

Hello everyone,
We recently 'moved' the server for one of our locations (currently shutdown for winter) to a new box (It is actually a fresh install upgraded to 5.4 MR2 using that locations license info, etc.) however after installing the same cc driver with the same configuration as the 'old' box when we try to authorize a credit card we get the (after long wait in which it indicates 'dialing backup number' after a while) an 'Internal Tapi Error -5' message. I know from past experience that this message usually means the cc driver is looking for a modem that either doesn't exist or is configured wrong, however we connect over internet (tcp/ip). So far I have:

1) Re-installed the cc driver (CaFDMS(5.2.0000.2925))
2) Verified driver setup copied appropriate files to appropriate locations.
3) Verified the parameters were the same in | configurator | devices | CA/EDC drivers as they were on 'old' box.
3) Verified registry entries were same as on 'old' box.
4) Swapped in the NIC from the 'old' box (in case there was some oddball MAC address, etc. issue).
5) Shut off all firewalls (tested, then re-enabled firewalls after still getting Tapi error).

Note: There are no modems in either 'old' nor 'new' servers .
I suspect I am missing something obvious, any assistance is appreciated.
Thanks in advanced!

 

[Serenitee]

Not sure but it seems as though it may have something to do with another issue that is showing up in the 3700d log as an IFS process error "No TCP/IP server name specified". Still scratching my head though.

 

[POSINSAM]

Set all device numbers to (1) set Micros NIC priority to (1)

 

[Moregelen]

CaFDMS is one of the drivers (I believe) where you will need to have the processor 'unlock' things before reinstalling. A lot of them will create a key on their first connect (which then gets stored in the windows registry somewhere) which then has to be provided on every subsequent request or the connection gets refused. I think CaFDMS does that, though I could be wrong. If you have the old server I'd look around and see if you can find a registry key like that. Sorry I can't give a more definite answer, but I honestly can't remember exactly which drivers do this.