Remote Desktop Web Connection ActiveX

I need to have this installed on my iPad but did not see it in the app's store. Without this I can't access my work pc. Any suggestions?

Look into logmein it's much easier than rdp as do not have to configure ports for each user
and once it's installed on your pc or mac it is accessable via any pc plus it has an iPhone/iPod/ipad app
called logmein ignition that will solve your problem, if you have multiple users with a remote access need
I would (already have) create a master or admin account then add your users pc or mac under that account
then each user that is in need to remote in can be either invited by the admin acount or given access permission from the admin account that way you have access control but as far as needing to remote in via remote desktop in my opinion and I administer over 300 users over 5 companies the logmein is the way to go in fact I am patiently awaiting my 3g ipad so that I can remote in from anywhere and everywhere hope this helps here's a web address
http://www.logmein.com
not sure if it's possible for you to email users but if it is shoot me a line if you have any questions and I will be more than happy to help out
Robthecomputerguy [email protected]

Similar Messages

  • WRT54GL not allowing Remote Desktop Web Connection

    Im currently using a WRT54GL in a network with just two computer. Computer A is using a wired connection and Computer B is wireless with a Linksys adapter. Public IP address from ISP is a static IP address and all is setup in the router allowing both computers internet access with no problems. Both computers are setup with static IP. Computer A is 192.168.1.101. Computer B is 192.168.1.103. Both computers are installed with Internet Information Services.
    1) Setting Up The Two Computers: I setup Computer A for port 50001, ie. I opened Control Panel, clicked Performance & Maint., Clicked Admin Tools, Double clicked IIS. Expanded Websites, right clicked Default Website and clicked on Properties. On the Website tab, I changed the value of the TCP port to the one above, 50001. I Opened the Properties Window of My Computer and clicked to the Remote tab. I placed a green Check into where it states, [Allow users to connect remotely to this computer]. On side note, I have admin rights to the computer so I  did not click to [Select Remote Users]. I then accessed the Windows Firewall Settings, In the Exception Tab, I have Remote Desktop with a Check - Set with TCP 3389. I also added new port - game it Name: Remote Access, Port:50001. Settings were all saved. (I did all the same exact steps for Computer B, but the only difference is I used for 50002 instead)
    2) Setting up the router: I access the router configuration with IP 192.168.1.1 Clicked to the Applications and Gaming. Selected [Port Range Forward]. Below where it tells to enter the ports and name for each port I entered for the first port. Application: FM-HS01, Start and End Ports: 50001 to 50001, Protocol: TCP, IP Address: 192.168.1.101, Enabled: {checked}. I again setup another below that for Computer B. FM-HS02, 50002 to 50002, TCP, 192.168.1.103, Enabled: {Checked}. I then clicked to Port Triggering screen. Under Application: [Remote Access], Trigger Range Start - End: [50001 to 50002], Forwarded Range Start - End: [3389 to 3389], Enabled [Checked]
    Under the Security Tab for Firewall - I unchecked {Block Anonymous Internet Requests}, but have {Filter Multicast}, {Filter Internet NAT Redirection} , {Filter IDENT(Port 113)} all checked.
    I also enabled remote access to router using default port 8080.
    By using the ISP Static IP: ie http://64.193.93.46:8080/, I am able to access the router config page no problems. Problem is trying to access each Computer A and B. For Example: in IE address bar, I entered http://64.193.93.46:50001/ I get page stating Under Construction. Now if I try http://64.193.93.46:50001/tsweb/ I actually get the Microsoft Windows Remote Desktop Web Connection screen stating to enter Server __________ Size: and Connection Button. I enter the Computer Name for Computer A: FM-HS01, Choose the appropriate size and clicked connect. Page loads then all I see is an outline of a box where I assume the remote computer's screen should show. A message appears after trying to load stating: "
    Remote Desktop can’t find the computer “FM-HS01”. This might mean that “FM-HS01” does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
    This is where I have been ending up at. I have not able to get pass this part. Any Help Please??? I am not sure is there are other ports I would need to open along with the ones I have specified above. On another side note, my Antivirus software for both computers are CA eTrust AntiVirus which I have also configured for both computers.

    Just change the ports to what ever you think of and be sure to make the right single port forwards (if you put comp A to 50001, make *.*.*.101:50001 forward and so on). Just be sure you are not running anything else on the same port, on the same computer (for excample the IIS terminal server client application). And from outside you just connect the remote desktop client to your external iport_number ie use the comp_ip:50001 for comp A in the client program connection window (not http:// in browser).
    - who stole my beer? -

  • Minimum services to run remote desktop web connection?

    While I recognize that installing anything to do with terminal services or RDS on a domain controller is not recommended it is my only choice for a very small business that I'm helping out. They have Server 2008 R2 and all they want to be able to do is
    have a couple of people remote in to their own computers when out of the office. What services are the simplest way to accomplish this? I can't find an answer to something this minimalist anywhere.

    Hi Jim,
    For your issue regarding double prompt, suggest you to enable RD Web SSO for your case; where we need to enter username and password once. In order for Web SSO to work:
    a. The connection in RemoteApp and Desktop Connections must have an ID. By default, it is set to the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of
    the RD Web Access server.
    b. RemoteApp programs must be digitally signed using a Server Authentication certificate [Secure Sockets Layer (SSL) certificate]. 
    c. Client operating systems must trust the certificate with which the RemoteApp programs are signed.
    You can refer the following article for information.
    Introducing Web Single Sign-On for RemoteApp and Desktop Connections
    http://blogs.msdn.com/b/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
    In regards to your error, we need to have required port open to make successful connection. Need to bind port 443 for RD Web and RD Gateway successful connection. Also need to have proper certificate.
    Addition something might have happened to your IIS settings and more specifically to your Default Application pool. For example if you install some third-party web application, it may have changed the 32/64 bit feature on your Application pool. So please check
    below points.
    1) Go to IIS -> Application Pools -> DefaultAppPool -> Advanced Settings -> Enalbe 32-Bit Application - > if it's True , change it to False
    2) Check other relevant application pools for the same setting - > SBS Web Workplace AppPool or SBS Web Applications application pool
    All of the pools should run with Enable 32-Bit - False
    More information.
    This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable
    https://support.microsoft.com/en-us/kb/969743
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].

  • Windows 8.1 pro Remote App crashes connecting to 2012 Remote Desktop Web Access published application

    Using 2012 Remote Desktop Web access to gain access to published applications. The workstation was a Windows 8.1 (home) upgraded to Windows 8.1 Pro with the Media Center add on. Launching the url to the login page for the RDW works fine. When the app is
    clicked on to launch the Remote App crashes. How do I get it to properly connect. Other Windows 8.1 pro workstations work. Although none were upgraded from the 8.1 (home) Here is the event.
    Faulting application name: mstsc.exe, version: 6.3.9600.16384, time stamp: 0x5215e2b5
    Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x530895af
    Exception code: 0xc0000005
    Fault offset: 0x0000000000065e8e
    Faulting process id: 0xab4
    Faulting application start time: 0x01cf5f2ed029e83f
    Faulting application path: C:\Windows\System32\mstsc.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 21a471d6-cb22-11e3-8263-a0886933dd25
    Faulting package full name:
    Faulting package-relative application ID:

    More info.
    The computer is brand new HP.
    Windows 8.1 pro with media center
    processor Intel i7-4700mq - 12gig ram -64bit
    Full windows touch support with 10 touch points 
    The computer is connecting to a 2012 Server hosted on Microsoft's Azure platform. Trying to access applications hosted by this server with Remote Desktop Web services. The computer can RDP using just the mstsc.exe to other computers and to the server with
    no problem.
    The computer presents the following msg box  Body: Remote Desktop Connection has stopped working. I have tried the following to resolve this and narrow the scope:
    -Created a new user account for the computer with admin rights, rebooted and logged in as the new user.
    -Tried a different user account for the portal, that does work. The user does not show up as connected.
    -All MS updates were loaded.
    -Added these changes to the registry to keep alive the connection: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Gateway\Transports\Rpc-----HttpKeepAliveTimeout=dword:00000001
    And HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client----RDGClientTransport=dword:00000001
    Loaded this update http://support.microsoft.com/kb/2919394/EN-US
    -Removed all printers
    -Removed Antivirus
    -Added the server to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default
    -Disabled everything in MSCONFIG startup
    -Ran sfc /scannow as administrator - no integrity violations
    Any suggestions?

  • Audio Redirection and Remote Desktop Web Access

    I recently deployed a 2012r2 Remote Desktop solution. I have a collection published for remote desktop sessions and have configured it to allow all redirection shown in the interface. However when users connect through Web Access, they do not get audio recording
    redirection.
    Is there a way to enable this through Remote Desktop Web Access?

    Hi,
    Glad to hear that it is up now. Please keep us informed when the issue is resolved.
    Best Regards.
    Jeremy Wu
    TechNet Community Support

  • Using remote desktop web access (RDWEB) with remoteapps and a traditional remote desktop

    I configured windows 2012 r2 remote desktop services and remote desktop web access (rdweb) and was able to click the icon on the rdweb page to log on to a remote desktop session. When I published a remoteapp program, the remote desktop icon went away. How
    do I get it back? Do I need to publish remote desktop as a remoteapp so users can both use remote apps and log on to a traditional remote desktop session?
    thanks in advance for the help

    Hi,
    You can just publish RDC as RemoteApp and then can connect to the desired remote desktop connection. You can check the below snap.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Windows 2008 R2 + Remote Desktop Web Access + Single Sign-On + 2 servers

    Hi
    First sorry for my English. I have got problem with run SSO with RDWeb. I configured everything follow this instructions:  http://blogs.msdn.com/b/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
    and http://blogs.technet.com/b/mrsnrub/archive/2010/03/22/remote-desktop-services-websso.aspx. After logon to RDWeb web page I click application icon. Then I see dialog box for credentials - SSO not working.
    I have got 2 servers with Windows Server 2008 R2 Standard:
    Server OL-AP1 with role Remote Desktop Session Host (RDSH) and certificate for digital sign RemoteApps
    Server OL-AP04 with ONLY Remote Desktop Web Access (RD Web) with certificate for https
    Client PC: Windows 7 SP1 with installing certificate for OL-AP01 witch I used for digital sign RemoteApps
    All certificates created by enterprise domain CA - Active Directory Certificate Services (AD CS)

    Hi,
    Thank you for posting in Windows Server Forum.
    Do you have RD Gateway setup in your environment?
    Have you configure RD Connection Broker and set the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server. 
    Client operating systems must trust the certificate with which the RemoteApp programs are signed. Suggest to install RDP 8.1 for client OS.
    Do you have a trusted certificate with a matching name configured on your RDSH server in RD Session Host Configuration? (Means cert must match the name that clients use to connect to it for running the RemoteApp).
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Remote Desktop Web Access Administration not in menu

    I am trying to figure out why RemoteApp is working and Remote Desktop connection isn't on my very simple installation. One thing I came across is that something seems to be missing from my Remote Desktop Services menu. According to the TechNet article at https://technet.microsoft.com/en-us/library/ee891009(WS.10).aspx
    if I should be able to access RD Web administration by following these instructions: 
    On the RD Web Access server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Administration.
    But when I go there I find that there is no Remote Desktop Web Access Administration. Any ideas on why it doesn't exist?

    Yes, that's the OS I'm using. Those settings are set properly as far as I know. Since this is all on one server, the DC (very small office that can't justify second server), I'm not using an RD Connection Broker so it's set to the RemoteApp sources and
    the Source name is the internal FQDN of the server. servername.domain.local. The weird thing is that when I log in via RD Web the RemoteApps Programs tab has a Remote Desktop icon that successfully connects me to the server but the Remote Desktop tab always
    fails, telling me it can't connect to the computer.

  • Can I use Apple Remote desktop to connect over the internet?

    I would like to use Apple Remote Desktop to connect back to my MacPro desktop at home while I am on my Macbook Air at work.  Will I need a static IP from my service provider to do it.

    Hi
    It's not absolutely necessary but it would be more useful if you did have one. Most ISPs will require you to have a business class broadband service at your home rather than a residential one. These cost more (a lot more in some cases) than a residential service. Call your home location's ISP and discuss it with them.
    If the cost is too much then you could go for a DynDNS account which is free. The details of this account would be configured in the whatever you're using as a firewall at your home's location. This assumes the firewall has the facility to add such an account. Thereafter it's just a question of configuring the port fowarding feature of that firewall.
    A potentially 'big' problem though is whether or not your workplace will allow that kind of traffic out of their network. This would be something you'd need to discuss with them first.
    HTH?
    Tony

  • Hi there , i use microsoft remote desktop to connect to my work pc - on my 21.5 mac the remote screen is half the size of my screen and i cant get it to be full screen - is this possible or am i just stupid ? many thanks

    Hi there , i use microsoft remote desktop to connect to my work pc - on my 21.5 mac the remote screen is half the size of my screen and i cant get it to be full screen - is this possible or am i just stupid ? many thanks

    What setting have you chosen in the view menu? Fit to Screen or Window.
    And, in Preferences what have you set for Display?

  • Apple Remote Desktop not connecting to O2 Wireless Box

    I've successfully got Apple Remote Desktop to connect to, view and control various Macs connected to numerous routers.
    But the O2 Wireless Box doesn't want to play ball and I simply can't figure out why it won't allow me to connect.
    Using http://portforward.com/english/routers/port_forwarding/O2/O2-TG585v7/Apple_Remot e_Desktop.htm as a guide (this was the only O2 router it referred to), I'm forwarding ports 3283, 5900 & 5988 but I simply can't connect using Apple Remote Desktop via the Internet.  It just sticks on 'Connecting...' and then goes to a failed message.  It suggested that, perhaps, Remote Desktop isn't enabled on the other machine ... but it is.
    It seems to be something very odd about the router (it doesn't even allow remote management of the router as O2 removed that functionality fearing it was 'too dangerous' to allow the end user access to this) and I'm wondering whether there's something else I need to do to make the connection.
    Can anyone give me as guidance on this please?  It's driving me crazy!

    Hi Jason,
    It is often difficult to explain a problem, so don't worry. Let's break it down.
    Firstly, does ARD work when you are at your place of work? - can you control a mac?
    If so, this is good.
    Ok, from work you need to access your router and find your public IP address, you only have one. You will often find this is the status page.
    The IP is usually a class A address starting with 80 or 90, but this obviously isn't always so, depending on your ISP and region. make sure you are not using the router's local lan IP! You will also need to make sure your home router is allowing ARD ports through!
    You now need to port forward the ARD ports to the mac you want to control, which I believe you have done. For example, port 3283 > IP address of remote mac.
    I know when I did this, I just opened up all ports for a couple of minutes just to get it working, then I locked access down. If you havn't done so then you need to enable remote management on your work router so you can configure it at home.
    On your mac at 'home' open ARD, and go to file> add by address and enter the PUBLIC IP address. You will also need to enter the admin user name and password for the said mac.
    That's it, you should have control.
    If your macs at work and home have a firewall enabled then you will need to update your rules.
    Good luck!

  • MBA CAN'T GET ON MS REMOTE DESKTOP DUE TO ACTIVEX

    I typically used my Toshiba to access my office through MS Remote Desktop. I have upgraded to a MBA (after many years of suggestions from my children) but find that when I try to access my computer at work I get the message " This portion of Remote Web Workplace requires the Microsoft Remote Desktop ActiveX control. Your Browser's security setting may be preventing you from downloading ActiveX controls. Adjust these settings, and try to connect again."
    I find no settings to adjust on Safari re ActiveX controls. Hence, trying again did not help. Obviously, I am missing something. Can anyone assist in allowing me to access my PC at work from the MBA?

    I don't know about your work setup, but you might be able to use Microsoft's RDC http://www.microsoft.com/mac/products/remote-desktop/default.mspx.

  • My printers works fine on my home network but disappears on a remote desktop terminal connection

    As I don't really know how to post a general addition to the knowledge base, I'm doing in Jeopardy style.  Here is the question to the above answer.  Well close enough.
    Many people have reported all over the net issues with printers working just fine on their home network  but disappearing when they connect to a server via RDT.  There are some legit updates needed where windows did not see anything but LPT and COM ports for printer re-direction assignment.  There are Mr. Fix it's for those and registry patches.  When all of that fails, the information highway seems to dead end.
    Here is what I learned today via 2 specific printers:  HP1022 and HP2840 lasjerjets.
    After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others.  This problem as far as I have come across deals exclusively with HP printers.  In simple terms:  the drivers are flawed.  This 1022 is a prime example.  It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder.  Enter a remote desktop session and ALL of them populate except the 1022.  This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers.  All except the 1022. 
      Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver.  I used a 1200 PCL driver.  Now log back into your RDT server and hockus pocus! there is your printer.  Totally un-usable because the driver will not run this printer.  Caveat:  each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
    Moving on we go to the HP OfficeJet/LajerJet2840.  Same thing.  It won't pass through as remote printer in RDT.  Go local.  Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
    While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
    Hey HP?  Whats with the drivers??
    Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing.  You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

    As I don't really know how to post a general addition to the knowledge base, I'm doing in Jeopardy style.  Here is the question to the above answer.  Well close enough.
    Many people have reported all over the net issues with printers working just fine on their home network  but disappearing when they connect to a server via RDT.  There are some legit updates needed where windows did not see anything but LPT and COM ports for printer re-direction assignment.  There are Mr. Fix it's for those and registry patches.  When all of that fails, the information highway seems to dead end.
    Here is what I learned today via 2 specific printers:  HP1022 and HP2840 lasjerjets.
    After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others.  This problem as far as I have come across deals exclusively with HP printers.  In simple terms:  the drivers are flawed.  This 1022 is a prime example.  It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder.  Enter a remote desktop session and ALL of them populate except the 1022.  This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers.  All except the 1022. 
      Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver.  I used a 1200 PCL driver.  Now log back into your RDT server and hockus pocus! there is your printer.  Totally un-usable because the driver will not run this printer.  Caveat:  each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
    Moving on we go to the HP OfficeJet/LajerJet2840.  Same thing.  It won't pass through as remote printer in RDT.  Go local.  Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
    While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
    Hey HP?  Whats with the drivers??
    Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing.  You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

  • Apple Remote Desktop not connecting

    I have set up new iMac with OSX.8.3 and released the remote administration as I did before on many other devices.
    In the Apple Remote Desktop window I can see the computer and it presents itself as any other computer also, to which I have access to (available, current user etc)
    However, when I try to connect I get in the LAN immediately "connection failed".
    From outside via VPN I get this message:
      Please make sure that the remote administration (in System Preferences "Shares") is enabled on the computer to which you want to connect. Also make sure that your network connection is working correctly.
    Here, after all, is an indication, albeit an improper. I can see the computer in the list of the ARD window and that it is available. But cannot connect either
    I have tried with and without firewall, with no success. In addition, in the firewall the Remote Administration is enabled.
    I am little perplexed. (With TeamViewer I can connect)

    Thanks a lot for your help
    TeenTitan wrote:
    while connect to the local network.
    is the computer on and awake when you try to connect?
    Yes it is
    on the new imac, have you verified remote management is enabled?
    Yes I did (the computer IS visible in the Remote Desktop list, I can see what app is running, which user account is active )
    if no, have you tried enabling it? (apple menu, system preferences, show all, sharing, check remote management)
    its correctly done
    If yes, have you tried unchecking it, and then re-checking it?
    Will try it
    if still no, is the user your try to connect with listed in remote management?
    Yes it is listed (however I checked the option for all user)
    if so, what about deleting and then re-adding the user your try to connect with?
    Will try that
    if no, what about adding the user to the list?
    I was creating already a new user, no improvement
    while connected to the same lan as the imac. Have you tried deleting the computer record for the imac from your ARD, and re-adding the client?
    Will try that
    Is both computers connect to the network the same way? if so, what are the IP address you get on both computers?
    yes they are. We have manual attributed IPs in the same range

  • Remote desktop not connecting

    So basically i have set up a server, created a domain, everything is fine, the server can access the internet, it can see other computers in the network, the computers can see the server. Problem is I want to administrate the server remotely. So i set up
    the remote desktop to allow users to connect remotely. Problem is it only lets me connect from other pc in the same network , I cannot make a connection from an outside network. I am trying many different options but none seem to help.
    I have placed users in the list which allows the remote desktop connection
    I tried disabling the firewall, i added the ports ranging 3387-3390 tcp and udp. Enabled any inbound and outbound rule for remote desktop.
    Tried port forwarding though there are 2 routers on the network so i had access to only one . I forwarded the same ports through the router. And called the internet provider to forward the ports for their router. (They havent dont that as i am writing this
    so that may be the problem but i cant be sure).
    I tried installing teamviewer as an alternative. Problem is when i installed it , it didnt work also. It said there is no internet connection and that i have to check it. Then it tries to connect to the StayAlive server but fails ant tells me that i may
    have a proxy , and i should manually set up its settings , but there is no proxy. So from what i have gathered . I am really at a loss here is there some settings i messed up in the windows server or is this a problem with ports not being open.
    I am having a hard time figuring out where the problem is , as i have tried doing every settings that comes to mind, but it has been a pain in the behind getting remote desktop to work from an outside network.
    Also i do know the outside Ip of the network, i use that to connect to the server but have no luck with that. I am open to any suggestions anyone may have. I will try to provide as much info as possible to help me solve this problem.

    I dont quite understand, problem is that it doesnt even connect to the server it basically times out while trying to connect, at first i thought maybe it was because there are no users with licenses added but the error would be different when connecting,
    also as i have said , i installed teamviewer on the server and it says to check internet connection, though the server can reach the internet. I tried creating the gateway, the wizard just created it . It didnt ask me to add any users. Can the server be somehow
    blocking connections, but not notifying? As there are no logs of connection attempts. It just seems that the server cant be reached from the outside only from inside the local network.
    The computers in the same network can use teamviewer, but the server even though being on the same network cannot. Firewall is turned off, no antivirus firewalls are present, ports have been forwarded through both routers. I cannot seem to find the reason
    to this problem.

Maybe you are looking for