Prev: Creating a wireless access point
Next: Configuring 802.1X Authentication
From: Joe on 3 Apr 2010 08:18
Update. My internet problem seems to have subsided now, apparently caused by
Symantec's NIS Smart Firewall not being so smart (based on similar NIS
problems of years past). After a few weeks of limiting my ability to connect
(e.g., had to temporarily disable the Smart Firewall), things now seemed to
have returned to normal. I'm guessing that a recent daily update fixed the
problem.

WBEM may have played a part, as I've reconstructed WMI using the WMI
Diagnosis Tool; however, the iNet connectivity problem continued for a while
after my WMI work. More about this under Discussions in Performance &
Maintenance.

-- Joe Davis


"Joe" wrote:

> Hi! I'm having a strange problem connecting to the i-Net. When my modem
> initially indicates connection, I can dial up okay. Then, with a single
> exception, I cannot connect to any site on the i-Net. Exception: If I first
> run Live Update on Norton, then I can access any other web sites with no
> problems, that is until I disconnect from AccessRunner.
> I tried NIS' One-Click Support, which said that my RPC service was turned
> off. In fact, RPC was started & in auto. My RPC Locator ervice, however, is
> disabled. So I started the service & set it to automatic. This had no effect
> on my problem.
> When I clicked the Dependencies tab of the RPC Locator service' Properties
> dialog box, I received the following error message: "WBEM error features not
> available. Upgrade WMI to a newer build."
> Note that the WBEM environment variable is present in the PATH statement.
>
> Any help will be greatly appreciated.
>
> Platform: WXP Pro SP3, IE8, & NIS2009, with all updates; ADSL, Stand-Alone
>
> --
> Joe Davis
First  |  Prev  | 
Pages: 1 2
Prev: Creating a wireless access point
Next: Configuring 802.1X Authentication