We have a remote site and the main site. Main site has two networked
computers with WinXP and Office'07 w/Business Contacts Manager - one computer
is hosting the main BCM database. We use Hamachi to create a VPN with the
remote site which has one computer on the 'Net' running Vista and Office'07
w/BCM. Got everything up and running and all was working very well.

Then Comcast cut-off our internet connection at the main site. We
re-connected with AT&T DSL about a week later. Since then, I cannot get the
remote site to re-connect to the main database - I continually get the error
stated in the subject line.

I know that I have VPN connectivity as I can browse the main computer via
the VPN and have been able to do other activities (non-MS) with the VPN - and
those activities aren't the problem, because those came after the
reconnection AND the attempt (several) to re-connect the BCM.

TIA for any assistance.

On Nov 3, 4:41 pm, SFSwimmer <SFSwim...@discussions.microsoft.com>
wrote:
> We have a remote site and the main site. Main site has two networked
> computers with WinXP and Office'07 w/Business Contacts Manager - one computer
> is hosting the main BCM database. We use Hamachi to create a VPN with the
> remote site which has one computer on the 'Net' running Vista and Office'07
> w/BCM. Got everything up and running and all was working very well.
>
> Then Comcast cut-off our internet connection at the main site. We
> re-connected with AT&T DSL about a week later. Since then, I cannot get the
> remote site to re-connect to the main database - I continually get the error
> stated in the subject line.
>
> I know that I have VPN connectivity as I can browse the main computer via
> the VPN and have been able to do other activities (non-MS) with the VPN - and
> those activities aren't the problem, because those came after the
> reconnection AND the attempt (several) to re-connect the BCM.
>
> TIA for any assistance.

Try running this command from a command prompt from your client:
sqlcmd -E -S "nameofyourdbserver\mssmlbiz,5356" -Q "select * from
orgtable"

It'll tell you if the machine can connect to the database. If not,
then the error message may indicate what's wrong.

Since it worked with one VPN and not another, I'd guess that the VPN's
are configured differently so that earlier one placed the client on
the same sub-net and the new VPN connects with the clint on another
sub-net. In which case I'd check that the Windows Firewall on the
database machine has opened the Small Business port (5356) to the
internet.