Questions

why is the network slow going to the Cloud?

Tags:
+
0 Votes
Locked

why is the network slow going to the Cloud?

luv2bike2
the network servers (windows) were moved to HQ from being on site several months back, There is a T-1 in this office however the end users were noticing that the network is slow. About 2 months back HQ decided to go with the Cloud. Now the network is soooooo sloooww it is unbelieveable. I do not have experience with working with Clouds and I was hoping someone could shed some light on how to make the network run faster (if possible).

I am not a full time employee for this company, I was laid off when they moved the servers to HQ, however I am contracted with them to help them with IT issues. The end users come up to me and say things like I wish the servers were still here, the network is so slow, i can not do my job because it takes forever to open a file, etc. I do not know which company HQ decided to go with so I do not have much detail to give out here.

Thanks in advance.
R
  • +
    0 Votes
    robo_dev

    Several parts to the network, shared applications, LAN resources such as printers and shared drives, and the Internet.

    Are all three equally slow?

    Is this a Windows-based network?

    Have they moved the domain controllers and mail servers to the cloud?

    For starters, using ping and tracert, see what kind of Ping times you are getting to and from various devices.

    The cloud is no great mystery, it is just a nicer word than 'outsourcing'.

    In your case, how is your office connected to the Internet and to HQ?

    If, for example, you get your Internet connectivity through the HQ connection, and they have moved the Windows server farm offsite, then the bandwidth needed for the HQ internet connection has probably increased by a factor of five or ten.

    Further, if you are now sending gobs of Windows domain traffic over the VPN link back to HQ, you could be over-subscribing that link by a lot.

    +
    0 Votes
    luv2bike2

    Printers and internet is set up locally, printing as far as I can see and have heard has not been a problem unless the end-user is printing something from a shared drive out in the "cloud". The printers are on the Domain Controller that is housed in the local office it is not in the cloud. The internet goes to an Internet Provider that this office has had for years, that has not changed. Shared drives, applications and data is out in the "cloud" and it takes forever for the end-users to open up a file that used to take a second or two.

    This is a Windows-Based Network. Before the move to the cloud the servers were Windows 2003.

    The Domain controllers are still housed in the office they were not moved to the cloud. Though Exchange eMail has been moved to the cloud and it is slow in getting emails.

    I pinged the two domain controllers that are local to this site:
    ping time for both is min 0ms max 1ms

    I pinged 2 of the printers here in the office
    for both of them Min 0ms max 1ms

    I pinged 4 of the servers out in the "cloud" several times and have gotten different results for each of them each time sometime it took less time to ping another time it took more time below is the average time for each of the servers
    Server 1 (terminal server) min 327ms max 349ms
    Server 2 ( application server) min 419ms max 452ms
    Server 3 (file server) min 330ms, max 353ms
    Server 4 (mail server) min 235ms max 305ms
    I do not know what the mail server name is
    This office is connected to the Internet and HQ through a T-1 that has been set up at this office for years and there was no problem connecting to the internet speed wise. This office had no reason to connect to the HQ for anything, however HQ Accounting department needed to connect to this office through Terminal Server and they said it was slow however not as slow as what these end-users are experiencing.

    I believe that was happens is this office goes directly to HQ and from HQ the requests go to the cloud. Since I know Zilch on Cloud computing, is it possible for this office to go directly to the "Cloud" instead of going to HQ? Or do they need to go to HQ to access the "cloud"?
    if they can go directly to the "Cloud", is it easy to set it up, say through their ISP?

    thanks so much for your help/answers
    R

    +
    0 Votes
    robo_dev

    holy cow....452 ms ping times? There's your problem.

    Off the top of my head, it sounds like the 'cloud' traffic has to go over an already slammed HQ Internet interface.

    The tricky part about moving it is to determine how Active Directory is setup, as users have to be able to authenticate to get to Windows resources.

    Terminal services is made to use small packets and go over the internet, so it can play better on a congested link.

    In order for file access to Windows servers to be even remotely usable, your latency needs to be MAXIMUM 90-100 ms. I've worked on projects where the ping times from France to Atlanta were typically 130-150ms, and that's going on undersea fiber.

    400 ms is like satellite internet service speed.

    +
    0 Votes
    Deadly Ernest

    services as it sounds to me like they set your local router up to direct the services now out in the cloud to go via HQ and then onto the cloud provider. Some organisations do it that way so only the one connection has authority to access info.

    After finding out what HQ IT intended and want, you should check the routing and dns info for the servers that are now out in the cloud. See where they're being directed and make sure it's the way the HQ people wanted.

    Also make sure HQ is very much aware of the performance delays being caused by this service, they may need tgo up services from their providers involved along the way.

    +
    0 Votes
    luv2bike2

    I spoke to the manager at this office and it does not seem to bother the manager with the slowness of the network, the manager said that the end users were just used to having the network going fast and now that it is slow the manager said the end users will just have to adjust. Thanks for your input!

    R

  • +
    0 Votes
    robo_dev

    Several parts to the network, shared applications, LAN resources such as printers and shared drives, and the Internet.

    Are all three equally slow?

    Is this a Windows-based network?

    Have they moved the domain controllers and mail servers to the cloud?

    For starters, using ping and tracert, see what kind of Ping times you are getting to and from various devices.

    The cloud is no great mystery, it is just a nicer word than 'outsourcing'.

    In your case, how is your office connected to the Internet and to HQ?

    If, for example, you get your Internet connectivity through the HQ connection, and they have moved the Windows server farm offsite, then the bandwidth needed for the HQ internet connection has probably increased by a factor of five or ten.

    Further, if you are now sending gobs of Windows domain traffic over the VPN link back to HQ, you could be over-subscribing that link by a lot.

    +
    0 Votes
    luv2bike2

    Printers and internet is set up locally, printing as far as I can see and have heard has not been a problem unless the end-user is printing something from a shared drive out in the "cloud". The printers are on the Domain Controller that is housed in the local office it is not in the cloud. The internet goes to an Internet Provider that this office has had for years, that has not changed. Shared drives, applications and data is out in the "cloud" and it takes forever for the end-users to open up a file that used to take a second or two.

    This is a Windows-Based Network. Before the move to the cloud the servers were Windows 2003.

    The Domain controllers are still housed in the office they were not moved to the cloud. Though Exchange eMail has been moved to the cloud and it is slow in getting emails.

    I pinged the two domain controllers that are local to this site:
    ping time for both is min 0ms max 1ms

    I pinged 2 of the printers here in the office
    for both of them Min 0ms max 1ms

    I pinged 4 of the servers out in the "cloud" several times and have gotten different results for each of them each time sometime it took less time to ping another time it took more time below is the average time for each of the servers
    Server 1 (terminal server) min 327ms max 349ms
    Server 2 ( application server) min 419ms max 452ms
    Server 3 (file server) min 330ms, max 353ms
    Server 4 (mail server) min 235ms max 305ms
    I do not know what the mail server name is
    This office is connected to the Internet and HQ through a T-1 that has been set up at this office for years and there was no problem connecting to the internet speed wise. This office had no reason to connect to the HQ for anything, however HQ Accounting department needed to connect to this office through Terminal Server and they said it was slow however not as slow as what these end-users are experiencing.

    I believe that was happens is this office goes directly to HQ and from HQ the requests go to the cloud. Since I know Zilch on Cloud computing, is it possible for this office to go directly to the "Cloud" instead of going to HQ? Or do they need to go to HQ to access the "cloud"?
    if they can go directly to the "Cloud", is it easy to set it up, say through their ISP?

    thanks so much for your help/answers
    R

    +
    0 Votes
    robo_dev

    holy cow....452 ms ping times? There's your problem.

    Off the top of my head, it sounds like the 'cloud' traffic has to go over an already slammed HQ Internet interface.

    The tricky part about moving it is to determine how Active Directory is setup, as users have to be able to authenticate to get to Windows resources.

    Terminal services is made to use small packets and go over the internet, so it can play better on a congested link.

    In order for file access to Windows servers to be even remotely usable, your latency needs to be MAXIMUM 90-100 ms. I've worked on projects where the ping times from France to Atlanta were typically 130-150ms, and that's going on undersea fiber.

    400 ms is like satellite internet service speed.

    +
    0 Votes
    Deadly Ernest

    services as it sounds to me like they set your local router up to direct the services now out in the cloud to go via HQ and then onto the cloud provider. Some organisations do it that way so only the one connection has authority to access info.

    After finding out what HQ IT intended and want, you should check the routing and dns info for the servers that are now out in the cloud. See where they're being directed and make sure it's the way the HQ people wanted.

    Also make sure HQ is very much aware of the performance delays being caused by this service, they may need tgo up services from their providers involved along the way.

    +
    0 Votes
    luv2bike2

    I spoke to the manager at this office and it does not seem to bother the manager with the slowness of the network, the manager said that the end users were just used to having the network going fast and now that it is slow the manager said the end users will just have to adjust. Thanks for your input!

    R