Mozilla/Firefox Flakiness..?

[Mark Sargent]

Hi All,

I am trying to access a SonicWallPro device from FC3 on a local LAN. 
Device IP = 192.168.168.168. eth1 is set to 192.168.168.12 and Cisco2900 
= 192.168.168.1. Firefox/Mozilla give an error when attempting to 
connect to the web management @ 192.168.168.168, although the device is 
pingable. This is only sometimes, and today is one of those sometimes.

The connection was refused when attempting to connect 192.168.168.168.

Now, if I take the same cable, and attach it to Windows98SE and connect 
via IE, it works. Why would I be getting this error only on FC3.? The 
browsers have no problem connecting to the net via eth0. Cheers.

Mark Sargent.

[Mark Sargent]

Mark Sargent wrote:
> Hi All,
>
> I am trying to access a SonicWallPro device from FC3 on a local LAN. 
> Device IP = 192.168.168.168. eth1 is set to 192.168.168.12 and 
> Cisco2900 = 192.168.168.1. Firefox/Mozilla give an error when 
> attempting to connect to the web management @ 192.168.168.168, 
> although the device is pingable. This is only sometimes, and today is 
> one of those sometimes.
>
> The connection was refused when attempting to connect 192.168.168.168.
>
> Now, if I take the same cable, and attach it to Windows98SE and 
> connect via IE, it works. Why would I be getting this error only on 
> FC3.? The browsers have no problem connecting to the net via eth0. 
> Cheers.
>
> Mark Sargent.

Hi All,

I just re-attached the cable to FC3 from Win98SE, and now it works. What 
would have caused this..? Next time I'll just remove/re-attached the 
cable to see if that was it, but, kinda annoying/weird, huh. Cheers.

Mark Sargent.

[James Wilkinson]

Mark Sargent wrote:
> I am trying to access a SonicWallPro device from FC3 on a local LAN. 
> Device IP = 192.168.168.168. eth1 is set to 192.168.168.12 and Cisco2900 
> = 192.168.168.1. Firefox/Mozilla give an error when attempting to 
> connect to the web management @ 192.168.168.168, although the device is 
> pingable. This is only sometimes, and today is one of those sometimes.
>
> The connection was refused when attempting to connect 192.168.168.168.
>
> Now, if I take the same cable, and attach it to Windows98SE and connect 
> via IE, it works. Why would I be getting this error only on FC3.? The 
> browsers have no problem connecting to the net via eth0. Cheers.

Hmm. It's been my experience that the SonicWall web management has been
flaky. It does vary with the SonicWall firmware, though: since you have
a Win98 machine around, you could try patching it.

On the other hand, I've found that SonicWall make you jump through more
hoops than one might consider necessary to get the firmware: good luck!

James.

[Matt Florido]

On Wed, March 16, 2005 11:05 pm, Mark Sargent said:
[...]
> Now, if I take the same cable, and attach it to Windows98SE and connect
> via IE, it works. Why would I be getting this error only on FC3.? The
> browsers have no problem connecting to the net via eth0. Cheers.
>
> Mark Sargent.

I think this problem is more attributed to SonicWALLism as opposed to
FireFox.  The Pro has been EOL for quite sometime.  I would be surprised
if it's the SonicWALL Java interface that's giving you problems.