Port for remote domain

Trying to set up my mail account for my website.  Can receive but cannot send.  I know there is a port I can use to get it to work but I haven't been able to recreate my research path for the last time I found the port number.  Can anyone help?

Hi, normally the ports are...
The receiving email ports are:
IMAP is port 143
IMAP-SSL is port 993
POP is port 110
POP-SSL is port 995
Outgoing ports are...
SMTP and SMTP-SSL is on ports 25, 587 and 465. Port 587 has to be SSL, and port 465 is enforced TLS-wrapped and is generally used by Outlook users.

Similar Messages

  • How to use a fixed port for remote assistance in windows 8.1 behind a nat router freebox?

    Hello,
    Before to use remote assistance in windows 8.1, i need to configure my nat router freebox.
    But remote assistance ( msra.exe ) use a dynamique port and never the same.
    How to use a fixed port for remote assistance ini windows 8.1 ?
    And why i can't use easy connect ?
    i read that the router must implement the PNRP protocol. I think it's a propriatary microsoft's protocol unknow on my router.
    Thanks

    Hello,
    Very good. It's a big range ( 255 mini from 49152 )  for a single port but if it's the only one possibility...
    You are very helpfull ( i don't know if it's a good english but you make me very happy )
    Merci beaucoup

  • Tuxedo Algorithm for remote domain calls

    I have 2 tuxedo domains having similar configurations (advertising same set of services, one on HP & other on Linux). I need to configure both these as remote domains on my local tuxedo domain which will act as a request initiator. Now, I'd like to know how this tuxedo will route any service request to 2 of those remote domains. Is it in round robin fashion or any other ? And do I need to configure it explicitly in the configuration file, if so, then how ?

    Hi,
    This depends upon how you configure the domain gateways.  If you import the services multiple times within the same local domain gateway/local access point, then the domain gateway will round robin the requests.  On the other hand, if you configure two domain gateways, import the services from one remote domain into one of the local domain gateways, and the services from the other remote domain into the other local gateway, then the local balancing will be a little more complicated.  In this case you will have to separate domain gateways each offering the same services.  Normally in this case Tuxedo will place requests on the first empty request queue it finds.  If all request queues are busy, then Tuxedo will select the request queue with the least amount of work queued.  The reason this is a bit more complicated is the way the domain gateway works.  So it has a thread that pulls requests off of it's request queue, so under normal light to moderate load, the domain gateway never has any requests in its queue.  Thus Tuxedo will handle virtually all the requests to the first domain gateway as it will nearly always appear idle.
    My recommendation if these are single machine domains, i.e., SHM mode domains, then just define a single domain gateway and import the services separately from the remote domains.  Additionally I would configure the other remote domain as the fail over domain for each service.  Thus if either remote domain fails, all traffic will end up on the remaining domain.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Forwarding UDP port for Remote Desktop Gateway

    What is the correct way to forward UDP 3391 port for RDG server?
    What direction should I choose for UDP port parameters? "Receive" or "Receive Send" or something else?

    Aurimas N, Were you able to get RemtoteFX working through TMG? I have the same issue whre I can not get UDP working with clients conneciting over the WAN.  Can you tell me specifically how you got this to work on your TMG?
    Thanks
    I am not sure how to check to be honest, on TMG I only see 443 port being used, and since it is remoteApp there is no connection indicator, or I don't know how to access it.

  • How to forward port for remote viewing...?

    Since getting a Time Capsule I have been unable to use my SlingBox remotely. After doing some research I figured out that I have to forward a port...but i have no idea how...or what port to forward.
    Can someone help me out here?

    Use Airport Utility. Click on the Manual Setup button, then click on the Advanced icon in the toolbar. Click on the Port Mapping tab then click on the [+] button to add a new configuration. Use port number 5001 for both TCP and UDP ports in the Public and Private fields. Use the IP address you have assigned to your Airport Express that you've connected to the Slingbox. You will find this all outlined in the Slingbox documentation PDF that came with the device. You can also find it at the Slingmedia website.

  • Forwarding port for remote desktop connection

    I have been able to connect to my home machine from work using remote desktop.  Because of some changes at work I am no longer able to do this on the default port (3389).  So I am trying to use port 5190 (which is used for AIM) or port 5050 (Yahoo messenger).  Both of these ports are enabled from work and I don't use them at home or on the computer I connect from.
    When I changed the port on my home computer, which is connected to a Linksys WRT54G router, I am able to connect when I am on my home LAN using machine_nameort.  But when I try my public IP addressort (which is how I would connect from work) I am not able to connect.  
    I have added a port in the port range forward area of my router.  I have tried 5190 and 5050 and both will not allow me to connect when I am not on my LAN. 
    Any ideas for this?
    RIKIL

    Actually you don't need to press the reset button for 30 seconds...only 5. 
    There are two ways to reset the Router’s
    factory defaults. Either press and hold the Reset
    Button for approximately five seconds, or restore
    the defaults from Administration > Factory
    Defaults in the Router’s web-based utility.
     This is what threw me, I pressed for more than 5 seconds and it wouldn't reset.  I had to hold it for about 20 and that worked.

  • Hyperion Financial Reporting ports for remote access

    Hi,
    May I know what ports should I open if to allow remote access to Hyperion Financial Reporting server to create reports through Hyperion Financial Reporting Studio in home pc?
    Thanks

    Hi,
    You can find a detailed write up on the Hyperion product ports here: http://hyperionism.blogspot.com/2008/11/hyperion-product-ports.html
    This document might be useful to you :- http://www.oracle.com/technetwork/middleware/bi-foundation/epm-component-communications-1112-167817.xls
    You could have also look into SERVERPORTBEGIN and SERVERPORTEND
    http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_tech_ref/frameset.htm?serverportbegin.html
    Hope this helps
    Greetings
    SST.....

  • Firewall ports needed for remote management?

    Hey guys,
    Does anyone know the ports needed so that I can remotely connect to other Win7 computer through compmgmt.msc, regedit, msinfo32, remote rsop.msc, etc?  I think those are just rpc connections, but not sure.  Is it tcp 135?
    Thanks,
    Dan
    Dan Heim

    Hi Dan,
    Based on my research, remote desktop connections are via RDP instead of RPC, so the ports for Remote Desktop to work, 3389 and 443 are used mostly.
    More information for you:
    Overview of Remote Desktop Gateway
    http://technet.microsoft.com/en-us/library/cc731150.aspx
    What ports are used by a RDS deployment?
    http://social.technet.microsoft.com/wiki/contents/articles/16164.what-ports-are-used-by-a-rds-deployment.aspx
    Getting Remote Desktop to
    work thru most firewalls
    http://blog.jordanterrell.com/post/Getting-Remote-Desktop-to-work-thru-most-firewalls.aspx
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    How RPC Works
    http://technet.microsoft.com/en-us/library/cc738291(v=WS.10).aspx
    Best Regards,
    Amy Wang

  • What "ethernet port" does airport utility use for "remote administration"

    I have a friend who was recently evangelized to Macs and bought a Macbook Pro and an Apple Airport Extreme (gigabit) Router, hereinafter called AE. The place where he lives has cable modem internet access and an older Linksys wireless-G router for the building, and I am trying to configure his new AE, prior to making it the primary router in the network (e.g. connected to the cable modem).
    When the AE is completely configured the Linksys will be retired.
    I remotely manage and maintain the network and some other computers in that house. The Linksys is configured for Remote Administration so I can manage it. I manage several PC's and Macs using Timbuktu Pro 8, with the necessary ports forwarded through to TB2 on those machines.
    I am trying to configure the Airport so it also can be managed remotely, so from a workstation on that network (accessed from where I am using TB2) and running Airport Utility, I have checked "Allow setup over WAN" on the Airport/BaseStation page. Now I would like to test whether I can connect and remotely administer that Airport Extreme from Airport Utility on my Mac.
    I assume that, if I can rout packets from my Airport Utility here through the internet to the public IP of the Linksys router there, I should be able to connect. But I can't.
    My setup is this. The target AE has its WAN port connected to an ethernet port on the Linksys, as is the LAN in the remote building. Nothing is connected to the AE's ethernet ports at this time. The Linksys is the DHCP server, and the AE has an IP from it, as does all the other ethernet- and wireless-connected computers, printers, etc. The AE's wireless is active and the wireless-connected devices in the building can connect to either its base station or to that of the Linksys. When the Linksys is retired the AE will be the only wireless in the building.
    I attempt to connect in the following way: On my Mac, I run Airport Utility. From the file menu I select "Configure other" and enter the public IP address of the remote Linksys, and give AE's password. There is a long wait
    Reading the Airport wireless device configuration....
    while Airport Utility tried to discover AE, and then
    An error occurred while reading the configuration..... (-6753)
    I suspect that my remote connection problem is due to the fact that the AE is behind the Linksys, and the proper port forwarding is not in place on it to pass the Airport Utility's packets through to the Wan port of the AE. This might be that I have not entered into the Linksys the correct port number to forward on to the AE. I've tried the three numbers in the list:
    "Well known TCP and UDP ports used by Apple software products" found at
    http://support.apple.com/kb/ts1629
    that are mentioned as possibly being involved with Airport Utility; 192, 4500 and 5009.
    Advice will be appreciated.
    Bob

    One example, and there may be others, is the (free) DynDNS dynamic DNS service which publishes a domain name for the WAN port of your router which can then be resolved, like all other domain names, to the actual IP address of the WAn port of your router. This service provides a solution to the problem of having a proper domain name in cases where your public IP address changes over time. Unless you pay for a static IP address, virtually all ISPs change your public IP address over time.
    So, you can register for a free DynDNS account at www.dyndns.com and that is how you come up with the User: and Password: information; use whatever User and Password you register at dyndns.com with.
    The first part of the hostname you can define as you wish, subject only to someone else having used it previously, and the remaining parts of the domain name might be "dyndns.org" or one of the other domain names provided by the DynDNS service. So, you could publish, via DynDNS, the name of your public IP address as, for example, joehlam.dyndns.org however you might want something less descriptive or more vague.

  • AD account logging to a remote domain controller for authentication

    Hi,
    I have a weird issue with an AD account using a different logonserver when authenticating to AD.  A domain admin account uses the local site domain controller but another account is using a remote domain controller as logonserver. I'm using both account
    to logon to the same server (CRM 2011). But when I issue the command "set l' from the command line, they shows different logonserver value. 
    My issue is the crm account is pointing to a remote domain controller (windows 2012 R2) which I don't want and should use the local site domain controller (windows 2008 R2). The reason being is that the CRM server is on a  test network (isolated) and
    when we test an upgrade of CRM addon product called Experlogix, the upgrade requires to get authenticated by AD but it fails and I think the logonserver is the issue. When the crm account is used on the test server it points not to the local site domain controller
    but to the remote dc which is not in the test server.
    Thanks for your help!!!
    AA

    Start by checking that your are sites and subnets are well configured.
    Use dssite.msc and make sure that:
    You have AD sites that represent your physical sites
    All the subnets in use are created and moved to the correct AD site
    Your DCs belong to the correct AD site
    You can read more about the DC Locator process here: http://social.technet.microsoft.com/wiki/contents/articles/24457.how-domain-controllers-are-located-in-windows.aspx
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • What port does WRT1900Ac listen on for remote admin

    good morning,
    I have had a few problems with linksys smart wifi (periodically cannot connect).
    traditionally I run dynDNS so I can connect to devices remotely (using port forwarding) and this works fine for me.
    what port does the linksys router itself listen on for remote router admin requests (i.e http://publicipaddress:whatport) 
    also, is this configurable?
    thanks
    Dan

    danielgwalter wrote:
    good morning,
    I have had a few problems with linksys smart wifi (periodically cannot connect).
    traditionally I run dynDNS so I can connect to devices remotely (using port forwarding) and this works fine for me.
    what port does the linksys router itself listen on for remote router admin requests (i.e http://publicipaddress:whatport) 
    also, is this configurable?
    thanks
    Dan
    You have to use a Smart Wifi account for remote administration on the WRT1900AC
    Please remember to Kudo those that help you.
    Linksys
    Communities Technical Support

  • How to make a route for sub domains with same IP but another Port

    Hello , 
    I have Windows Server 2008 R2 Domain Controller . the IP address is 172.16.0.200 and the Domain is ( BTC.local ) . I have software login page ( localhost:6090 ) the port of service is 6090 . and if i want to access this page from another PC then i write
    ( 172.16.0.200:6090 ) . My question is how i can change the IP address and the port to sub domain like ( IQ.BTC.local ) so that i can access from another PC by writing the sub domain . 

    > question is how i can change the IP address and the port to sub domain
    > like ( IQ.BTC.local ) so that i can access from another PC by writing
    > the sub domain .
    Create CName records in your subdomains DNS servers.
    Greetings/Grüße,
    Martin
    Mal ein
    gutes Buch über GPOs lesen?
    Good or bad GPOs? - my blog…
    And if IT bothers me -
    coke bottle design refreshment (-:

  • DNS/LDAP Issue for Trusted Domain

    Hi
    I'm trying to configure  Configuration Manager 2012 R2 Forest Discovery to a trusted domain.
    Objects from the trusted domain (users/computers) show up in the Collections, but when I check under Administration\Active Directory Forests I can see Discovery Status "Failed to connect using default account" and Publishing status "Cannot
    Contact LDAP Server".
    I've added the SCCM server to local admin at the trusted domain via GPO and have also created the system Management container.
    When I check the log ADForestDisc.log I get this error message:
    "Failed to connect to forest X. This can be because of disjoint DNS namespaces, network connectivity or server availibility issue. Error Information The specified forest does not exist or cannot be contacted."
    I have setup Conditional Forwarders in DNS in both domains.
    I have also read other forums about this issue and should have the answer:
    "This error occurs for all of the domains that you mentioned and is typical when SRV records for DCs in those remote domains cannot be found. Forest discovery relies on DNS name resolution of SRV records to locate a suitable DC to communicate with."
    "The site server performing the forest discovery must be able to resolve the SRV records for the DCs or root domain of the other forest."
    We are using Windows AD integrated DNS in both domains.
    I'm not so familiar with DNS configuration so I appreciate if someone could tell more specific how to fix this.
    Thanks in advance

    Hi
    Thank you for your answer. This issue is solved. I've missed to open some ports in the router/firewall between the LANs.
    The status under Active Directory Forests is Succeded now, but when I check under boundaries, I can only see the "Default-First-Site-Name" site for the first domain (same LAN as CM Server) and I can only see the IP address range for that LAN.
    I don't Think  this is a big issue, but shouldn't the site name and address range for the other LAN (where the trusted domain is) be automatically found to during forest Discovery when I've checked the options to create site and ip boundaries automatically?

  • Do I need to open ports for my services if I am connecting through VPN

    Hi,
    I work in a small office and we are trying to connect people remotely to our server through VPN.
    Using the Server App I managed to make VPN work and successfully connected to our file share points, so that means file sharing worked without opening ports for afp on my Airport router.
    On the other side I cant connect to other services as iCal and Address Book as I am locally in the office. Does that mean I have to open the ports for those services on the router, if yes then why use VPN in the first place.
    Thanks,

    If I understood you correctly:
    External client -> (server.domain.name) -> Router -> Server: is working
    Internal client -> (server.domain.name) -> Router -> Server: is not working
    Internal client -> (local ip) -> Server: is working
    If yes, you can implement a-la "split zone DNS".
    1. On the external DNS your domain name server.domain.name resolved to the external router IP.
    2. You should add record (and zone) server.domain.name to your OS X Lion Server DNS pointing to local IP
    When you are connected to VPN, system sets DNS server to your Lion server and server.domain.name is resolving to local IP.
    When you are working without VPN, system use external DNS and server.domain.name is resolving to external IP.
    Of course, you should open ports for your services on the router is you want to use them from external network.
    I am using this configuration and it works perfectly.

  • Methods for Remote Event Log Collection (WMI vs RPC vs WinRM)

    Hi,
    I'm currently evaluating several 3rd party tools (SIEMs) to help me with log management in a large (mostly) Windows domain environment. Each tool uses a different approach to collecting the event log from remote systems, and I'd like help understanding the
    pros and cons of each approach. I've dropped this in the scripting forum as the tools are essentially running different scripts and it's this part I would like to understand.
    WMI: An agent installed on a windows server connects to each monitored box and grabs their event logs via WMI. Our legacy SIEM already collects from over 2000 servers using this method.
    RPC: As above, but using RPC. No changes required on the remote machines.
    WinRM: An appliance integrates with AD and collects event logs remotely using WinRM. This is reasonably new to me (i'm a security guy, not a sys admin) but I seem to have to enable an additional remote management tool, and open a new listening port on every
    single machine I want to collect the event log from.
    I read the following blog entry, which seemed to indicate that RPC was the best choice for performance, considering I'm going to be making high frequency connections to over 2000 targets:
    http://blogs.technet.com/b/josebda/archive/2010/04/02/comparing-rpc-wmi-and-winrm-for-remote-server-management-with-powershell-v2.aspx 
    However, everything I have found on the subject of remote event collection seems to suggest that WinRM is the "approved" method for event log collection. The vendor using the WinRM approach is also suggesting that it is the only official MS supported
    way of doing this.
    So I would like to ask, is there a reason that WMI and RPC should not be used for this purpose, since they clearly work and don't require any changes to my environment? Is there some advantage to WinRM that justifies touching my entire estate and opening
    an additional port (increasing my attack surface)?
    Thanks in advance,

    Hi,
    I'm aware of the push method, and may indeed move to it in time, although I'm just as likely to install a 3rd party agent on the machines to perform this role with greater functionality and manageability for the same effort. I've only seen organisations
    using commercial agents (snare, splunk, etc) or WMI for log collection in practice, so I don't think I'm the only one with reservations about it.
    Anything that involves making configuration changes to a large and very varied estate is not something to do lightly. Particularly if alternatives exist that don't require this change to be carried out immediately. That is why I'm looking to properly understand
    the pros and cons of these "legacy" approaches for use as an interim solution if nothing more.
    Pulling probably is more resource intensive, although I've not seen an actual comparison, but it's not really that fragile in my experience. If a single pull fails, you just collect the logs you missed at the next pull cycle in a few seconds/minutes.
    All logs are pulled directly into a SIEM for analysis, so that part is covered.
    Anyway, I appreciate the input, but I'm still holding out for concrete reasons to move away from WMI/RPC or to embrace WinRM. Bear in mind I'm considering fixing something that doesn't look broken to me!
    Cheers,

Maybe you are looking for