Network segmentation - Micros network rules

[jd11111]

We are working on segmenting our POS network from the other back office systems. We would like to still allow applications like Payroll Preprocessing, Human Resources, POS Configurator, etc. to function on the other manager computers. Our pos network would be on 10.2.1.1 and our other back office systems would be on 10.1.1.1.

Has anyone done this or know what these applications need in order to function on a different network?

We have the following ports/protocols set up but the applications still can't find the database server on the Micros server.
2638 TCP
7300 TCP
7301 UDP

 

[DrZogg]

hi,

Have done this myself, on separate VLans. The trick is to run CAL on the client on the different subnet, and to enter the IP ADDRESS of the server, as CAL cannot communicate through at this point. CAL will then perform a system shutdown and restart, and commence downloading the files. Later, copy the MDSHOSTS.xml into the C:\Program Files\MICROS\Common\Etc directory. Running a BOH application, it will look here first for the server directions, and will boost performance amazingly. Because you have put it there manually it will not be updated, so you may want to make a login script \ robocopy call to copy the latest hosts from the Micros server, but I digress.

Alternatively you can add a redundant NIC for the office LAN.

See how you go

DrZogg

 

[jd11111]

Actually already followed those steps exactly and it seemed to work fine, but when I try to run an application I get the error that the database server cannot be found or isn't started.

 

[DrZogg]

hi,
*when running the applications, this is where the MDSHOSTS.xml needs to be in the \common\etc directory, can you confirm that it is there?
*Are you using an unmanaged switch or can you guarantee the ports are open?
*Go to ODBC and enter settings there (there is already a MICROS ODBC setting there, can that connect? )

Can you ping the server & telnet to it?

 

[jd11111]

- yes, mdshosts is there
- managed switch, ports are open
- what settings in the micros odbc connection would I need to add?

yes, can ping micros server from computer.

 

[jd11111]

there were 2 issues on this and we got some help from our local Micros expert!

The encryption keys did not get added to the registry on the client PC when CAL installed Micros. We had to export this from the Micros PC and add it to the registry on the client.

The other issue was in the ODBC connection. We had to specify dobroadcast=no.

 

[DrZogg]

Great work. My next suggestion was to connect / setup in the local network, take it back to the other lan, modify the IP settings manually and not run CAL.

 

[jd11111]

DrZogg,
We have most things working now, but we still can't get Enterprise Office applications to work.

When we launch Payroll Preprocessing, Human Resources, etc., we get "this product has not been properly licensed". They are licensed and work normally on the server.

Any ideas?