• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1811
  • Last Modified:

RWW connection getting kicked off with error 50331694

Hello,

We have a client with a new SBS 2008 network. We setup one user with Remote Web Workplace (RWW) access. She is getting kicked off of the connection after 30-50 minutes with the following error:

Remote Desktop Disconnected; An internal error has occurred (error 50331694).  For more information, contact your network administrator or Microsoft Product Support.

I can't find any reference to this error on Microsoft's KB, nor Google.

We have already updated the registry on the server to allow for longer timeout settings (we moved it up to 8 hours) as per http://blogs.technet.com/sbs/archive/2009/06/15/how-to-configure-the-rww-timeout.aspx, but she continues to get kicked out. Also, I have been able to connect via RWW and let it sit for at least two hours without getting kicked off, so I am suspicious of either her connection (Bresnan cable broadband) or her computer (a brand-new HP with Windows 7 Professional 64-bit).

Ideas?

Thanks,

Jeff
0
JAStillwell
Asked:
JAStillwell
  • 5
  • 4
1 Solution
 
markdmacCommented:
I'd suspect there is a problem with the user's network connection.  What happens if you first establish a VPN and then use RDP direct instead of RWW?
0
 
JAStillwellAuthor Commented:
Markdmac:

Right now she is setup with only RWW access, so I'd need to reconfigure SBS 2008 to allow her to VPN. I'll try it.

Also, she previously used GoToMyPC with the old computers and, other than a bit of lag, could stay connected for hours.
0
 
markdmacCommented:
I think I would still suspect the Internet connection.  Anything can change and what may have been a stable connection in the past might not be now.  Using a VPN will help you determine that, bypass the IIS dependency in RWW so you can eliminate that as a potential cause.

At both ends I would also make sure that the Power Managment settings in the NICs is set to NOT allow Power Management to shut down the NIC.  By default that is enabled.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
JAStillwellAuthor Commented:
I think the problem is with the specific computer. I had the client connect her old Windows XP Pro computer back on her broadband connection and use RWW to connect in. She was able to connect successfully and stay connected for over 3 hours without getting kicked off. The computer I want her to use is a brand-new Windows 7 Pro 64-bit. I'll check the NIC settings to see if they are timing out, but I'm wondering what else the problem might be. The error 50331694 is odd in that I can't find a reference to it anywhere, and it's a Microsoft error box that is popping up!

Anyway, any additional troubleshooting ideas would be appreciated.
0
 
markdmacCommented:
Isn't there anything in the event logs?
0
 
JAStillwellAuthor Commented:
I haven't checked the event logs, but I was able to login to the computer and poke around a little. I got an 800 error trying to connect via Windows VPN. I verified that a second computer (with XP rather than 7) is able to connect, stay connected via RWW, and successfully connect via VPN/RDP. The one difference I found is that the old computer has Norton on it, and the new computer has AVG. I disabled AVG's firewall to see how the new computer works, and it appears that we can connect and hold a connection via RWW.

So, apparently AVG Internet Security's firewall is a bit too strong to work with RWW and Windows VPN. It's odd that RWW connects and then disconnects with an error after being idle, but shutting off the firewall allows it to stay connected. Any advice on turning the firewall back on and opening a couple ports? How about switching back to Windows Firewall and disabling AVG's firewall?
0
 
markdmacCommented:
If this is SBS 2003 then you need to open port 4125 on the firewall.  There is also a setting on the VPN to disconnect when idle aft x minutes.  I always set that to NEVER.
0
 
JAStillwellAuthor Commented:
As mentioned in the OP, it's SBS 2008. I have adjusted the built-in timeouts to 8 hours. The error is not a "you've been logged out", but an internal error.

I set her up to connect via VPN and RDP. Similar problem where the VPN connection is disconnecting after it's idle for 30 min to a couple hours. Her old computer doesn't have the same problem, so I need to get into the Windows 7 NIC settings and see if there is a problem there, or what the event log shows on the specific computer. I don't think the server is noticing anything in particular about the connection, so I think it's limited to the specific Windows 7 remote computer.
0
 
JAStillwellAuthor Commented:
After swapping out network cables and switch ports, it appears that the disconnect issue might be resolved. It looks like the suggestion that the 'network connection' is the problem is correct.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now