General information
Category:
COM/DCOM and OLE Automation
We have an MTS server here in our office on our LAN. It has several VFP COM components installed under MTS. The client PCs in this office have no problem connecting to these objects from our VFP client. The box the MTS server is on can be seen through Network Neighborhood under Windows. So our LAN setup seems to be good.
The problem is with our WAN connection. Our users in our Chicago office cannot see the MTS box under network neighborhood. How do we set this up? Is it an NT security issue? Is it an MTS issue? Must all client PCs be able to reference the MTS box by computer name or can it be IP address?
Overall, what is the "standard" implementation of a 3-tier system? Is there an MTS box for each office and one SQL server that's accessed over the WAN? Or is there one MTS box on the same LAN as the SQL server and each client box connects to the same MTS server over the WAN?
Client Client Client
|
LAN
|
MTS
|
WAN
|
SQL Server
OR
Client Client Client
|
WAN
|
MTS
|
LAN
|
SQL Server
Are both options? Is there any good documents discussing this anywhere on the web?
Thanks in advance!
paul
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only