using Safari 4 to manage Linksys WRT300n router

try using https login, that solved the problem for me but browser response time slowed down when managing the router.

I had the same issue yesterday while using Safari 4 to manage my Linksys WRT160N router. after seeing this thread I opened Firefox and it worked perfectly.

It would seem, on the surface at least, that Safari may indeed be the culprit here, but that conclusion does not explain why I can successfully configure a Linksys WRT54GS (note the S) router but not a WRT54G router using Safari 4.0.3. Granted, these two routers are on two different networks with two different Macs, but both Macs are the same model running the same version of OS-X and the same version of Safari. Perhaps the router plays a role in this problem as well. I suppose I could take the GS router over to my friend's house and see if I can configure it there (where configuring the G router is failing). If I do, I will post my findings.

Thank you OmniWeb worked in reconfiguring my linksys router WRT300N, safari and firefox failed although I have the latest version of each browser

Hi

Im having the same problem with my Linksys router and Safari 4.0.3, but I'm thinking the problem occurred when I updated my Linksys firmware. Could be wrong about that though.

I see this thread has been marked as solved? What advise solved it?

I was having the same problem and discovered a solution. The problem is "solved" when you use Firefox instead of Safari. It's been literally years now that Safari can't properly display the search box in the upper right corner of this online discussion forum. What's going on? Why isn't Safari more compatible with other products and with Apple's own website?

Someone earlier was quick to say that it was a problem with the connection dropping and that "It's not a problem with Apple." Well, actually it is a problem with Apple and with Safari. I wish Apple could get Safari to be as compatible as Firefox.

same deal here. safari says the connection is dropped. firefox works.
lame sauce, apple. lame sauce

Hi
I had this problem with Safari and Linksys WRT54GL Router too. I accidentally found the solution. It is use "Cancel changes" button to SAVE changes and not "Save Settings" if you work with Safari and Linksys Router WRT54GL.

I tried to add a wireless network to my Linksys WRV200 with Safari 4.04 (OSX 10.6.2) and when I clicked "save settings" the message appeared about the lost connection. This message has nothing to do with the browser, but is caused by a brief loss of connection as the router saves the configuration or worse still, has to go through a reboot cycle. Safari 4.04 apparently cannot recover from this. It could have something to do with the cgi responses to the browser and how they are handled. I don't know cgi, so I can't speak to that intelligently.

I encountered the same phenomenon, when configuring a Linksys WRT54G. If you use IE (6 or 7) the browser actually goes into a wait state, which is part of the cgi script, and then refreshes after enough time has comfortably expired, allowing the router to return to a "normal" state.
This is why we are experiencing problems. I don't have a good solution, except IE on a Windows box, but I will keep trying.

OK, I should have waited a few minutes, but I found a solution, atleast for the Linksys WRV200, I can only assume it works for the WRT54G as well.

Download Camino http://caminobrowser.org/download/releases/2.0.1

It's an opensource browser, not visually as appealing as Safari, but IT WORKS!

If your configuration changes require the router to reboot or go into the wait state, be patient, Camino recovers very well.

On other compatibilty notes, it's a little sluggish with some Java applets, but seems to handle them well. It works with two banking websites that I tried and Blackboard (an educational online classroom environment) which is normally quite persnickety and "requires" IE7, but doesn't like IE8.

After updating to Safari 4.0.5 (on both the Mac and the PC), the problem is now gone. Whatever it was, Apple must have fixed it.