Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Anywhere Access problems

Answered Anywhere Access problems

  • Friday, February 08, 2013 1:35 AM
     
     
    Sign In to Vote
    0
    We have a recently-installed WS 2012 Essentials server and I initially ran the Anywhere Access Wizard to configure remote web access.  It returned the usual two errors (see below) about my router (a Linksys RV082), but afterward I was able to log in remotely using xxxx.remotewebaccess.com from my Phone 8 and home PC.  Something I did recently has broken the configuration (possibly installing .NET 1.1 with a 2007 version of QuickBooks Server).  Now, nothing I have tried has been successful.  I still get the "There may be more than one router on your network" and "Anywhere Access to your server is blocked."  I have tried enabling UPnP on the router as well as configuring it manually, forwarding Ports 80 and 443.  On the client end, I get a "500 - Internal server error." when I open the https://xxxx.remotewebaccess.com/Remote page.  I am at a loss of things to try.  Suggestions?
     

All Replies

  • Friday, February 08, 2013 1:33 PM
     
     
    Sign In to Vote
    0
    This could be a problem.  You *may* need to restore the server from a backup taken before you installed QB 2007 on the server.  Of course, hindsight says to NEVER install the QB app on the server. .Net 1.1 can cause all sorts of problem with SBS 2008 and above. 
     
    I'm going to post the entire text of a thread I found since the originating web site sometimes does not show the 'answers section' if I  post just the link.  The thread talks about the same issue you have.  I would say at this point you need to restore the server from a backup, upgrade to a newer version of QB and then move just the QB company file(s) to a shared folder on the server if you only need single user access to QB.  If you need multiuser access, you should install the QB Server Database Manager on the WS2012E server to set up QB for multiuser access.  There are some other steps (like setting up the WS2012E firewall for QB Server Manager), but first get your server back to operating condition and then we can tackle the QB issues.
     
     
     
    -----------------------------------------------
    QUESTION
     
    I have a newly installed Windows SBS 2011 Essentials server, along with newly installed Workstations with Windows 7 Pro. Everything is working great, with shares, AD...etc. I'm trying to get the workstation backups going and am not successful. I have researched the issue and have tried the fixes recommend but nothing is working. The error I get after entering the login credentials is this:  “Cannot connect this computer to the network. The server is not available. Try connecting this computer again, or for more information, see Troubleshoot computers to the server”
     
    I have tried this solution ( Although the Cert was already selected, I tried changing it to the different ones listed, all with the same results.)
     
     
    Also to note, at first I could not access the site <servername>/connect from any LAN machines, I kept getting an error 500 saying it could not load aspi_filter. I fixed that issue by removing the ..net 4 isapi binding. But since have added it back, both the 32bit abd 64bit and could access the site fine now.
     
    I have attached the latest ClientDeploy Log that has the error info in it. I really would like to get this working ASAP.
     
    More info: Each workstation does have Norton 360 installed, and I have tried disabling the Smart Firewall and it does not affect it.
     

    ANSWERS
     

    by: cgaliher
     
    You are still getting 500 errors from the server. The connect process uses several .net calls behind the cent, so while your isapi changes solved one y,prom, the underlying problem is still there. My first guess is that a 3rd-party app was I stalled on the server that mangled .net. What has been installed?
     

    by: smarin820Posted on 2012-10-05 at 12:21:01ID: 38468480
     
    I did have to install an of version of Quickbooks which installed ..net 1.1 before its installer could continue. Could that be the problem? Would it do any good to reinstall .net 4?
     

    by: cgaliherPosted on 2012-10-05 at 12:26:39ID: 38468505
     
     .net 1.1 will kill an SBS server every time.
     

    You can try reregistering .net, but I make no promises. My experience has been hit-or-miss. You may have to restore a pre-quickbooks backup.  Susan has a good blog post on .net on SBS. While her screenshots reference SBS 2011 Standard, the principles and problems are the same on essentials.
     

    by: smarin820Posted on 2012-10-05 at 13:53:22ID: 38468803
     
     Well I uninstalled QB 2006 as well as .net 1.1 and then reregistered ..net 4, restarted iis and still have the problem. I can't restore any backup as this was a new install and backups did not start until it went into production.
     

    by: smarin820Posted on 2012-10-05 at 14:10:40ID: 38468847
     
     
    I made sure to reregister the framwork64 also and changed the isapi/cgi to allowed and still does not work, with the same error. I guess I'm hosed here.....
    -------------------------------------------------------------------------------
     

    --
    Merv  Porter   [SBS-MVP]
    ============================
     
  • Wednesday, February 13, 2013 2:19 AM
     
     Answered
    Sign In to Vote
    0

    This was of great help.  I got it working again w/o removing the QuickBooks Server (2007 multi-user).  Here's what I did:

    1. Uninstall .NET 1.1 after installing the QB server (it runs fine with WES .NET 2.0 and 3.5).
    2. Open a command prompt with administrator rights and run c:\windows\microsoft.net\framework64\aspnet_regiis -ir
    3. Opened Server Manager and deleted the .NET 2.0 and 4.0 (32-bit) filters under the Default IIS filters

    I tried a few other things between #2 and #3 (like uninstalling/re-installing .NET 3.5) but I don't think it was necessary because it was still broken until I did #3.


    • Marked As Answer by David Baltz Wednesday, February 13, 2013 2:21 AM
    • Edited by David Baltz Wednesday, February 13, 2013 3:58 PM
    •