Hfrxdjt

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Is it wise to focus on putting odd beats on left when playing double bass drums?

Symmetry in quantum mechanics

Was there ever an axiom rendered a theorem?

What are the advantages and disadvantages of running one shots compared to campaigns?

Where to refill my bottle in India?

Where else does the Shulchan Aruch quote an authority by name?

If a centaur druid Wild Shapes into a Giant Elk, do their Charge features stack?

Need help identifying/translating a plaque in Tangier, Morocco

What do the Banks children have against barley water?

LWC and complex parameters

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Can I legally use front facing blue light in the UK?

Is it legal to have the "// (c) 2019 John Smith" header in all files when there are hundreds of contributors?

What is the meaning of "of trouble" in the following sentence?

What is GPS' 19 year rollover and does it present a cybersecurity issue?

Manga about a female worker who got dragged into another world together with this high school girl and she was just told she's not needed anymore

How can I fix this gap between bookcases I made?

How to manage monthly salary

Can I find out the caloric content of bread by dehydrating it?

How can I add custom success page

Piano - What is the notation for a double stop where both notes in the double stop are different lengths?

Copycat chess is back

Check if two datetimes are between two others

Set up public ip on server [on hold]

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;

1

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

share|improve this question

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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♦ 45 mins ago

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

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  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
  13 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  11 hours ago
  

  
  
  
  

add a comment | 

1

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

share|improve this question

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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♦ 45 mins ago

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

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  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
  13 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  11 hours ago
  

  
  
  
  

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

share|improve this question

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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.

share|improve this question

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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.

share|improve this question

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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 8 hours ago

Community♦

1

edited 8 hours ago

Community♦

1

asked 18 hours ago

marvin castromarvin castro

121

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 18 hours ago

marvin castromarvin castro

121

1 Answer
1

active

oldest

votes

10

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.

share|improve this answer

answered 18 hours ago

Mikael HMikael H

776110

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  17 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  14 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  can anyone recommend some resources for these 5 concepts?
  
  – Mike Palmice
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  11 hours ago
  
  

  
  
  
  

 | 
show 3 more comments

10

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.

share|improve this answer

answered 18 hours ago

Mikael HMikael H

776110

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  17 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  14 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  can anyone recommend some resources for these 5 concepts?
  
  – Mike Palmice
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  11 hours ago
  
  

  
  
  
  

 | 
show 3 more comments

10

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.

share|improve this answer

answered 18 hours ago

Mikael HMikael H

776110

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  17 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @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
  14 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  can anyone recommend some resources for these 5 concepts?
  
  – Mike Palmice
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  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
  11 hours ago
  
  

  
  
  
  

 | 
show 3 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.

share|improve this answer

answered 18 hours ago

Mikael HMikael H

776110

share|improve this answer

answered 18 hours ago

Mikael HMikael H

776110

answered 18 hours ago

Mikael HMikael H

776110

answered 18 hours ago

Mikael HMikael H

776110