Hi Everyone, Thanks for all responses and information. I'm currently working with Isaac to find the best efficient solution.
Thanks again. Best, Mohammad On Mon, Nov 24, 2014 at 10:58 AM, Mike Howard <[email protected]> wrote: > If your router a consumer grade NAT router, it probably does not have > sufficient logging capability to meet the requirements of the Security > Policy for NAT Devices: https://security.berkeley.edu/NAT.html > > Every server deserves it's own connection, public IP address, and > hostname. You've already paid for the network and firewall service through > the DNR, so take advantage of them and register your hosts properly. > > If your lab needs wiring in the walls for the second server, a new data > jack can be installed for a one-time $307 fee. (This is very reasonable > considering the labor involved.) > > On Mon, Nov 24, 2014 at 10:39 AM, Igor Savine <[email protected]> > wrote: > >> I assume the router comes with a built-in firewall that allows to map >> TCP ports 22 and 33 on the WAN network interface to LAN serverA:22 and >> serverB:33, respectively. >> >> -Igor >> >> On Mon, Nov 24, 2014 at 10:02 AM, Mohammad Soheilypour >> <[email protected]> wrote: >> > Hi Igor, >> > >> > And then what do I need to do on the router to distinguish the two >> servers? >> > >> > Thanks, >> > Mohammad >> > >> > On Mon, Nov 24, 2014 at 9:59 AM, Igor Savine <[email protected]> >> wrote: >> >> >> >> A simple workaround would be using a nonstandard port number (e.g. 33 >> >> instead of 22) on one of the servers. >> >> >> >> -- >> >> Igor Savine >> >> Information Systems Analyst >> >> University of California Berkeley >> >> 993 Evans Hall >> >> Berkeley, CA 94720 >> >> (510) 643-8747 >> >> [email protected] >> >> >> >> On Mon, Nov 24, 2014 at 9:54 AM, Isaac Orr <[email protected]> wrote: >> >> > Hi Mohammad, >> >> > >> >> > Without getting into the specifics of configuring things so this >> >> > works, is there a reason why the servers are connected behind their >> >> > own router? Just curious, because there may be a simpler way to do >> >> > things. >> >> > >> >> > iso >> >> > >> >> > >> >> > On Mon, Nov 24, 2014 at 9:51 AM, Mohammad Soheilypour >> >> > <[email protected]> wrote: >> >> >> Hi Everyone, >> >> >> >> >> >> I'm not quite sure that this is the right place to ask this type of >> >> >> question >> >> >> or not, I hope it is. We have two servers in our lab that are both >> >> >> connected >> >> >> through a router. Both servers have static IPs and we need to be >> able >> >> >> to ssh >> >> >> to each of them. The problem is that we cannot ssh to both of them >> when >> >> >> they >> >> >> are connected to the router (they are in another room and therefore >> we >> >> >> are >> >> >> not in their network), rather we can see only one of them. Is there >> any >> >> >> solution to have both of them connected to the router and also >> >> >> accessible >> >> >> from outside? >> >> >> >> >> >> Best, >> >> >> Mohammad >> >> >> >> >> >> -- >> >> >> Mohammad Soheilypour >> >> >> Molecular Cell Biomechanics Laboratory >> >> >> University of California, Berkeley >> >> >> >> >> >> Email : [email protected] >> >> >> [email protected] >> >> > >> > > -- > Mike Howard > Network Engineer > UC Berkeley SAIT > -- Mohammad Soheilypour Molecular Cell Biomechanics Laboratory University of California, Berkeley Email : [email protected] [email protected]
------------------------------------------------------------------------- The following was automatically added to this message by the list server: To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site: http://micronet.berkeley.edu Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet. This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past.
