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

When connected to LAN, FF can't find servers; no problem with wi-fi

  • 4 replies
  • 8 have this problem
  • 46 views
  • Last reply by FredMcD

more options

Running Firefox 26.0 on a Windows 8.1 system. The thing I run into is this: I have no problem loading pages and surfing when I'm connected to my network wi-fi (I have a dual-function modem that does wireless and LAN simultaneously). However, whenever I plug in the LAN cable, I get the error message that Firefox can't find the server. This happens whether or not I disconnect the wireless in conjunction. BUT, if I continually hit the [Try Again] button, or simply hit the reload icon in the address bar, the page will eventually load, usually after a few attempts. However, the page usually loads only partially at first, seemingly without advanced HTML formatting. But, after I hit reload again a couple times, the page loads normally. Stranger, is that the behavior is not consistent--some pages load fine. But I can't for the life of me figure out a pattern.

I've tried troubleshooting by disabling NoScript, but it doesn't seem to make a difference.  It's almost as if the wait time for a response from the server is so minimal when connected to LAN that the server has no chance of loading the first time.  Does that make any sense?  If so, how can I go about fixing the issue?

Thanks for any help you can offer on this (to me, anyway) head-scratcher.

Running Firefox 26.0 on a Windows 8.1 system. The thing I run into is this: I have no problem loading pages and surfing when I'm connected to my network wi-fi (I have a dual-function modem that does wireless and LAN simultaneously). However, whenever I plug in the LAN cable, I get the error message that Firefox can't find the server. This happens whether or not I disconnect the wireless in conjunction. BUT, if I continually hit the [Try Again] button, or simply hit the reload icon in the address bar, the page will eventually load, usually after a few attempts. However, the page usually loads only partially at first, seemingly without advanced HTML formatting. But, after I hit reload again a couple times, the page loads normally. Stranger, is that the behavior is not consistent--some pages load fine. But I can't for the life of me figure out a pattern. I've tried troubleshooting by disabling NoScript, but it doesn't seem to make a difference. It's almost as if the wait time for a response from the server is so minimal when connected to LAN that the server has no chance of loading the first time. Does that make any sense? If so, how can I go about fixing the issue? Thanks for any help you can offer on this (to me, anyway) head-scratcher.

Chosen solution

Maybe a different DNS server is used or there is still some data cached.

Did you try a hard reload to bypass the cache to refresh all files?

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)

You can also try to toggle Work Offline off/on after changing the network connection.


If is also possible that your firewall treats the Wi-fi connection different than the LAN connection.

Read this answer in context 👍 3

All Replies (4)

more options

Chosen Solution

Maybe a different DNS server is used or there is still some data cached.

Did you try a hard reload to bypass the cache to refresh all files?

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)

You can also try to toggle Work Offline off/on after changing the network connection.


If is also possible that your firewall treats the Wi-fi connection different than the LAN connection.

more options

Does your computer show connected to the hard wire?

more options

Fredmcd: my computer does show connected too the hardwire.

Cor-el: Weird thing: I looked into the firewall thing; turned it off briefly to see if it would make a difference. It did...sites loaded just fine without the firewalll on while on LAN. So then I turned it back on (I couldn't see any way to distinguish between wi-fi and LAN in the firewall options), and the sites are now loading quickly. Somehow, just checking the firewall settings seems to have done the trick. Thanks for your help!

--R

more options

Go back to the firewall and check the settings for ALL programs listed. Make sure that the programs that you want to access the net are ALLOWED.