1. Home
  2. Point-Of-Sale Software
  3. 3rd party server for connection okay?

3rd party server for connection okay?

We had a network guy come in and try to configure our network - 3 stores and HQ in seperate locations. Because of our router and dsl configuration, vpn would not work. He set up an outside ip address (dnsdyn.org) in order to have the stores and HQ talk. Still not working! ARGH!!!!!!! In the store it shows a connection but then states invalid store id. The store id is correct. In the HQ client the address is the ip address of the outside source and the port? Anyone know why this isn't working and have any suggestions???? Thank you!

Reply to
ZCSF
Loading thread data ...

Are you sure the Store ID is correct? Does the message mention a connection password in addtion to Store ID? You can have different passwords on each store. If you get to the point where it is checking the Store ID, it sounds like you are connected. Connections generally fail with Socket Not Found or Connection forcibly rejected by Socket messages.

Glenn Adams Tiber Creek C> We had a network guy come in and try to configure our network - 3 stores and

Reply to
Glenn Adams [MVP - Retail Mgmt

Reply to
Doug Pic-N-Pac

Reply to
ZCSF

That's a very specific error. Your connection settings are correct, you are just using the wrong connection password for that store.

In HQ Manager, Admin, Stores, open the properties for that store, go to the connection (or maybe schedule) tab and change the connection password.

At the store, in HQ Client, File, Configuration, HQ Server tab, change the Connection password to the new value entered at HQ - make sure you are logged into Windows as an Administrator or your changes will not be saved.

Try connecting again...

Glenn Adams Tiber Creek C> 100% sure it's correct. After the network guy left he suggested that we

Reply to
Glenn Adams [MVP - Retail Mgmt
Reply to
CptSoft

Take the password out on the store side, That's your problem.

Reply to
Ron Reyes

Reply to
ZCSF

I am having this same problem. We just upgraded 5 locations to 2.0.0110 from

1.3xx. One of the store locations is located on the same network that the hq server is. Actually the two are are running on the same server. I had no problems at the 4 remote locations connecting up the hq client, but the 'local' one is giving me the same error as described in this post. There is no password assigned to connect, but I went ahead and put one in at the hq side and client side just to see if that would matter but it did not. I've checked the store table in HQ to make sure the store is still there. It is. I'm stuck. Any ideas? Thanks very much.

MRW

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Reply to
mattw

I am having this same problem. We just upgraded 5 locations to 2.0.0110 from 1.3xx. One of the store locations is located on the same network that the hq server is. Actually the two are are running on the same server. I had no problems at the 4 remote locations connecting up the hq client, but the 'local' one is giving me the same error as described in this post. There is no password assigned to connect, but I went ahead and put one in at the hq side and client side just to see if that would matter but it did not. I've checked the store table in HQ to make sure the store is still there. It is. I'm stuck. Any ideas? Thanks very much.

MRW

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Reply to
cptsoft

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.