LijeBaley
asked on
Remote software access problem
I have a customer that has an office with server 2008 R2 on it. He is opening up an office in another location and wants to use the programs on the individual computers at the main office and access the data on the server with no server at the new location( 9 workstations, all XP). Is it possible and if so, how can it be done ?
R. Andrew Koffron
putting in a terminal server at the main office is probably the best answer. otherwise he's going to need pretty high bandwidth at both locations as well as VPN endpoints if they have any security concerns at all., but especially the upstream on the main office.
Yes you can
There are a few ways to go about this
The best option is to have a VPN between the Two offices and then just access the files you want of the server because it will be as if it’s on the same network. This will work for normal types of files nothing major like CAD or streaming.
But I got a few questions before proceed.
Q1 what do you mean buy you want to access the software on the XP PC’s (this can be done but only one user can use each pc at a time
Q2 how much can you spend on this solution
Q3 do you have broad band at each location
Q4 can your budget stretch to a Terminal Server.
Q5 if not Q4 do you want the user to be able to remote access the current PC and work off it remotely.
There are a few ways to go about this
The best option is to have a VPN between the Two offices and then just access the files you want of the server because it will be as if it’s on the same network. This will work for normal types of files nothing major like CAD or streaming.
But I got a few questions before proceed.
Q1 what do you mean buy you want to access the software on the XP PC’s (this can be done but only one user can use each pc at a time
Q2 how much can you spend on this solution
Q3 do you have broad band at each location
Q4 can your budget stretch to a Terminal Server.
Q5 if not Q4 do you want the user to be able to remote access the current PC and work off it remotely.
ASKER
Q1 They have a program that everyone in the office uses as patients move through . The main office has a set of xp computers that they use all but one day a week. The database that program uses is in 2 mapped drives on the server. One user here for each computer there would be perfect. Everyone here could log onto their personal machine at the other end.
Q2 As much as I need to as long as it works when i am done. of course, in this profession yesterday wasnt soon enough .
Q3 The main office runs DSL at 1.5Mbps . The remote location is running DSL at 3 Mbps.
Q4 A server at this location is going to happen. Just not soon enough. As long as a year away depending on cash flow.
Q5 In a perfect world where the possible always happened everyone would come to the remote site and load the desktop on their personal machine at the main office.
Q2 As much as I need to as long as it works when i am done. of course, in this profession yesterday wasnt soon enough .
Q3 The main office runs DSL at 1.5Mbps . The remote location is running DSL at 3 Mbps.
Q4 A server at this location is going to happen. Just not soon enough. As long as a year away depending on cash flow.
Q5 In a perfect world where the possible always happened everyone would come to the remote site and load the desktop on their personal machine at the main office.
LijeBaley:
One key statement that you said is "Patients". He has to send HIPPA data through a VPN tunnel. Any breach and he is in serious trouble. Most of these Patient, scheduling programs are not that intensive unless they also do billing on them. I would upgrade the DSL to 6Mbps on each as the upload speed tends to be low. Gotta get that up.. Use a pair of Cisco or Linkys small business class routers.
After the tunnel is up it shouldn't be to bad.
My guess is that these offices are dynamic or PPOE as well so take that into consideration when you build the tunnels. You will probably bridge the modems and setup dyndns on both. Make sure you can administer both routers remotely if it is dynamic for when the tunnel breaks.
HTH
Ken
One key statement that you said is "Patients". He has to send HIPPA data through a VPN tunnel. Any breach and he is in serious trouble. Most of these Patient, scheduling programs are not that intensive unless they also do billing on them. I would upgrade the DSL to 6Mbps on each as the upload speed tends to be low. Gotta get that up.. Use a pair of Cisco or Linkys small business class routers.
After the tunnel is up it shouldn't be to bad.
My guess is that these offices are dynamic or PPOE as well so take that into consideration when you build the tunnels. You will probably bridge the modems and setup dyndns on both. Make sure you can administer both routers remotely if it is dynamic for when the tunnel breaks.
HTH
Ken
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it is a dentist office
LijeBaley,
Harel66 and I are on the same page on this. You have to have security. Kaput! I also agree with the Terminal server. You can probably buy a used dell off ebay. The bottom line is that I know how "FRUGAL" these people can be until pushed.
It is up to you to create a solution and to advise them on what they need; even if they don't take that advice. Don't offer any guaranty on the security of the solution but do tell them they must do "due diligence". Then provide the best solution you can. Document your suggestions and your concerns.
Then build them what they want or walk away. You are the one that has to support it even if it is their bad idea. They will forget their role as soon as it is up.
Good luck,
Ken
Harel66 and I are on the same page on this. You have to have security. Kaput! I also agree with the Terminal server. You can probably buy a used dell off ebay. The bottom line is that I know how "FRUGAL" these people can be until pushed.
It is up to you to create a solution and to advise them on what they need; even if they don't take that advice. Don't offer any guaranty on the security of the solution but do tell them they must do "due diligence". Then provide the best solution you can. Document your suggestions and your concerns.
Then build them what they want or walk away. You are the one that has to support it even if it is their bad idea. They will forget their role as soon as it is up.
Good luck,
Ken
>It is up to you to create a solution and to advise them on what they need;
>even if they don't take that advice. Don't offer any guaranty on the security
>of the solution but do tell them they must do "due diligence".
As IT guys, we normally have the whole trying to squeeze blood from a turnip thing on all networks, but a dentists office stall needs to be HIPPA compliant. this is a type of case where If the Doctor/Dentist kept the budget so tight that I couldn't do the right type of setup, I'd make them sign the "against medical advice" form. I'd write up an agreement form that says basically:
I am implementing a solution that I know is not going to work long term, I DO NOT Warranty either the work or intellectual property, I am implementing an IT strategy I feel is going to fail and I think it's a bad plan. I will not even give my famous 30 and 30 warranty (30 feet 30 seconds) because I'm certain it's going to fail and leak information and is a problem just waiting to happen. You the Doctor must acknowledge that YOU are taking full responsibility for this project, and since you have refused my professional advice at every turn are agreeing to not hold me responsible in any way or manner for the results of this plan sign here __________________________
of course I'd make it more legal and proper grammar, but that's the jist. Most doctors/lawyers I've ever dealt with either get reasonable, or fire me on the spot, either way is good, let the next guy that tries to make a remote solution for $22.00 take the headaches and pain, and probable lawsuit. I mean come on, the dude is opening another office he's not "THAT" broke. it's just business if he's expanding he needs to support it properly.
>even if they don't take that advice. Don't offer any guaranty on the security
>of the solution but do tell them they must do "due diligence".
As IT guys, we normally have the whole trying to squeeze blood from a turnip thing on all networks, but a dentists office stall needs to be HIPPA compliant. this is a type of case where If the Doctor/Dentist kept the budget so tight that I couldn't do the right type of setup, I'd make them sign the "against medical advice" form. I'd write up an agreement form that says basically:
I am implementing a solution that I know is not going to work long term, I DO NOT Warranty either the work or intellectual property, I am implementing an IT strategy I feel is going to fail and I think it's a bad plan. I will not even give my famous 30 and 30 warranty (30 feet 30 seconds) because I'm certain it's going to fail and leak information and is a problem just waiting to happen. You the Doctor must acknowledge that YOU are taking full responsibility for this project, and since you have refused my professional advice at every turn are agreeing to not hold me responsible in any way or manner for the results of this plan sign here __________________________
of course I'd make it more legal and proper grammar, but that's the jist. Most doctors/lawyers I've ever dealt with either get reasonable, or fire me on the spot, either way is good, let the next guy that tries to make a remote solution for $22.00 take the headaches and pain, and probable lawsuit. I mean come on, the dude is opening another office he's not "THAT" broke. it's just business if he's expanding he needs to support it properly.