Share
Report
35 I've inherited an RMS system with little documentation that was installed before I started managing this network. We ran into the situation yesterday when the network (not RMS) AD/DNS server went down, and communication between the registers (and register/server) failed. I'm hoping someone can enlighten me as to how the registers physically interact when processing transactions and credit card authorizations. Thus I can try harden the physical configuration so that the registers can continue to function in the future if the AD/DNS server crashes or needs to be taken offline for service.
What I know...
That the registers (running XP) clearly needed DNS to resolve to each other. They are programmed with static IP addresses and I can certainly add direct entries to each register's host file for name resolution.
That each register that processes credit cards needs to have Registers listed, pin pad option activated, etc.
That ports 5003 and 443 outbound need to be open on the firewall.
What I don't know...
How does the credit card authorization (customer transaction) get processed? Is the credit card authorization sent directly from each register out to the bank? Or is the authorization request sent to the register / RMS Server that, in turn, would coordinate the authorization request and act as the proxy for the individual registers?
Besides adjusting the local host file, are there any other settings within configuring RMS at each register that should be adjusted so that the registers / desktops running RMS can communicate directly with each other?
Thanks!
Peter
*This post is locked for comments
All responses (
Answers (
