This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

After Upgrade to Firefox 20 on a Windows Server 2008 R2 Remote Desktop server, You can't browse with firefox

  • 1 reply
  • 18 have this problem
  • 36 views
  • Last reply by cor-el

more options

After Upgrade to Firefox 20 on a Windows Server 2008 R2 Remote Desktop server, You can't browse with firefox. When you type something to browse, and then press Enter, Nothing happends, Same thing with the search windows.

But Bookmarks and home button works, And also links then you have used the bookmarks to get to a website.

But you can't type a website and then press enter or the -> to get to a webpage after the upgrade.

This is tested now on 4 different servers all with the same problem after the upgrade.

It looks like firefox does not recogninize the Enter button anymore then on Remote Desktop Connection.

After Upgrade to Firefox 20 on a Windows Server 2008 R2 Remote Desktop server, You can't browse with firefox. When you type something to browse, and then press Enter, Nothing happends, Same thing with the search windows. But Bookmarks and home button works, And also links then you have used the bookmarks to get to a website. But you can't type a website and then press enter or the -> to get to a webpage after the upgrade. This is tested now on 4 different servers all with the same problem after the upgrade. It looks like firefox does not recogninize the Enter button anymore then on Remote Desktop Connection.

All Replies (1)

more options

There appears to be a problem with Firefox 20 with UNC paths when using roaming profiles on a server.

This is currently investigated and tracked via this bug report.

(please do not comment in bug reports: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)

Modified by cor-el