Re: Linksys WRT54G and Linksys BEFSR41 (Two Router setup)

I tried your fix below, but still same symptom. It shows now another error
afetr starting up: my Norton Antivirus 2003 comes up with a dialog box.
Although I have TCP/IP installed it gives me an error:

"Symantec Email Proxy" TCP/IP is not installed 1003.3
Any idea what has happened ?



"Duane Arnold" <(E-Mail Removed)> wrote in message
news:Xns93BF1C3246F2Bnotmenotmecom@204.127.204.17. ..
> "Michael Grigat" <(E-Mail Removed)> wrote in
> news:j7JSa.267096$_(E-Mail Removed) .com:
>
> > I have the following setup:
> > internet -> cablemodem -> BEFSR41 router (DHCP enabled, address
> > 192.168.1.1, newest firmware) ->Linksys Powerline bridge 10/100
> > another room: Linksys Powerline bridge 10/100 -> WRT54G Router (newest
> > firmware, address set to 192.168.1.254, DHCP disabled, setup as router
> > not as gateway) connected to three office computer (Win XP Pro) by
> > hardwire, one laptop (Win 2000) by wireless connection.
> > I had a hard time to get above setup working. I thought everything
> > worked fine. All computers communicated at the end and were able to
> > connect to the internet. Tonight I rebooted one of my computers that
> > worked before in this setup and now it cannot find the internet
> > anymore. Somehow I feel that something is wrong with the DHCP
> > function. The IP address was 169.254.151.208. The DHCP server should
> > have issued an address above 192.168.1.100, which is also shown by the
> > release table that I can still see with another computer.
> > Any clue what went wrong? I am out of answers. I tried to manually
> > adjust the IP address on computer in question to 192.168.1.100 and
> > point to the router one, which did not help either. Either router can
> > not be accessed by IExplorer after typing the address of either
> > router. I must overlook some setting. One of my computer is currently
> > accessing the internet and I can also open both router configurations.
> > It seems that I am unable to regain connection in a random way with my
> > computers after rebooting.
> > Any help is appreciated.
> >
> >
>
> The machine getting a 169.xxx number means that the machine could not get
a
> valid IP and the DHCP on the machine assigned that number. Anytime that
has
> happened to me, I have had to rebuild the TCP/IP Stack on the machine as
it
> has gone bad for some reason. But it usually happens when I combine the
> NetBeui and NWlink IPX/SPX/NetBios together on the machine. I just use
> NWlink over TCP/IP to avoid any issues.
>
> You can use Regedit and go to the following registry entries.
>
> 1) HKEY_LOCAL_MACHINE/system/CurrentControlSet/Services
>
> Locate Winsock and Winsock2 and right-click and Delete
>
> You then come out of Regedit and go to Network and Dial-up connection to
> the Local-Area Connection (for the Network Card) and select Properties.
> In the box uninstall everything in the box --- take note of what is in
> the box. Then reboot the machine which will rebuild the TCP/IP Stack and
> the Winsock(s).
>
> Then you install everything back in the Network Card Property Box and you
> should be good to go.
>
> It is possible that the stack is the problem see if the solution doesn't
> correct the problem.
>
> HTH
>
> Duane
> --
> The protection of the machine is a process and not a given!

"Michael Grigat" <(E-Mail Removed)> wrote in
news:cw0Ta.255256$(E-Mail Removed) .com:

> I tried your fix below, but still same symptom. It shows now another
> error afetr starting up: my Norton Antivirus 2003 comes up with a
> dialog box. Although I have TCP/IP installed it gives me an error:
>
> "Symantec Email Proxy" TCP/IP is not installed 1003.3
> Any idea what has happened ?
>

Did you get another 169.xxx with *Auto Config* words with the IP?

If you got another 169.xxx, then you still have a issue. If you didn't
and you're able to access the Internet and other machines on the network
with the machine, then everything is cool.

If everything is cool, then Norton is full of shit and uninstall Norton
and reinstall it.

You could try to use one of the router's static IP's and see if that
works, then you could narrow it down that something is wrong with the
router's DHCP.

Good luck

Duane

--
The protection of the machine is a process and not a given!