Set up public ip on server [on hold] The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Windows Server 2008 Routing / NAT - USB Wireless adapter not showing upTraceroute showing weird path. Is load balancing router is responsible for this?ufw portforwarding to virtualbox guestDomain Based Port Forwarding with VLAN routingSetting up a server that routes local traffic through vpn, while still being able to access internet directlyRouting two subnetworks through the same gatewayKVM port-forwarding from ppp0 to VM's bridged NIC not working, but to VM's NAT NIC works?additional public IP and local networkAllow transparent port forwarding in Azure subnetAfter adding firewall rule, why did my Discord get the error “No Route”?
Do ℕ, mathbbN, BbbN, symbbN effectively differ, and is there a "canonical" specification of the naturals?
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
Why doesn't a hydraulic lever violate conservation of energy?
What aspect of planet Earth must be changed to prevent the industrial revolution?
Why are PDP-7-style microprogrammed instructions out of vogue?
Can each chord in a progression create its own key?
Variable with quotation marks "$()"
Why can't wing-mounted spoilers be used to steepen approaches?
should truth entail possible truth
Was credit for the black hole image misappropriated?
Word to describe a time interval
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
Is there a way to generate uniformly distributed points on a sphere from a fixed amount of random real numbers per point?
What can I do if neighbor is blocking my solar panels intentionally?
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
Loose spokes after only a few rides
How did passengers keep warm on sail ships?
Does Parliament need to approve the new Brexit delay to 31 October 2019?
What's the point in a preamp?
Huge performance difference of the command find with and without using %M option to show permissions
One-dimensional Japanese puzzle
Accepted by European university, rejected by all American ones I applied to? Possible reasons?
What information about me do stores get via my credit card?
Mortgage adviser recommends a longer term than necessary combined with overpayments
Set up public ip on server [on hold]
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Windows Server 2008 Routing / NAT - USB Wireless adapter not showing upTraceroute showing weird path. Is load balancing router is responsible for this?ufw portforwarding to virtualbox guestDomain Based Port Forwarding with VLAN routingSetting up a server that routes local traffic through vpn, while still being able to access internet directlyRouting two subnetworks through the same gatewayKVM port-forwarding from ppp0 to VM's bridged NIC not working, but to VM's NAT NIC works?additional public IP and local networkAllow transparent port forwarding in Azure subnetAfter adding firewall rule, why did my Discord get the error “No Route”?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am not quite sure if this should belong here but how do I add public ip to my server?
I wanted to launch a system in Server B live to internet. The problem is no physical connection is linked between my server(Server A) and the Server B.
What I noticed with Server B was:
- the server is using dynamic ip
- the server is located on the other street so cabling is not an option
- it has a default gateway 192.168.0.70.1
- I also noticed that only those PC's connected to the wifi was able to connect to the system.
I have read somewhere that assigning Public IP and Port Forwarding to Server B will probably help me launch that system live to the internet.
The problem is I have little/to no knowledge at networking and every term is like a puzzle to me.
routing port-forwarding
edited Apr 8 at 17:00
Community♦
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by HBruijn, Jenny D, rnxrx, kubanczyk, Ward♦ Apr 9 at 0:57
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HBruijn, Jenny D, rnxrx, kubanczyk, Ward
add a comment |
I am not quite sure if this should belong here but how do I add public ip to my server?
I wanted to launch a system in Server B live to internet. The problem is no physical connection is linked between my server(Server A) and the Server B.
What I noticed with Server B was:
- the server is using dynamic ip
- the server is located on the other street so cabling is not an option
- it has a default gateway 192.168.0.70.1
- I also noticed that only those PC's connected to the wifi was able to connect to the system.
I have read somewhere that assigning Public IP and Port Forwarding to Server B will probably help me launch that system live to the internet.
The problem is I have little/to no knowledge at networking and every term is like a puzzle to me.
routing port-forwarding
edited Apr 8 at 17:00
Community♦
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by HBruijn, Jenny D, rnxrx, kubanczyk, Ward♦ Apr 9 at 0:57
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HBruijn, Jenny D, rnxrx, kubanczyk, Ward
2
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
1
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49
add a comment |
I am not quite sure if this should belong here but how do I add public ip to my server?
I wanted to launch a system in Server B live to internet. The problem is no physical connection is linked between my server(Server A) and the Server B.
What I noticed with Server B was:
- the server is using dynamic ip
- the server is located on the other street so cabling is not an option
- it has a default gateway 192.168.0.70.1
- I also noticed that only those PC's connected to the wifi was able to connect to the system.
I have read somewhere that assigning Public IP and Port Forwarding to Server B will probably help me launch that system live to the internet.
The problem is I have little/to no knowledge at networking and every term is like a puzzle to me.
routing port-forwarding
edited Apr 8 at 17:00
Community♦
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am not quite sure if this should belong here but how do I add public ip to my server?
I wanted to launch a system in Server B live to internet. The problem is no physical connection is linked between my server(Server A) and the Server B.
What I noticed with Server B was:
- the server is using dynamic ip
- the server is located on the other street so cabling is not an option
- it has a default gateway 192.168.0.70.1
- I also noticed that only those PC's connected to the wifi was able to connect to the system.
I have read somewhere that assigning Public IP and Port Forwarding to Server B will probably help me launch that system live to the internet.
The problem is I have little/to no knowledge at networking and every term is like a puzzle to me.
routing port-forwarding
routing port-forwarding
edited Apr 8 at 17:00
Community♦
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 8 at 17:00
Community♦
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 8 at 17:00
Community♦
1
edited Apr 8 at 17:00
Community♦
1
edited Apr 8 at 17:00
Community♦
1
1
asked Apr 8 at 7:12
marvin castromarvin castro
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 7:12
marvin castromarvin castro
142
asked Apr 8 at 7:12
marvin castromarvin castro
142
142
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
marvin castro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by HBruijn, Jenny D, rnxrx, kubanczyk, Ward♦ Apr 9 at 0:57
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HBruijn, Jenny D, rnxrx, kubanczyk, Ward
put on hold as off-topic by HBruijn, Jenny D, rnxrx, kubanczyk, Ward♦ Apr 9 at 0:57
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HBruijn, Jenny D, rnxrx, kubanczyk, Ward
2
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
1
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49
add a comment |
2
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
1
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49
2
2
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
1
1
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49
add a comment |
1 Answer
1
active
oldest
votes
Presenting a service to the Internet definitely should not be done unless you know what you're doing. Fortunately it's mostly a matter of not being naïve, but you definitely should have passed a certain threshold of knowledge before you attempt this.
Assuming you're the single person who will have to manage this solution, here are some concepts with which you should be somewhat familiar before attempting to set up a public server:
- Network firewall concepts and rules.
- IPv4 routing.
- DNS and Dynamic DNS
- Securing Internet traffic using TLS
- TLS Certificates and their management
Tip: Practice these things in a test environment separate from your production environment. If money is an issue, you can "invest" in a test environment as small as a regular home DSL router and a Raspberry Pi, as long as you have access to a public IP.
And since this is supposed to be an Internet facing production service, don't skimp on your training. Nobody will thank you for it.
answered Apr 8 at 7:36
Mikael HMikael H
811210
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
|
show 5 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Presenting a service to the Internet definitely should not be done unless you know what you're doing. Fortunately it's mostly a matter of not being naïve, but you definitely should have passed a certain threshold of knowledge before you attempt this.
Assuming you're the single person who will have to manage this solution, here are some concepts with which you should be somewhat familiar before attempting to set up a public server:
- Network firewall concepts and rules.
- IPv4 routing.
- DNS and Dynamic DNS
- Securing Internet traffic using TLS
- TLS Certificates and their management
Tip: Practice these things in a test environment separate from your production environment. If money is an issue, you can "invest" in a test environment as small as a regular home DSL router and a Raspberry Pi, as long as you have access to a public IP.
And since this is supposed to be an Internet facing production service, don't skimp on your training. Nobody will thank you for it.
answered Apr 8 at 7:36
Mikael HMikael H
811210
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
|
show 5 more comments
Presenting a service to the Internet definitely should not be done unless you know what you're doing. Fortunately it's mostly a matter of not being naïve, but you definitely should have passed a certain threshold of knowledge before you attempt this.
Assuming you're the single person who will have to manage this solution, here are some concepts with which you should be somewhat familiar before attempting to set up a public server:
- Network firewall concepts and rules.
- IPv4 routing.
- DNS and Dynamic DNS
- Securing Internet traffic using TLS
- TLS Certificates and their management
Tip: Practice these things in a test environment separate from your production environment. If money is an issue, you can "invest" in a test environment as small as a regular home DSL router and a Raspberry Pi, as long as you have access to a public IP.
And since this is supposed to be an Internet facing production service, don't skimp on your training. Nobody will thank you for it.
answered Apr 8 at 7:36
Mikael HMikael H
811210
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
|
show 5 more comments
Presenting a service to the Internet definitely should not be done unless you know what you're doing. Fortunately it's mostly a matter of not being naïve, but you definitely should have passed a certain threshold of knowledge before you attempt this.
Assuming you're the single person who will have to manage this solution, here are some concepts with which you should be somewhat familiar before attempting to set up a public server:
- Network firewall concepts and rules.
- IPv4 routing.
- DNS and Dynamic DNS
- Securing Internet traffic using TLS
- TLS Certificates and their management
Tip: Practice these things in a test environment separate from your production environment. If money is an issue, you can "invest" in a test environment as small as a regular home DSL router and a Raspberry Pi, as long as you have access to a public IP.
And since this is supposed to be an Internet facing production service, don't skimp on your training. Nobody will thank you for it.
answered Apr 8 at 7:36
Mikael HMikael H
811210
Presenting a service to the Internet definitely should not be done unless you know what you're doing. Fortunately it's mostly a matter of not being naïve, but you definitely should have passed a certain threshold of knowledge before you attempt this.
Assuming you're the single person who will have to manage this solution, here are some concepts with which you should be somewhat familiar before attempting to set up a public server:
- Network firewall concepts and rules.
- IPv4 routing.
- DNS and Dynamic DNS
- Securing Internet traffic using TLS
- TLS Certificates and their management
Tip: Practice these things in a test environment separate from your production environment. If money is an issue, you can "invest" in a test environment as small as a regular home DSL router and a Raspberry Pi, as long as you have access to a public IP.
And since this is supposed to be an Internet facing production service, don't skimp on your training. Nobody will thank you for it.
answered Apr 8 at 7:36
Mikael HMikael H
811210
answered Apr 8 at 7:36
Mikael HMikael H
811210
answered Apr 8 at 7:36
Mikael HMikael H
811210
answered Apr 8 at 7:36
Mikael HMikael H
811210
811210
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
|
show 5 more comments
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
Well I have done all of these things. I am just poor at doing network. I am scared of hitting an IP Address if ever I will set a Public IP
– marvin castro
Apr 8 at 8:20
2
2
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: "Hitting an IP address"? What does that even mean? If you mean "using an IP address that's already in use by someone else", then Stop.Right.Now. I agree with this answer (+1), you need to understand Internet Technology to a much better level if you want to safely put something on the Internet that won't be hacked in minutes. I'm serious; that is the time it takes to break into an unsecured server on the 'Net.
– MSalters
Apr 8 at 10:32
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
@marvincastro: I'm really not a proponent of "easy" answers to this sort of question, because doing these things well does require a small but solid set of knowledge in a number of areas (see my earlier post), and the only good way of achieving that is through reading and practice. It doesn't have to be expensive, but it has to be allowed to take some time.
– Mikael H
Apr 8 at 11:12
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
can anyone recommend some resources for these 5 concepts?
– Mike Palmice
Apr 8 at 13:44
1
1
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
@marvincastro: unfortunately, Mikael H is right. I think I understand what you mean by "hitting an IP address", you probably mean using one that is already in use. This would cause absolutely no problem to anyone but you, for the simple reason that things work differently: your ISP would give you an IP. If you try using another, nobody will reach your machine, and the fact you don't understand this shows that you don't have proper knowledge of routing.
– user1532080
Apr 8 at 13:45
|
show 5 more comments
2
The first step is to ask your ISP to assign you a public IP address if they don’t give you one by default. It might be either static or dynamic (accessible from outside but not guaranteed to be constant). This and many more things will influence further steps (see Mikael’s answer). Unfortunately, this question cannot be answered generally.
– Melebius
Apr 8 at 11:56
1
It is also very unclear what the link to Server A is. You just mention it's not linked to Server B, but don't say a word about how is should be interacting with it (if at all). Which makes me think you could even be looking at VPN between A & B, and something like giving external access to Server B from Internet (might be achieved thru port forwarding on some your consumer grade router)
– user1532080
Apr 8 at 13:49