Re: Router install problem

PaulFXH wrote:
On 7 abr, 17:11, "PaulFXH" <paulfxhack...@xxxxxxxxx> wrote:
On 7 abr, 13:09, Lem <lem...@xxxxxxxxxxx> wrote:

<old portion of thread snipped>
Paul,
I've been toying with the idea of emigrating to Brazil. Maybe I should
just come down and start a computer repair business in São Paulo. Can I
get by without any Portuguese?
You mean you still haven't picked up enough Portuguese in the stuff I
been sending in this thread?





A router is an interface between two networks that otherwise couldn't
communicate directly. In your case, that's the Internet (the Wide Area
Network or WAN) and your local area network (LAN). Usually, the WAN
side of the router is configured to talk to the Internet via a cable or
DSL modem which is connected to the router's WAN/Internet port and the
LAN side of the router (the 4 LAN ports and the wifi radio) is
configured to talk to the local computers. The router provides Network
Address Translation (NAT) to translate addresses between those on the
Internet and those on your LAN.
In your setup, I couldn't understand how to get the router to talk to
your SpeedStream modem, so I've disregarded that portion of the router
(the NAT function is provided by Windows ICS). However, when you used
the DI-524 "Internet Connection Wizard" you were configuring the
WAN-facing side of the router. I don't know why the router should have
"stalled" for 30 minutes, but none of the settings you made in the
"Internet Connection Wizard" are relevant to the way I was trying to
setup your system. Put another way, all of those settings have to do
with the DI-524's WAN/Internet port, which should not be connected to
anything.
I don't have a DI-524, so I don't know what its "Wizard" screens look
like, but for now, you needn't worry about settings you made there for
the reasons explained above. I've downloaded the manual, and based on
that, here's all that you need to do:
After you login to the DI524 configuration screens, you should see a
screen with 5 tabs across the top (Home, Advanced, Tools, Status, Help)
and 5 buttons on the left (Wizard, Wireless, WAN, LAN, DHCP).
Configure the DHCP server (which you seem to have already done, but for
completness):
Click the DHCP button. On the Home tab, click the radio button for
"Disabled" and click "Apply."
Configure the LAN-facing IP of the DI-524 (this is what you wanted to
set to 192.168.0.5):
Click the LAN button. On the Home tab, set the IP address to
192.168.0.5 and the subnet mask to 255.255.255.0 (leave "Local Domain
Name" blank) and click the "Apply" button.
Note 1: If you don't click the "Apply" button on any of these screens,
any changes you make on the screen are discarded when you switch to
another screen.
Note 2: As soon as you click "Apply" after changing the IP address, you
probably will be disconnected. That's because you were talking to the
router at 192.168.0.1, and it's not at that address any more. Just
re-login to the router, this time using 192.168.0.5 in your browser.
Before you quit the DI-524 configuration screens, you can check that
settings indeed have been applied by clicking on the "Status" tab and
"Device Info" button. The parts of this page that you are interested in
are the LAN and Wireless sections. The info in the WAN section is not
relevant because your WAN port is not connected. Note that the "DHCP
Release" and "DHCP Renew" buttons in the WAN section refer to the DHCP
server *at your ISP* and NOT to the DHCP server that is internal to your
DI-524.
Once you are working with the cable between the laptop and the DI524,
here's what to do with the wifi:
Login to the router at 192.168.0.5
Click the Wireless button. On the Home tab, set the SSID to something
unique, but not your last name or address. You can leave the channel at
its default (6), or if you experience interference from nearby wifi
networks, try setting it to 11 or 1 (due to overlap, there really are
only 3 distinct channels, even though it looks like 11). Setup the
encryption.
The downloadable manual only shows WEP encryption, but I assume that
more recent versions of the DI-524 should be capable of better
encryption. In order from worst to best: none, WEP 64, WEP 128, WPA,
WPA2. In picking a level of encryption, you are limited by both the
router and the laptop. If your laptop is relatively new, and fully
up-to-date with Windows XP sp2 and subsequent Microsoft updates, you
should have at least WPA, if not WPA2. A WPA "passphrase" can be up to
63 characters long. Pick one that is at least 8 characters, not a
dictionary word, uses both letters and numbers, but is easy to remember.
Many experts recommend using at least a 20 to 25 character phrase, but
this may be overkill. There are also many WPA/WEP key generators on the
Internet; Google for "wpa key generator".
One other thing: you probably should change the password used to access
the DI-524. This is done from the "Tools" tab, "Admin" button.
Remember to click the "Apply" button, and write down the password
somewhere safe. You can also set the router's time from the "Tools" tab
"Time" button. Other than compulsiveness, the only reason to do this is
if you set up some of the router's features to limit Internet access at
specified times.
Thanks for your wonderfully detailed instructions which I bet you
thought were by now truly n00bie-proof.
Alas no. The saga continues.
However, I did get through most of it and, even though pressing the
Apply button gave a never-ending "saving and restarting" message, it
did at least allow me to continue.
When I checked the Status tab, the changes I had made to the DHCP
server (disabled) and Lan IP (192.168.0.5) seemed to have been saved.
It's possible that the reason it didn't stop "saving and restarting"
is that the connection to 192.168.0.1 was lost during the saving
process.
Anyway, I was able now to connect to 192.168.0.5 and make the SSID and
encryption changes.
After this I tried to change the name and password for connection to
DI524 and it just wouldn't accept the Admin/Blank name and password
that was needed for this change to be accepted.
So, I reset the DI524 and hooked it up again. Now, trying to conect to
192.168.0.1 (I presume it gets reset back to this) I get the following
message:

Firmware Upgrade
File Path

NOTICE !!
If you upload the binary file to the wrong TARGET, the router may not
work properly or even could not boot-up again.

where the space after File Path is to allow me to input the path of
which I have no idea.

After several re-attempts to reset the DI524 I kept getting this page
rather than the Username/Password box that always appeared before.

Looks like Murphys Law applies with equal if not increased vigor down
here too.
I'm going to try again tomorrow to reset the DI524 and take it from
there.

Paul

OK, so this is a continuation of my post from yesterday and I'm
delighted to report that I now have a wired connection through the
DI524 (from the Encore card) to the laptop. Everything seems to be
normal (for the moment at least). Indeed, I should point out that the
laptop is dual boot (WinXP and Ubuntu Linux; the latter being what I
normally use). All of the configuration stuff I did for the DI524 was
in Windows. But even when I booted back to Ubuntu, the internet
connection was perfect.

I really wish, though, that I could explain in a logical scientific
manner why it's working today but didn't yesterday. Unfortunately, I
cannot.
Nevertheless, there are some strange things happening when the DI524
is connected to the laptop:

i) apparently lost the connection to both 192.168.0.1 and 192.168.0.5
yesterday and a message regarding a firmware upgrade persisted in
showing up (but only for 192.168.0.1; enetring 192.168.0.5 just gave a
"page not found" error). No sign of this firmware message to day.

ii) today I reset the DI524 and tried again to ensure that DHCP was
disabled and the LAN IP was set at 192.168.0.5 However, even after
resetting, these values that I had entered yesterday were still there.
Shouldn't resetting put everything back to "factory settings"?

iii) while I was there on the DI524 configuration page, again I seemed
to have lost the connection as clicking on any of the tabs (e.g.
STATUS or LAN or DHCP) just gave a "page not found" error. The only
tab that workd was HOME, posibly because this was cached. So, I had to
go through the whole resetting and reconnecting rigmarole again.
However, when I tried again, the laptop now had the internet connected
and everything was fine.

Now, I know the next step is to try to get the laptop to accept a
wireless internet signal from the DI524 but I decided to leave that
for tomorrow and bask for a while in the glory of this hard-won
triumph.

Nevertheless, it did cross my mind that if the reason that the DI524
was not seen by the computer when I had set it up between the SS5200
and the desktop was because of the 192.168.0.1 being also the IP
address of the Local3 connection and the fact that both the DI524 and
SS5200 had enabled DHCP servers, then perhaps this would work now
(with the DI524 set to 192.168.0.5 and DHCP disabled).
So, I tried it but got the same result as before which is an error
from the DI524 install disk stating that no router is seen.

I should point out that the Velox internet signal/SS5200 modem seems
to be a delicate combination here. For example, if the internet to the
desktop is not deactivated with care (in other words, without a power
cut or need to pull the plug on the computer due to a freeze) then
both the computer and the SS5200 must remain powered off for at least
10 minutes before switching on again. Otherwise no internet connection
will be possible.
I have a feeling that yanking the ethernet cable from the SS5200
during the DI524 installation (to the desktop) may well be inducing
whatever is upsetting it when not shut down with care. I may try again
tomorrow with a little more delicacy to see if this will enable the
DI524 to be installed as originally planned.

One thing I found strange was that the Local3 connection from the
desktop to the laptop remained unaltered (even though I did nothing to
reconfigure this) when the DI524 was interposed between the laptop and
the desktop.

With the setup as it is now, I ran "ipconfig/all" on both the desktop
and the laptop which are given below:

Desktop:
Configuração de IP do Windows

Nome do host . . . . . . . . . . . : Paul
Sufixo DNS primário. . . . . . . . :
Tipo de nó . . . . . . . . . . . . : desconhecido
Roteamento de IP ativado . . . . . : sim
Proxy WINS ativado . . . . . . . . : não

Adaptador Ethernet Conexão local 3:

Sufixo DNS específico de conexão . :
Descrição . . . . . . . . . . . . . : ENCORE 10/100Mbps Fast
Ethernet PC
I Adapter
Endereço físico . . . . . . . . . . : 00-08-54-B0-3B-95
DHCP ativado. . . . . . . . . . . . : Não
Endereço IP . . . . . . . . . . . . : 192.168.0.1
Máscara de sub-rede . . . . . . . . : 255.255.255.0
Gateway padrão. . . . . . . . . . . :

Adaptador Ethernet Conexão local:

Sufixo DNS específico de conexão . :
Descrição . . . . . . . . . . . . . : VIA Rhine II Fast
Ethernet Adapter

Endereço físico . . . . . . . . . . : 00-07-95-C1-69-EE
DHCP ativado. . . . . . . . . . . . : Sim
Configuração automática ativada . . : Sim
Endereço IP de config. automática . : 169.254.142.244
Máscara de sub-rede . . . . . . . . : 255.255.0.0
Gateway padrão. . . . . . . . . . . :

Adaptador PPP Conexão Velox:

Sufixo DNS específico de conexão . :
Descrição . . . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Endereço físico . . . . . . . . . . : 00-53-45-00-00-00
DHCP ativado. . . . . . . . . . . . : Não
Endereço IP . . . . . . . . . . . . : 201.58.xyz.abc (I
disguised these as this seems to be my "real" external IP)
Máscara de sub-rede . . . . . . . . : 255.255.255.255
Gateway padrão. . . . . . . . . . . : 201.58.xyz.abc
Servidores DNS. . . . . . . . . . . : 200.165.132.147
200.165.132.154
NetBIOS por Tcpip . . . . . . . . . : Desativado

Laptop:
Configuração de IP do Windows

Nome do host . . . . . . . . . . . : Paul2
Sufixo DNS primário. . . . . . . . :
Tipo de nó . . . . . . . . . . . . : misto
Roteamento de IP ativado . . . . . : não
Proxy WINS ativado . . . . . . . . : não
Lista de pesquisa de sufixo DNS. . : mshome.net

Adaptador Ethernet Conexão local:

Sufixo DNS específico de conexão . : mshome.net
Descrição . . . . . . . . . . . . . : Intel(R) PRO/100 VE
Network Connec
tion
Endereço físico . . . . . . . . . . : 00-18-FE-27-B5-9C
DHCP ativado. . . . . . . . . . . . : Sim
Configuração automática ativada . . : Sim
Endereço IP . . . . . . . . . . . . : 192.168.0.121
Máscara de sub-rede . . . . . . . . : 255.255.255.0
Gateway padrão. . . . . . . . . . . : 192.168.0.1
Servidor DHCP . . . . . . . . . . . : 192.168.0.1
Servidores DNS. . . . . . . . . . . : 192.168.0.1
Concessão obtida. . . . . . . . . . : domingo, 8 de abril de
2007 15:57:
12
Concessão expira. . . . . . . . . . : domingo, 15 de abril de
2007 15:57
:12

Paul



--
Lem -- MS-MVP - Networking
To the moon and back with 64 Kbits of RAM and 512 Kbits of ROM.http://en.wikipedia.org/wiki/Apollo_Guidance_Computer



Paul,
I'm glad you finally got things going.

Your DI-524 still seems a bit flaky to me. AFAIK, it shouldn't ask you to upgrade the firmware unless you click on the link to check for an upgrade (on the Tools tab, Firmware button). And, as you noted, resetting is supposed to reset everything to factory defaults. I'm not as familiar with D-Link devices as Linksys, but in the latter I've seen examples where reset needed to be done more than once in order to really get it to work.

The ipconfig /all results look OK.

The Encore NIC appears to be using Windows Internet Connection Sharing (as it should). That's why it is set to 192.168.0.1 with a subnet mask of 255.255.255.0. It doesn't show a default gateway or DNS servers because these functions are performed on the other part of the "shared" connection.

The Local (VIA Rhine II) NIC has what's called an APIPA address, which is automatically assigned (Configuração automática ativada . . : Sim) when the NIC is set to obtain an IP address automatically but no DHCP server is available.

The Velox connection (PPP/SLIP) shows, as you assumed, your "real" IP address, i.e., the one that you show to the rest of the Internet. Depending on how Velox works, that may change each time you connect (a dynamic IP) or it may not. Most ISPs in the US use dynamic IP addresses unless you pay more. This allows the ISP to own fewer IP addresses than they have actual customers, on the theory that not all customers will be on-line at the same time.

The laptop looks like you re-configured it to get an automatic IP address, and it has been assigned 192.168.0.121 by the DHCP allocator function of ICS. As it should, it points to the Encore NIC for its default gateway and DHCP and DNS servers.

Tchau e boa sorte
--
Lem MS MVP -- Networking

To the moon and back with 64 Kbits of RAM and 512 Kbits of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
.