Re: Remotely Connecting To Servers
From: Phillip Windell (_at_.)
Date: 10/11/04
- Next message: Brian Mense: "RED X on drive mappings"
- Previous message: Phillip Windell: "Re: VPN and same subnets . . ."
- In reply to: Cardin Smith: "Remotely Connecting To Servers"
- Next in thread: Cardin Smith: "Re: Remotely Connecting To Servers"
- Reply: Cardin Smith: "Re: Remotely Connecting To Servers"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 11 Oct 2004 13:05:14 -0500
"Cardin Smith" <it-department@springdale-group.com> wrote in message
news:ueuq2Q5rEHA.536@TK2MSFTNGP11.phx.gbl...
> 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.
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...
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)
> 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).
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.
That doesn't even make any sense.
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: Brian Mense: "RED X on drive mappings"
- Previous message: Phillip Windell: "Re: VPN and same subnets . . ."
- In reply to: Cardin Smith: "Remotely Connecting To Servers"
- Next in thread: Cardin Smith: "Re: Remotely Connecting To Servers"
- Reply: Cardin Smith: "Re: Remotely Connecting To Servers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
