Remotely Connecting To Servers

  • Thread starter Thread starter Cardin Smith
  • Start date Start date
C

Cardin Smith

Okay here is the situation.

At the moment, company A has joined with Company B.
Company A decides that Company B should move from a peer to peer network to
a Server / Client network. (This part is easy).
Company A then decides that it wants Company B to be a part of it's network.
(Okay, fair enough, i can set up a VPN on the server over there and then let
it connect to our server, hence all of it's clients will see our shares and
access network files).

But wait, here comes my problem. Company A has an accounting package which
resides on their server (we will call it Server1). Company B won't have VPN
bandwidth until next year so we will have to install the accounting package
there also. Now the head accountant who works at Company A, will sometimes
go down to Company B, and wants to be able to Log In and work just as if he
was in Company A. (No problem i think to myself i will just make the server
at Company B mimic all the settings of the one at Company A (okay so
technically wouldn't this mean that i would have two servers both called
Server1 in order for this to work??? Yea you are right, you would... So what
happens when the time comes to link the both of them up to each other?? Oh
crap, how will that work. Won't i have to change the Server name, and also
Demote it because i would have had to originally set it up as a Standalone
sever??? Yep i am pretty sure you must)


See my dilema (other than the fact that i talk to myself). Does anyone have
a good idea on the best way on going about doing what i have to do.

Note the following things
1. There will be a minium of 8 - 9 months of Company B not being capable of
having enough vpn speed.
2. Want any mobile user (users with laptops) to be able to walk into Company
B and be able to work flawlessly. (This is only really a problem for the
accountants because the accounting software is a mapped drive).
3. In the long run the server at Company B will hook into the server at
Company A, in which place Company A server remains and the Big Daddy.
4. Should i change up the installation on Company A server now, because at
the moment it is set up as a stand alone server.
 
Cardin Smith said:
But wait, here comes my problem. Company A has an accounting package which
resides on their server (we will call it Server1). Company B won't have VPN
bandwidth until next year so we will have to install the accounting package
there also.
Click to expand...

Then get the bandwidth sooner. Things must be done at the proper time, ..if
you don't have the bandwidth then it is the wrong time to give the system
"more to do".
Now the head accountant who works at Company A, will sometimes
go down to Company B, and wants to be able to Log In and work just as if he
was in Company A. (No problem i think to myself i will just make the server
at Company B mimic all the settings of the one at Company A (okay so
technically wouldn't this mean that i would have two servers both called
Server1 in order for this to work??? Yea you are right, you would...
Click to expand...

No you would not.
So what
happens when the time comes to link the both of them up to each other?? Oh
crap, how will that work. Won't i have to change the Server name, and also
Demote it because i would have had to originally set it up as a Standalone
sever??? Yep i am pretty sure you must)
Click to expand...
See my dilema (other than the fact that i talk to myself). Does anyone have
a good idea on the best way on going about doing what i have to do.
Note the following things
1. There will be a minium of 8 - 9 months of Company B not being capable of
having enough vpn speed.
2. Want any mobile user (users with laptops) to be able to walk into Company
B and be able to work flawlessly. (This is only really a problem for the
accountants because the accounting software is a mapped drive).
Click to expand...

Your dilema is that you want things to work before they can possibly work.
The bandwidth is required for things to work,...therefore the "plan" must be
changed so that you get the bandwidth now instead of 8-9 months from now.
3. In the long run the server at Company B will hook into the server at
Company A, in which place Company A server remains and the Big Daddy.
4. Should i change up the installation on Company A server now, because at
the moment it is set up as a stand alone server.
Click to expand...

That doesn't even make any sense.
 
Okay, so lets say this scenerio. Company B has full bandwidth needed. What
would be the best steps to take to have them hook up to each other?

My thoughts are to set up the server at Company B to create a VPN into
Company A, hence every computer on Company B network should now see
everything on Company A??

Thanks for any help.
 
Cardin Smith said:
Okay, so lets say this scenerio. Company B has full bandwidth needed. What
would be the best steps to take to have them hook up to each other?

My thoughts are to set up the server at Company B to create a VPN into
Company A, hence every computer on Company B network should now see
everything on Company A??
Click to expand...

Sorry if I sounded too negative. Yes, correct, VPN is the way to go. You
probably want to create a "Router-to-Router" (Site-to-Site) VPN. This is
not the same as a Remote Access VPN. Many people aren't aware there is more
than one "model" of VPN. *But*...until you get the bandwidth to make it
work you are waisting your time.

As far as "seeing everything" on the opposite network,...that depends on how
you define "seeing". VPN does not provide "naming" and does not provide
"network browsing" (Network Neighborhood). VPN follows the same patterns,
limitations, and restrictions involved when working across two subnets with
a router between (except much slower).
 
Thanks alot for this information, it has helped me to take a clearer look at
the different aspects of the task in hand. Thanks so much for the getting
back to me about my second question.

Kind regards;

Cardin Smith
 
Back
Top