In order for us to allow the Acumatica system to relay our domain and send emails from the Acumatica system I need to open our firewall for the Acumatica sending mail servers. Does anyone happen to know the IP address or IP range of the Acumatica sending mail servers? We host our exchange in-house which is why it is needed.
You need to lookup the servers you are using on page System Email Accounts SM204002:
Usually it's trickier to identify the ports than the IP. For IP you can resolve the host name of the server. Ex: hostname is outlook.office365.com in image above, it resolves to:
The ports will very likely be the same as any other public SMTP server. You know which port to target based on SMTP server type (incoming/outgoing/relay), authentication support (SSL/TLS). For reference from this link:
We were able to figure it out by pinging our Acumatica site. With that IP we were able to put a secure path through our firewall so that it can talk to our internal exchange server. Hopefully, the IP will not change and this setting will continue to work.
For those who need the IP of there Acumatica site ping your site (ex. name.acumatica.com) this IP is the relying IP that Acumatica uses for your account to send mail through there system.
IP Addresses can tend to change. I believe what you are referring to is you are opening firewalls based on specific ip addresses. The challenge there is the Acumatica IP address could change one day and without any notice your email will stop working.
I recommend using an SMTP Server that is open, but requires authentication (logging in) in order to relay emails.
Related
I need to send a fake IP address to a defined server (ip) due to the need for security and distrust in that server. Unfortunately, I have to use this server, but I do not want fake IP to be sent to all servers where I connect. I need it for windows operating system.
Does anyone know how to do this?
I make a web site to my local. I set bindings local.com and www.local.com. I add hosts xml to
127.0.0.1 local.com
127.0.0.1 www.local.com
So, I can connet on my pc like
local.com,
www.local.com,
192.168.1.35
But another pc on my network can't conenct with friendly name
www.local.com,
local.com,
But same pc can connet with ip
192.168.1.35
How can that another pc connect with friendly name ?
IP Addresses are the numerical identification for each device on a computer network.
Named Addresses invented, because remembering each device Address's turned to a difficult job.
So someone must know's which names must be converted to which IP Address.
DNS Servers are responsible to do this translation. But you done that locally. Actually you don't have a DNS Server on your local System, So you can't tell to others that "WWW.Something.COM" is my Address.
If you didn't connected to the internet, you must establish a DNS Server or done this task manually in all clients:
https://helpdeskgeek.com/networking/edit-hosts-file/
Running a DNS Server is another task. you can search for DNS Server applications like https://simpledns.com/ or you can setup a DNS Server using Windows Server. for both scenarios you need to tell to your clients to add your DNS Server Address to their network Adapter settings.
or If you are connected to the Internet, you can Use a NoIP to register a free Address:
https://www.noip.com/
you then need to download an application (In Noip.com) to monitor IP changes, it will monitors your IP address and it changes and then tells to NOIP.com to translate your address into your current IP address.
Actually NOIP will registers your address globally around the Internet network and each one who can access to the internet is able to reach to your address.
I came into a struggle the last few days.
Using WAMP Server and following this Tutorial I set up a local email environment, and I wanted to make the emails reach accounts outside of the local host.
I heard you need to make some changes in the DNS zone, so here is my DNS Zone at Freenom.
Is is possible to make emails sent from a computer using hMailServer reach the outside world through a domain?
Thank you for your time.
It is possible but it depends on your Scenario.
If you are behind a Router or a NAT or a Dynamic IP-Address it's almost not possible
to run a real World sending SMTP-Server and you shouldn't
If you have a Hosting plan (your own Windows V-Server or Root server) with Remote Desktop
access and a static ip address it's and access to the DNS-Configuration of your Internet Domain, it is possible and recommended.
1) First you need to setup a DNS A Record which points to your static IP in DNS
2) You need to create DNS MX Record which points to your A Record
Now you can add a new hMailServer Domain and add accounts and sent Emails
out. But you should setup a DNS A Record for IMAP or POP3 as well so you can
Receive Emails and not only sending.
One of our customers is planning to change the public IP address of their server where their website is hosted (in-house on IIS).
The website was built with Classic ASP.
What changes are needed on the server after the IP address change, and where would they be?
(I know this question is very vague but this is all the information I have for now - apologies.)
Normally there will be no dependencies on a specific IP address in classic ASP.
IIS ofcourse manages on which IP address(es) and which hostnames the (asp) site will respond (in the bindings setting for the site), and the public DNS settings are responsible for routing the proper hostname to the correct (new) IP address, but ASP code doesn't care about hostnames or ip-addresses, it just responds to whatever IIS thinks should be handled by the site in question.
The DNS will propably be hosted at the companies Internet provider, you should check if the site in IIS has the correct bindings, and if it is not configured to respond to specifically the old IP address.
If the server uses multiple IP addresses you may need to alter the bindings in IIS manager to ensure that the domain of your website is associated with the correct IP, and obviously you will need to update the DNS record for your domain. Neither of these are specific to Classic ASP
One of our client wants to do port forwarding to the crm server , so that users can access the crm from Internet. They are using ZyXel firewall (for port forwarding).
They have mapped 203.xx.xx.xx(public ip) to 192.Xx.xx.xx(local ip) with incoming and outgoing port 5555(default port of our crm server), but it doesn't work. Any suggestions?
I tried to map for rdp and sql report server(web server), these things are able to access.
I have been stuck with this more than a day. Can anyone please help
It's more common to see full IFD implementation with crm 2011, since SSL allows for more security. I do think it's possible to configure CRM to work with just regular port forwarding though, although I have never done it myself.
Take a look here: http://www.mscrmguru.com/2013/05/exposing-microsoft-dynamics-crm-2011.html
Examples of software that can be used for port forwarding includes
Microsoft Forefront Treat Management Gateway (TMG) and Microsoft
Forefront Unified Access Gateway. Basically what it comes down to is
the following:
The user enters an internet address e.g. http://crm.mycompany.com.au
The internet address is recognised and points to the external
registered IP address e.g. 162.123.123.11
The external IP address is redirected to your internal IP address
through your reverse proxy / tunnelling / port forwarding e.g.
10.0.0.10
The user enters username and password and gets authenticated.
The Microsoft Dynamics CRM 2011 pages is displayed to the user.
Finally I solved the issue by binding port 80 to the crm website in IIS. Not sure why 5555 port didnt work, even though the port is opened in the firewall.
You have to add a corresponding Policy Control to pair with the corresponding NAT rule otherwise when the NAT / port forwarding rule is applied, it will be directed to the stateful packet inspection part of the device controlled by the Policy Control rules and be dropped from that point forward.
Policy Control is found by selecting the Configuration menu option (looks like two yellow gear or cogs whatever you call them), then selecting Security Policy, then Policy Control.
The rule structure is similar to NAT, except on this screen you permit or deny traffic based on ZONES that maps to any physical or logical interface configured. In most cases, you want to permit port 5555 traffic coming from the WAN zone from ANY IP address, to the LAN, DMZ or VLAN zones to the IP of the host or object configured in the ZyXEL firewall.
You'll want to ensure that port 5555/TCP or 5555/UDP, whichever is applicable to permit, is configured as a Service Object under the Configuration->Object->Service menu.
Configuring the service before will allow easy setup afterwards when setting your NAT and policy rules, because you'll be able to select the new service object instead of entering ports only. It's also required to set a service object anyways for all Policy Routes.
It feels like the work has been done twice, but NAT and Policy Routes are two different things that have to be configured to allow most kinds of non-standard traffic. You admin might have had an easier time configuring other rules such as HTTP, FTP, SMTP and various common services, because the firewall has built-in objects for those services, which makes configuring rules for services running non-standard high-range ports a little but more tricky.