Questions

T-1 or another communication line need to be set up?

Tags:
+
0 Votes
Locked

T-1 or another communication line need to be set up?

luv2bike2
Here is the situation:
Company" A" LAN is set up at one site in one city and connects to LAN HQ in another city through a T1 than it goes out to the "Cloud". Even though it is slow it is working. Company "A" has just recieved a contract to buld parts for Company "B". Comnpany "B" is going to buy all the equipement (i am assuming whatever is needed to connect the 3 or 4 PC's to their server(s) in Company "A" location, along with again i am assuming a switch) to be installed at Company "A" so that Company "B" can monitor the testing, monitor burn-in etc of the parts that Company "A" is building for Company "B". Company "A" wants to know if the T-1 that is already present and ever so slow, will work for Compan "B" to access their computers at Company "A" site or does another T-1 or another communication line need to be set up and if the current T-1 is used will the two LAN's speed get even slower than what it is. Company "A" does not want Company "B" to have access to their LAN - files and printers etc.

if more information is need to assist in answering this please ask away. basically it will be 2 LAN's in one office using the same T-1 connection out.

Thanks in advance.
R
  • +
    0 Votes
    Slayer_

    Isn't T1 only 1.44mbit?

    +
    0 Votes
    timshows

    Then what are you using then? Fiber?

    +
    0 Votes
    Slayer_

    Well my residential cable is 20mbit....

    +
    0 Votes
    info

    It DOES seem outdated, but the main difference is that your residential cable is a 'demand-based' system. If the 20Mbps is available, you get it. If a ton of other people are using the system, you get whatever is left over. With something like a T1, you get guaranteed 1.5Mbps ALL OF THE TIME. Check the price difference between 'demand-based' and 'guaranteed bandwidth' solutions and you'll be shocked. Besides, for most businesses, 1.5Mbps symmetrical is enough.

    +
    0 Votes
    robo_dev

    At a high level, if things are setup properly, a standard T1, (1.54MBS), circuit can work just fine.

    This is a tricky question to answer because a LOT depends on what application and data are going over the network, and if it's all setup properly.

    Part of what you are asking is about the setup where a remote site uses the Internet connection at the main HQ site. Overall this is a really inefficient way to do things, because now ALL the regular traffic from the remote site has to go to/from HQ, AND all the Internet traffic has to go to/from the HQ site....ALL OVER THE SAME INTERFACE. It's like six lanes of traffic going over a one lane road.

    Ideally the remote site should be given it's own Internet connection, however this means HQ has to trust the remote site to use the Internet responsibly....

    For the remote company A and B to connect to each other a VPN connection over the Internet would be the best.

    +
    0 Votes
    info

    I don't think he asked about the remote site using the connection at the main HQ site for all of their Internet needs.

    +
    0 Votes
    info

    On how Company 'B' wants to monitor the data. There's two ways they can go about this, depending on the setup and software. They can either send all of the production data over the Internet via VPN (as robo_dev mentioned) from Company 'A' to Company 'B', where it can be stored and analyzed. Depending on how much data there is, it's still doable, but uses more bandwidth, especially if it needs to happen during working hours, and in real-time. The way I would consider first would be to set up a dedicated Company 'B' computer (or computers) at Company 'A', connected to the equipment. This computer would be accessed via RDP or VNC and remotely controlled. The amount of bandwidth required is very low and since that computer is LAN-based, the speed at which you see the data from the equipment is faster. They can get that computer to save and copy data to Company 'B' only when required.

    Company 'B' access to your network should easily be limited either way you/they go, but again, the RDP/VNC solution seems better. They only control those PCs, which only have access to the equipment, and the VPN connection. Same with the 'fixed' connection.

    You're kind of caught in the middle here. What you need to do is get your HQ to keep you in the loop with what Company 'B' wants, and what they're prepared to provide. You could quite easily provide a dedicated connection, even segregated, for Company 'B' yourself, but this would probably violate an HQ policy because now the possibility is there that someone from the outside could access your's and the HQ network...

    +
    0 Votes
    TG2

    Look .. a lot of what you're asking requires a good deal of presumption.

    1) what kind of connectivity is available in both locations.
    2) can the same service provider be used to service both locations?

    -- case in point, #2 ... say you went with Cox or Comcast Business Cable, and took 20/10 speeds (20 meg down 10 meg up, if they offer it) ... if *both* locations could get on Cox .. Or Comcast as the same carrier .... then a VPN between office locations would *more likely* be a good fit..

    Why? Because your VPN from site to site would not need to traverse the 'internet' at large to get from one to the other .. it would *only* go the backbone of the provider ...

    3) VPN an option? it should be.. this would allow you to create multiple zones... 1 zone in each location is office systems .. and neither of the offices from one side shall see the other side's internal lan ... 1 zone will be your atypical DMZ with web servers or what have you .. and then the 3rd zone ... at least at your A office side .. would be where your test computer things.. are located.. so that the other company can have access to them ...

    4) check to see if MetroE services are available (Metro "Ethernet") Again you would VPN each other .. and these can be sub 1000 per side depending on the speeds chosen ..

    In any case .. the main things to try to do, are to stop sending traffic across the lines.. that should go out locally ... example in the extreme.. say in your A side's office building there is a Sandwich shop ... they run their own web server and take orders ... why should your traffic to the sub shop go from your office .... out to the other office *then* go to the internet to route back to ISP-X into the subshop downstairs from you!?

    Now.. the reason to skip the T1 .. depending on the number of users you are servicing ... is because as the technology used in the web advances ... more and more often you will find people "abusing" the bandwidth without consciously thinking they are doing so..

    Add to this decade of Youtube and Facebook consumptionism ... the data that you need to go back and forth from office to office, and you're now putting-on Data Fights with datahogs going at each other in a battle royale.

    So ... unless security and absolute uptime with guaranteed government mandated SLA's are a requirement .... high speed data connections in each location, with good VPN's are a good way to go (..ie FCC mandates 4 hour SLA for Technician working on a T1 line ... where your cable or DSL internet provider would service you "as best as possible", with the only SLA being the amount they would pay you if their service failed)

    Anyway.. lots to think about out ... lots to look at pricing for ... and you may want to look around for Data Management companies that can help you by doing actual resource analysis ... and they they would help you by ordering the lines, etc..

    Had good dealings with some companies in the past that were just absolutely awesome when it came to pricing, ordering, and turn-up ... though it was in the T1 hay-days ....

    +
    0 Votes
    robo_dev

    At a high level, if things are setup properly, a standard T1, (1.54MBS), circuit can work just fine.

    This is a tricky question to answer because a LOT depends on what application and data are going over the network, and if it's all setup properly.

    Part of what you are asking is about the setup where a remote site uses the Internet connection at the main HQ site. Overall this is a really inefficient way to do things, because now ALL the regular traffic from the remote site has to go to/from HQ, AND all the Internet traffic has to go to/from the HQ site....ALL OVER THE SAME INTERFACE. It's like six lanes of traffic going over a one lane road.

    Ideally the remote site should be given it's own Internet connection, however this means HQ has to trust the remote site to use the Internet responsibly....

    For the remote company A and B to connect to each other a VPN connection over the Internet would be the best.

    +
    0 Votes
    info

    On how Company 'B' wants to monitor the data. There's two ways they can go about this, depending on the setup and software. They can either send all of the production data over the Internet via VPN (as robo_dev mentioned) from Company 'A' to Company 'B', where it can be stored and analyzed. Depending on how much data there is, it's still doable, but uses more bandwidth, especially if it needs to happen during working hours, and in real-time. The way I would consider first would be to set up a dedicated Company 'B' computer (or computers) at Company 'A', connected to the equipment. This computer would be accessed via RDP or VNC and remotely controlled. The amount of bandwidth required is very low and since that computer is LAN-based, the speed at which you see the data from the equipment is faster. They can get that computer to save and copy data to Company 'B' only when required.

    Company 'B' access to your network should easily be limited either way you/they go, but again, the RDP/VNC solution seems better. They only control those PCs, which only have access to the equipment, and the VPN connection. Same with the 'fixed' connection.

    You're kind of caught in the middle here. What you need to do is get your HQ to keep you in the loop with what Company 'B' wants, and what they're prepared to provide. You could quite easily provide a dedicated connection, even segregated, for Company 'B' yourself, but this would probably violate an HQ policy because now the possibility is there that someone from the outside could access your's and the HQ network...

    +
    0 Votes
    TG2

    Look .. a lot of what you're asking requires a good deal of presumption.

    1) what kind of connectivity is available in both locations.
    2) can the same service provider be used to service both locations?

    -- case in point, #2 ... say you went with Cox or Comcast Business Cable, and took 20/10 speeds (20 meg down 10 meg up, if they offer it) ... if *both* locations could get on Cox .. Or Comcast as the same carrier .... then a VPN between office locations would *more likely* be a good fit..

    Why? Because your VPN from site to site would not need to traverse the 'internet' at large to get from one to the other .. it would *only* go the backbone of the provider ...

    3) VPN an option? it should be.. this would allow you to create multiple zones... 1 zone in each location is office systems .. and neither of the offices from one side shall see the other side's internal lan ... 1 zone will be your atypical DMZ with web servers or what have you .. and then the 3rd zone ... at least at your A office side .. would be where your test computer things.. are located.. so that the other company can have access to them ...

    4) check to see if MetroE services are available (Metro "Ethernet") Again you would VPN each other .. and these can be sub 1000 per side depending on the speeds chosen ..

    In any case .. the main things to try to do, are to stop sending traffic across the lines.. that should go out locally ... example in the extreme.. say in your A side's office building there is a Sandwich shop ... they run their own web server and take orders ... why should your traffic to the sub shop go from your office .... out to the other office *then* go to the internet to route back to ISP-X into the subshop downstairs from you!?

    Now.. the reason to skip the T1 .. depending on the number of users you are servicing ... is because as the technology used in the web advances ... more and more often you will find people "abusing" the bandwidth without consciously thinking they are doing so..

    Add to this decade of Youtube and Facebook consumptionism ... the data that you need to go back and forth from office to office, and you're now putting-on Data Fights with datahogs going at each other in a battle royale.

    So ... unless security and absolute uptime with guaranteed government mandated SLA's are a requirement .... high speed data connections in each location, with good VPN's are a good way to go (..ie FCC mandates 4 hour SLA for Technician working on a T1 line ... where your cable or DSL internet provider would service you "as best as possible", with the only SLA being the amount they would pay you if their service failed)

    Anyway.. lots to think about out ... lots to look at pricing for ... and you may want to look around for Data Management companies that can help you by doing actual resource analysis ... and they they would help you by ordering the lines, etc..

    Had good dealings with some companies in the past that were just absolutely awesome when it came to pricing, ordering, and turn-up ... though it was in the T1 hay-days ....

  • +
    0 Votes
    Slayer_

    Isn't T1 only 1.44mbit?

    +
    0 Votes
    timshows

    Then what are you using then? Fiber?

    +
    0 Votes
    Slayer_

    Well my residential cable is 20mbit....

    +
    0 Votes
    info

    It DOES seem outdated, but the main difference is that your residential cable is a 'demand-based' system. If the 20Mbps is available, you get it. If a ton of other people are using the system, you get whatever is left over. With something like a T1, you get guaranteed 1.5Mbps ALL OF THE TIME. Check the price difference between 'demand-based' and 'guaranteed bandwidth' solutions and you'll be shocked. Besides, for most businesses, 1.5Mbps symmetrical is enough.

    +
    0 Votes
    robo_dev

    At a high level, if things are setup properly, a standard T1, (1.54MBS), circuit can work just fine.

    This is a tricky question to answer because a LOT depends on what application and data are going over the network, and if it's all setup properly.

    Part of what you are asking is about the setup where a remote site uses the Internet connection at the main HQ site. Overall this is a really inefficient way to do things, because now ALL the regular traffic from the remote site has to go to/from HQ, AND all the Internet traffic has to go to/from the HQ site....ALL OVER THE SAME INTERFACE. It's like six lanes of traffic going over a one lane road.

    Ideally the remote site should be given it's own Internet connection, however this means HQ has to trust the remote site to use the Internet responsibly....

    For the remote company A and B to connect to each other a VPN connection over the Internet would be the best.

    +
    0 Votes
    info

    I don't think he asked about the remote site using the connection at the main HQ site for all of their Internet needs.

    +
    0 Votes
    info

    On how Company 'B' wants to monitor the data. There's two ways they can go about this, depending on the setup and software. They can either send all of the production data over the Internet via VPN (as robo_dev mentioned) from Company 'A' to Company 'B', where it can be stored and analyzed. Depending on how much data there is, it's still doable, but uses more bandwidth, especially if it needs to happen during working hours, and in real-time. The way I would consider first would be to set up a dedicated Company 'B' computer (or computers) at Company 'A', connected to the equipment. This computer would be accessed via RDP or VNC and remotely controlled. The amount of bandwidth required is very low and since that computer is LAN-based, the speed at which you see the data from the equipment is faster. They can get that computer to save and copy data to Company 'B' only when required.

    Company 'B' access to your network should easily be limited either way you/they go, but again, the RDP/VNC solution seems better. They only control those PCs, which only have access to the equipment, and the VPN connection. Same with the 'fixed' connection.

    You're kind of caught in the middle here. What you need to do is get your HQ to keep you in the loop with what Company 'B' wants, and what they're prepared to provide. You could quite easily provide a dedicated connection, even segregated, for Company 'B' yourself, but this would probably violate an HQ policy because now the possibility is there that someone from the outside could access your's and the HQ network...

    +
    0 Votes
    TG2

    Look .. a lot of what you're asking requires a good deal of presumption.

    1) what kind of connectivity is available in both locations.
    2) can the same service provider be used to service both locations?

    -- case in point, #2 ... say you went with Cox or Comcast Business Cable, and took 20/10 speeds (20 meg down 10 meg up, if they offer it) ... if *both* locations could get on Cox .. Or Comcast as the same carrier .... then a VPN between office locations would *more likely* be a good fit..

    Why? Because your VPN from site to site would not need to traverse the 'internet' at large to get from one to the other .. it would *only* go the backbone of the provider ...

    3) VPN an option? it should be.. this would allow you to create multiple zones... 1 zone in each location is office systems .. and neither of the offices from one side shall see the other side's internal lan ... 1 zone will be your atypical DMZ with web servers or what have you .. and then the 3rd zone ... at least at your A office side .. would be where your test computer things.. are located.. so that the other company can have access to them ...

    4) check to see if MetroE services are available (Metro "Ethernet") Again you would VPN each other .. and these can be sub 1000 per side depending on the speeds chosen ..

    In any case .. the main things to try to do, are to stop sending traffic across the lines.. that should go out locally ... example in the extreme.. say in your A side's office building there is a Sandwich shop ... they run their own web server and take orders ... why should your traffic to the sub shop go from your office .... out to the other office *then* go to the internet to route back to ISP-X into the subshop downstairs from you!?

    Now.. the reason to skip the T1 .. depending on the number of users you are servicing ... is because as the technology used in the web advances ... more and more often you will find people "abusing" the bandwidth without consciously thinking they are doing so..

    Add to this decade of Youtube and Facebook consumptionism ... the data that you need to go back and forth from office to office, and you're now putting-on Data Fights with datahogs going at each other in a battle royale.

    So ... unless security and absolute uptime with guaranteed government mandated SLA's are a requirement .... high speed data connections in each location, with good VPN's are a good way to go (..ie FCC mandates 4 hour SLA for Technician working on a T1 line ... where your cable or DSL internet provider would service you "as best as possible", with the only SLA being the amount they would pay you if their service failed)

    Anyway.. lots to think about out ... lots to look at pricing for ... and you may want to look around for Data Management companies that can help you by doing actual resource analysis ... and they they would help you by ordering the lines, etc..

    Had good dealings with some companies in the past that were just absolutely awesome when it came to pricing, ordering, and turn-up ... though it was in the T1 hay-days ....

    +
    0 Votes
    robo_dev

    At a high level, if things are setup properly, a standard T1, (1.54MBS), circuit can work just fine.

    This is a tricky question to answer because a LOT depends on what application and data are going over the network, and if it's all setup properly.

    Part of what you are asking is about the setup where a remote site uses the Internet connection at the main HQ site. Overall this is a really inefficient way to do things, because now ALL the regular traffic from the remote site has to go to/from HQ, AND all the Internet traffic has to go to/from the HQ site....ALL OVER THE SAME INTERFACE. It's like six lanes of traffic going over a one lane road.

    Ideally the remote site should be given it's own Internet connection, however this means HQ has to trust the remote site to use the Internet responsibly....

    For the remote company A and B to connect to each other a VPN connection over the Internet would be the best.

    +
    0 Votes
    info

    On how Company 'B' wants to monitor the data. There's two ways they can go about this, depending on the setup and software. They can either send all of the production data over the Internet via VPN (as robo_dev mentioned) from Company 'A' to Company 'B', where it can be stored and analyzed. Depending on how much data there is, it's still doable, but uses more bandwidth, especially if it needs to happen during working hours, and in real-time. The way I would consider first would be to set up a dedicated Company 'B' computer (or computers) at Company 'A', connected to the equipment. This computer would be accessed via RDP or VNC and remotely controlled. The amount of bandwidth required is very low and since that computer is LAN-based, the speed at which you see the data from the equipment is faster. They can get that computer to save and copy data to Company 'B' only when required.

    Company 'B' access to your network should easily be limited either way you/they go, but again, the RDP/VNC solution seems better. They only control those PCs, which only have access to the equipment, and the VPN connection. Same with the 'fixed' connection.

    You're kind of caught in the middle here. What you need to do is get your HQ to keep you in the loop with what Company 'B' wants, and what they're prepared to provide. You could quite easily provide a dedicated connection, even segregated, for Company 'B' yourself, but this would probably violate an HQ policy because now the possibility is there that someone from the outside could access your's and the HQ network...

    +
    0 Votes
    TG2

    Look .. a lot of what you're asking requires a good deal of presumption.

    1) what kind of connectivity is available in both locations.
    2) can the same service provider be used to service both locations?

    -- case in point, #2 ... say you went with Cox or Comcast Business Cable, and took 20/10 speeds (20 meg down 10 meg up, if they offer it) ... if *both* locations could get on Cox .. Or Comcast as the same carrier .... then a VPN between office locations would *more likely* be a good fit..

    Why? Because your VPN from site to site would not need to traverse the 'internet' at large to get from one to the other .. it would *only* go the backbone of the provider ...

    3) VPN an option? it should be.. this would allow you to create multiple zones... 1 zone in each location is office systems .. and neither of the offices from one side shall see the other side's internal lan ... 1 zone will be your atypical DMZ with web servers or what have you .. and then the 3rd zone ... at least at your A office side .. would be where your test computer things.. are located.. so that the other company can have access to them ...

    4) check to see if MetroE services are available (Metro "Ethernet") Again you would VPN each other .. and these can be sub 1000 per side depending on the speeds chosen ..

    In any case .. the main things to try to do, are to stop sending traffic across the lines.. that should go out locally ... example in the extreme.. say in your A side's office building there is a Sandwich shop ... they run their own web server and take orders ... why should your traffic to the sub shop go from your office .... out to the other office *then* go to the internet to route back to ISP-X into the subshop downstairs from you!?

    Now.. the reason to skip the T1 .. depending on the number of users you are servicing ... is because as the technology used in the web advances ... more and more often you will find people "abusing" the bandwidth without consciously thinking they are doing so..

    Add to this decade of Youtube and Facebook consumptionism ... the data that you need to go back and forth from office to office, and you're now putting-on Data Fights with datahogs going at each other in a battle royale.

    So ... unless security and absolute uptime with guaranteed government mandated SLA's are a requirement .... high speed data connections in each location, with good VPN's are a good way to go (..ie FCC mandates 4 hour SLA for Technician working on a T1 line ... where your cable or DSL internet provider would service you "as best as possible", with the only SLA being the amount they would pay you if their service failed)

    Anyway.. lots to think about out ... lots to look at pricing for ... and you may want to look around for Data Management companies that can help you by doing actual resource analysis ... and they they would help you by ordering the lines, etc..

    Had good dealings with some companies in the past that were just absolutely awesome when it came to pricing, ordering, and turn-up ... though it was in the T1 hay-days ....