Quick Heal IP to be accessed through internet
-
If it is a public IP, what is the issue? Just use the IP address, it should be accessible from anywhere on the Internet. NAT is not a factor for reaching a public IP.
-
@scottalanmiller I need to configure this process in new ISP with new IP
-
@Lakshmana said:
@scottalanmiller I need to configure this process in new ISP with new IP
I don't understand. You have a public IP. Why does the ISP matter? Why do you need to reconfigure?
-
@scottalanmiller said:
Why do you need to reconfigure
Public IP is changed now.Now new IP is provided for this configuration -
So why mention the public IP that you used to have? Is the new one a public IP?
-
I agree with @scottalanmiller. It's a PUBLIC IP. This isn't something inside your network that you need to port forward or NAT through. If it's a PUBLIC IP, it's exposed to the world. We have firewalls and the like to PREVENT people from seeing stuff they aren't supposed to. If this server has a public IP, you should be able to access it over the WAN no issue.
-
@scottalanmiller Now my WAN was changed to another Public IP.so i need to configure at new IP.
-
@Lakshmana said:
@scottalanmiller I already had the IP was (1.1.1.1) and now I have given 2.2.2.2(example).So the WAN was changed now and the service of antivirus has to be configured
Like we've been saying. This makes no sense. It's just an IP address. What is there to reconfigure? Why do you keep mentioning NAT (we talked about this in private IM for a bit.) You've not given any reason, at all, as to why you think there is some reason to talk about the NAT.
-
@Lakshmana said:
@scottalanmiller Now my WAN was changed to another Public IP.so i need to configure at new IP.
Again, this makes no sense.
-
@scottalanmiller OK Forget NAT now.
-
Don't keep saying that you "need to do this or that." Instead, tell us WHY you think the NAT is involved. Changing IP addresses does not affect NAT. Give us why you think NAT is related to this discussion. Either you've not told us what is happening or you don't understand what NAT is. One way or another, you are saying one thing and then saying you need to do something that is completely unrelated and we have no means of connecting the two.
-
@Lakshmana said:
@scottalanmiller OK Forget NAT now.
Very good.
Now, what do you need to accomplish?
-
@Lakshmana Please see this scenario
1)The system in one company with the IP 192.168.1.155
2)The other system from other company 192.168.2.200
3)I need this two system to communicate with the Quick Heal Antivirus.(New Public IP)Whether NATing is needed to be done for this process
-
@Lakshmana said:
1)The system in one company with the IP 192.168.1.155
2)The other system from other company 192.168.2.200These are not public IPs. Are these servers or clients.
-
@Lakshmana said:
Whether NATing is needed to be done for this process
Of course not. You just said that you were going to forget NATing. But here we go again.
NATing is for accessing things that you host, not for accessing things that other people host. Public IP addresses have no configuration in NAT.
Do you configure a NAT rule for every website that people use?
-
@Lakshmana said:
3)I need this two system to communicate with the Quick Heal Antivirus.(New Public IP)
So what's the issue? They should "just work". Have you tested them yet?
-
@scottalanmiller said:
So what's the issue? They should "just work". Have you tested them yet?
OK.I need to do Port restricted Cone NAT.
-
@Lakshmana said:
@scottalanmiller said:
So what's the issue? They should "just work". Have you tested them yet?
OK.I need to do Port restricted Cone NAT.
What does this mean?
-
@scottalanmiller PLease see this link
-
What is the IP address of your Quick Heal device?
(just give us part of it).
