Re: Solution to an unusual RWW problem
- From: "Maxibo" <totallyanon@xxxxxxxxx>
- Date: Wed, 21 Dec 2005 09:36:51 -0000
Hi Owen, Many thanks for your post.
I too can vouch for the problems with Linksys.... TWO different models at
different clients causing no-end of probs, site works then doesn't, SMTP
mail was the biggest problem very intermittent.
Googling found many probs relating to firmware and the biggest seemed going
backwards to older firmware was solutions.
I am not using Linksys any more Draytek Vigor were introduced and no
problems since.
"Owen Williams" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1e12a4335667f41e9896d4@xxxxxxxxxxxxxxxxxxxxx
> This is a FYI post. I am documenting an unusual (to me at least!)
> situation and its resolution so that it might help someone else with
> similar issues. My apologies if this information is already well known.
>
> CONFIGURATION: Installed a new SBS2003 SP1 Premium with the following 2-
> NIC network configuration:
>
> [Verizon Business DSL (dynamic IP)] =>
> [Westell 6100 in bridge mode; 192.168.1.1/24] =>
> [LinkSys BEFSX41; Ext=DHCP, Int=192.168.2.1/24;
> DHCP server start=192.168.2.100] =>
> [Ext SBS NIC; 192.168.2.2/24 (static)] =>
> [SBS2003 Prem SP1] =>
> [Int SBS NIC; 10.0.0.1/24 (static);
> DHCP server start=10.0.0.10] =>
> [Ethernet Switch] =>
> [Workstations]
>
> ISA 2004 was *not* installed; the RRAS firewall was configured with
> CEICW.
>
> PROBLEM: Remote Web Workplace worked fine from within the LAN but would
> not work from the Internet. I could get the initial RWW logon page, but
> after entering credentials the page would time-out.
>
> DIAGNOSTICS: Port scans (using www.grc.com ShieldsUp) for 25, 443, 444,
> and 4125 indicated port forwarding at the router and RRAS firewall was
> working. Ports 25, 443, and 444 showed OPEN. I could TELNET to 25,
> 443, and 444 from the Internet and inbound e-mail worked fine. Port
> 4125 showed CLOSED with an unknown application, which is the expected
> state with RWW. TELNET to 4125 returned "Could not open connection to
> the host, on port 4125: Connect failed." I used Jim Harrison's
> WinsockTool (download from http://isatools.org) to temporarily establish
> a port 4125 listener on the external NIC, and the port scan changed to
> report the port was OPEN.
>
> I tried the usual stuff:
>
> * Rerun the CEICW, including turning off the RRAS firewall, then turning
> it back on.
> * Manually re-entering the port forwarding on the router.
> * Just for grins, enabling UPnP and letting CEICW configure the router.
>
> Bottom line, everything *looked* OK, but RWW would not work from the
> Internet.
>
> THE SOLUTION: I have a LinkSys BEFSX41 at another client which has been
> working flawlessly for almost 2 years. However, it was still using
> older firmware. There have been many reports that the most recent
> supported firmware, v1.50.18, is buggy. The newer BEFSX41 was using
> that.
>
> So, notwithstanding the fact that everything SEEMED to be OK, I
> configured one of my old test routers - a trusty NetGear, circa 2001
> vintage - and installed it in place of the LinkSys. Voila, RWW worked
> like a champ. So the problem had to be the router.
>
> I then:
>
> * Reset the BEFSX41 back to factory defaults.
> * Downgraded the firmware to v.1.45.7, a version considered stable.
> * Redid the router configuration for this client's network.
> * Put the BEFSX41 back in service.
>
> Victory: RWW continued to work!
>
> Hope this might help out some other poor soul who is tearing out his/her
> hair. You are NOT going crazy!
>
> -- Owen Williams
> ClearView Technology Consulting, LLC
.
- References:
- FYI: Solution to an unusual RWW problem
- From: Owen Williams
- FYI: Solution to an unusual RWW problem
- Prev by Date: Re: Problems pasting files onto new server shared folder
- Next by Date: RE: VBScript: Remote Desktop Disconnected
- Previous by thread: FYI: Solution to an unusual RWW problem
- Next by thread: Re: Upgrading SQL instances to 2005
- Index(es):
Relevant Pages
|
