Remote server for MS Business Contact Manager 2010

[GRoston]

I would like to serve the database for BCM 2010 from an internet accessible server. This server also happens to be on my LAN.

First, I installed and configured the database on the server.

Using the server's LAN name and LAN IP:
I was able to successfully connect to the database when I used sqlcmd from my client machine. I was also able to successfully connect to the database when I used the BCM connection wizard from my client machine.

Using the server's internet name and internet IP:
I was able to successfully connect to the database when I used sqlcmd from my client machine. I was unable to connect to the database when I used the BCM connection wizard from my client machine. The error message is this, "The computer, <name>, is not available or does not contain any shared Business Contact Manager databases..." Using a packet sniffer on the server, I observed that no requests showed up on port 5356 when the connection request came from BCM.

These tests strongly suggest that

• The firewall is properly configured
• The database is properly configured
• The BCM database is properly shared

So, my question is this: Is there some way to twist BCM's 'arm' such that it will connect to a database server not located on the same LAN as the client?

Thank you!

 

[Johnathan Lyman]

I would like to serve the database for BCM 2010 from an internet accessible server. This server also happens to be on my LAN.

First, I installed and configured the database on the server.

Using the server's LAN name and LAN IP:
I was able to successfully connect to the database when I used sqlcmd from my client machine. I was also able to successfully connect to the database when I used the BCM connection wizard from my client machine.

Using the server's internet name and internet IP:
I was able to successfully connect to the database when I used sqlcmd from my client machine. I was unable to connect to the database when I used the BCM connection wizard from my client machine. The error message is this, "The computer, <name>, is not available or does not contain any shared Business Contact Manager databases..." Using a packet sniffer on the server, I observed that no requests showed up on port 5356 when the connection request came from BCM.

These tests strongly suggest that

• The firewall is properly configured
• The database is properly configured
• The BCM database is properly shared

So, my question is this: Is there some way to twist BCM's 'arm' such that it will connect to a database server not located on the same LAN as the client?

Thank you!

You may also be having routing issues. The gateway/router may not be sending traffic from that port to the BCM server. Check your routing table and or port forwarding table.

What do you have the BCM server running on, out of curiosity?

 

[GRoston]

Johnathan,

Thanks for the reply. Since sqlcmd IS working when 'routed' via the internet, I do not think that the gateway/router is the issue, especially since I did configure it to route traffic to the BCM port to the server.

In my case, the 'server' is a fairly lame Windows XP box.

 

[Johnathan Lyman]

Johnathan,

Thanks for the reply. Since sqlcmd IS working when 'routed' via the internet, I do not think that the gateway/router is the issue, especially since I did configure it to route traffic to the BCM port to the server.

In my case, the 'server' is a fairly lame Windows XP box.

I'm shooting in the dark at this point as I am unfamiliar with BCM. It is possible that the sqlcmd is pinging the server on a different or more well known port thus the firewall on said machine is allowing the sqlcmd traffic and not letting port 5356 through. Try disabling the Windows Firewall and or any other software firewalls you have on your machine. You could also have your port sniffed (lol at nerd joke) and see if it's really open: WhatsMyIP.org : Port Scanners/Sniffers.

Since traffic routing is not an issue, it should go straight to your bcm box.

 

[GRoston]

Johnathan - I am convinced that BCM is the problem - I am attempting to work around that by enabling VPN to my server.