Re: Router install problem

PaulFXH wrote:
On Apr 3, 12:33 pm, Lem <lem...@xxxxxxxxxxx> wrote:
PaulFXH wrote:
On Apr 3, 9:28 am, "PaulFXH" <paulfxhack...@xxxxxxxxx> wrote:
Lem wrote:
PaulFXH wrote:
Lem wrote:
Lem wrote:
PaulFXH wrote:
On Apr 2, 5:53 am, "Scott" <fcct...@xxxxxxxxx> wrote:
"Scott" <fcct...@xxxxxxxxx> wrote in message
news:uUd4GDQdHHA.4984@xxxxxxxxxxxxxxxxxxxxxxx
"PaulFXH" <paulfxhack...@xxxxxxxxx> wrote in message
news:1175382419.269195.77660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi everybody
I working right now in Brazil and have a 550 kbps broadband
connection. The internet reaches the computer through a modem at
present.
However, having recently acquired a second computer we have tried to
install a wireless router (D-Link DI-524 802.11g/2.4GHz) between the
modem
and the computer.
Although I have followed the instructions to the letter, when I get
to
do the final test, I get an error message saying the router is not
detected. After telling me to check the connection between the router
and the computer (which is not the problem), the install goes no
further than this.
Note that in my desperation, I have actually physically changed the
modem and the router and the various network cables for new versions
without at all improving the situation.
I have spoken to the ISP down here but they showed little interest in
helping me.
Any clues as to how I can resolve this?
Thanks
Paul
I was reading the specs on your Speed Stream 5200. Looks like a nice
router/firewall. According to the user manual you need to use a
cross-over
cable when connecting the Speed Stream to a hub or a switch without an
"Uplink" port.
Hope this helps. Good luck. Scott
Also the manual says that the default IP for the Speed Stream is
192.168.254.254 although it may vary by ISP. I think the answers you
seek
are in the Speed Stream manual. Did you log on to the router and look
at the
settings? http://speedstream
Good luck. Scott
--
How many computer programmers does it take to change a light bulb? None.
That's a hardware issue.
Once again I'd like to say thanks to everybody for helping me to
resolve this problem. I should also point out that although I've been
using the internet for 15 years now, about 90% of the stuff being
discussed in this thread is very new to me so forgive me if I seem to
be a little befuddled.
Here below I'm going to try to clarify some of the doubts/questions
people had as well as providing details of the test that Lem
suggested.
As a further point of clarification, the desktop computer to which the
internet (modem only) is directly connected has TWO network cards: the
first (VIA Rhine II) receives the incoming signal from the modem. The
second (Encore 10/100Mbps) is a PCI card that permits the internet to
reach the second computer (laptop) through a (very long) network
cable. The first connection is known as "Local" and the second
(between computers) is known as "Local 3".
So, I went through the computer power-off, router reset, router-to-
computer setup exactly as Lem described.
When I did this, three lights were lit on the router (Power, Status
(blinking) and LAN#1).
Then after typing "ipconfig/all" at the DOS prompt I got the following
information: (note that because I'm in Brazil, this came up in the
Portuguese language, So, I'm giving the English translation):
Configuration of Windows IP
Name of Host Paul
DNS Primary Suffix
Type of Node Unknown
Routing of IP activated Yes
WINS Proxy activated No
Ethernet Connection Adapter Local 3
Specific DNS suffix for Connection Encore 10/100Mbps Fast Ethernet
PCI Adapter
Physical address 00-08-54-B0-3B-95
DHCP activated No
IP address 192.168.0.1
Subnet mask 255.255.255.0
Default Gateway
Ethernet Connection Adapter Local
Specific DNS suffix for Connection VIA Rhine II Fast Ethernet
Adapter
Physical address 00-07-95-C1-69-EE
DHCP activated Yes
IP address 169.254.2.98
Subnet mask 255.255.0.0
Default Gateway
For some reason, I did this whole test again starting from the
powerdown to the router reset and so on. This time, the same three
router lights were lit but additionally the WLAN light was flashing.
Interestingly, when I did the ipconfig/all again, everything was the
same except for some significant differences as shown in the section
below:
Ethernet Connection Adapter Local
Specific DNS suffix for Connection VIA Rhine II Fast Ethernet
Adapter
Physical address 00-07-95-C1-69-EE
DHCP activated Yes
IP address 192.168.0.100
Subnet mask 255.255.255.0
Default Gateway
DHCP Server 192.168.0.1
DNS Servers 192.168.0.1
Concession obtained Today
Concession expires Next week
I hope this throws some light on matters for somebody as I still
remain somewhat flumoxed.
Here are some further clarifications:
a) With the router only connected to the computer and no internet
connection I typed "arp -a" (without quotes) at a DOS prompt but the
message I got was "No entry encountered"
b) I am unclear as to whether this is a DSL or a Cable modem. However,
it is a Speed Stream 5200 which has four lights marked PWR, DSL, USB
and ENET. It receives the broadband signal from a phone line which is
why I thought it was a DSL modem. But as I've said I'm very much a
nooby here
c) The modem was supplied by the ISP (Velox here in Brazil) and no
manual was provided. I have not yet looked for an online version of
the manual
d) When I said that I got an error message during the attempted
installation of the router, the error message (No Router Detected) was
provided by the D-Link installation CD (not from Windows)
e) When I said that "somebody else mentioned that the modem might have
an internal NAT setup" this came from another thread I posted in
another group. But this thread didn't go any further than that
Are we seeing any light at the end of the tunnel?
Thanks
Paul
The vital clue actually came from Scott's posting. This relates to the
"internal NAT setup" in the modem that you mentioned. This is, in fact,
part of the problem.
Your SpeedStream 5200 actually is a combination DSL modem and router.
You do not want to have two routers in your network.
You have two options:
1. Configure the SpeedStream 5200 to operate in "Bridged" mode. In
this mode, the router portion is disabled and the SpeedStream 5200 acts
as a DSL modem only. If you want to do this, you need to connect an
Ethernet cable to the SpeedStream 5200 and enter either
http://speedstreamorhttp://192.168.254.254inyour browser to access
the SpeedStream's configuration pages. For more details, consult the
manual. If you don't have one, it's at
http://www2.windstream.net/downloads/links/SpeedStream211.pdf
2. Alternatively, and perhaps easier, you have to disable the router
portion of the D-Link, and just use it as a wireless access point and
Ethernet switch. In order to accomplish this, you have to do three
things: (1) connect the cable from the SS5200 to the DI524 using a LAN
jack on the DI524 -- NOT the Internet jack; (2) ensure that the DI524
has a LAN IP in the range expected by the SS524; and (3) turn off the
DHCP server in the DI524.
Unfortunately, I have to leave for about 3 or 4 hours right now, so I
can't give you details. You can look it up in the DI524 manual, and
I'll check back later this afternoon.
Continuing ...
When you did things the second time, the computer connected successfully
between "Local" and the DI-524. At this point, you should have been
able to enter 192.168.0.1 in a browser and reach the login screen for
the DI-524 configuration pages. This will be necessary for what follows.
The first piece of information you need is the IP range expected by the
SpeedStream 5200. The definitive way to get this info would be to
connect your computer directly to the SpeedStream (as it originally
was), ensure that you actually have Internet connectivity (you might
need a reboot), and do an ipconfig /all and look at the IP address
assigned to "Local" by the SpeedStream. Alternatively, judging by the
SpeedStream manual, it appears as if the SpeedStream DHCP server assigns
IP addresses in the range 192.168.254.1 to 192.168.254.253. Let's
assume that this is correct, and therefore we will assign the DI-524 an
IP address of 192.168.254.200.
1. Connect to the DI-524 configuration screens by entering 192.168.0.1
...

read more »

Well, I just don't understand this. I had sent this same reply TWICE
yesterday but neither seems to have reached the forum.
So, here it is again, I just hope that three identical replies don't
arrive from me at the same time. If they do, just read one.

Here's the second of the replies I sent

Hi
I've already written a substantial reply that appears to have been
lost in the transmission. So, I'm just a little less good humored than
usual. Anyway, if that were the worst thing that was ever going to
happen to me, I would be extremely relieved.

OK, tried a number of things but, as yet, still no real progress.

First, the first instruction in Lem's list suggests connecting the
DI524 (without SS5200 or internet) and going to the address http://192.168.0.1.
Unfortunately, I have just never been able to get anywhere typing this
into a browser address bar with or without internet and with or
without the DI524 hooked up.
So, that puts a damper on things from the start.

Nevertheless, I went ahead and connected the desktop Encore 10/100
Mbps card to the LAN #1 on the DI524 and went from LAN #2 port to the
laptop. All of this was done with the resetting of the DI524 advocated
by LEM and with the SS5200 connected to the VIA Rhine II card on the
desktop. Therefore there was internet to the desktop.
However, once the laptop was "connected", an error message appeared in
the tray saying that there was a conflict with another network. So, I
gave up on this.

Then, with the same resetting precautions, I connected the Encore card
to the WAN port of the DI 524 and the LAN#1 port on the DI524 to the
laptop.
Now, I got a message in the tray saying that Local 3 (to the laptop)
was connected and no error messages, The DI 524 had five lights lit or
flashing (Power, WAN, #1 with Status and WLAN flashing).

I then ran ipconfig and ipconfig/all at a DOS prompt and got the
following:

ipconfig

Configuração de IP do Windows


Adaptador Ethernet Conexão local 3:

Sufixo DNS específico de conexã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 . :
Endereço IP . . . . . . . . . . . . : 192.168.0.100
Máscara de sub-rede . . . . . . . . : 255.255.255.0
Gateway padrão. . . . . . . . . . . :

Adaptador PPP Conexão Velox:

Sufixo DNS específico de conexão . :
Endereço IP . . . . . . . . . . . . : 201.58.171.234
Máscara de sub-rede . . . . . . . . : 255.255.255.255
Gateway padrão. . . . . . . . . . . : 201.58.171.234

ipconfig/all

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 . . . . . . . . . . . . : 192.168.0.100
Máscara de sub-rede . . . . . . . . : 255.255.255.0
Gateway padrão. . . . . . . . . . . :
Servidor DHCP . . . . . . . . . . . : 192.168.0.1
Servidores DNS. . . . . . . . . . . : 192.168.0.1
Concessão obtida. . . . . . . . . . : quarta-feira, 4 de abril
de 2007 0
9:16:52
Concessão expira. . . . . . . . . . : quarta-feira, 11 de
abril de 2007
09:16:52

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.171.234
Máscara de sub-rede . . . . . . . . : 255.255.255.255
Gateway padrão. . . . . . . . . . . : 201.58.171.234
Servidores DNS. . . . . . . . . . . : 200.165.132.147
200.165.132.154
NetBIOS por Tcpip . . . . . . . . . : Desativado


Looking good so far.
However, when I went to the laptop, even though a network connection
was indicated, when I opened a browser, it was just so unbelievably
slow to be actually unusable.
I then reconfigured the connection to change from DHCP to Static IP
using IP of 192.168.0.1, Subnet mask of 255.255.255.0 and Default
Gateway of 192.168.0.254. However, no change.

Taking out the DI524 and going straight from the Encore card to the
laptop gave me back my internet on the laptop but only after a reboot
(I had reconfigured back to DHCP before making this change).

So still no luck on this one.
Any ideas as to where we go from here?

Paul




Hi Paul,

I only see one post from today and none from yesterday.

If you can't connect to the DI524 from your laptop, as I suggested, there are only a limited number of possibilities:

1. The cable is bad. This probably is not the case, assuming that you're using the same cable to connect the laptop to the DI524 that you used to connect the laptop to the Encore NIC in the main computer. If you have another cable, you might try that.

2. The NIC in the laptop is bad. This is not the case. You know the laptop's NIC works because you can get to the Internet when it's connected to the Encore NIC.

3. The laptop NIC is not configured to use DHCP or it is set to use a static IP OTHER than 192.168.0.2 to 192.168.0.254. This also is not likely to be the case because we know that the Encore NIC has an IP of 192.168.0.1 (coincidentally the same as the default IP address of the DI524), and we know that the laptop communicates with the Encore NIC.

To test, set the laptop to have a static IP of 192.168.0.2 and subnet mask 255.255.255.0. Before you do this, make sure you write down how the laptop's NIC is configured so you can restore it when this test is done. I suspect it is set to obtain an IP address automatically. You can leave default gateway blank at this time. Disconnect everything from the router except a cable from a LAN jack to the laptop. Enter 192.168.0.1 in a browser on the laptop. What happens?

4. The DI524 has been set to an IP address of something other than the 192.168.0.1 and is not resetting to 192.168.0.1 when the reset button is depressed. I suppose it's possible that Brazilian versions of the DI524 have a different default IP, but I doubt it. What happens if you open a command prompt on the laptop and type "ping 192.168.0.1" (without quotes) and press Enter?

5. Some portion of the DI524 is broken.

At this point, I'm leaning toward #5.

As a last resort, try the following:

With your system configured as it used to be, i.e., the laptop connected directly to the Encore card, and with Internet connectivity from the laptop confirmed, run ipconfig /all on the laptop and record the information. I suspect that the laptop's IP address will be 192.168.0.x, but I don't know if the default gateway will be 192.168.0.1 (which is what I think it ought to be) or 201.58.171.234 (or something else).

Disconnect the laptop and set its NIC to a static IP of 192.168.0.2 (actually, you can use anything other than .1, .100, or .254). Set the subnet mask to 255.255.255.0. Set the default gateway whatever it was when you had Internet connectivity through the Encore NIC.

Connect the router as in your first setup above (the desktop Encore 10/100 Mbps card to the LAN #1 on the DI524 and went from LAN #2 port to the laptop). You should not get the "conflicting IP address" error message this time. If you don't get Internet connectivity, try setting the default gateway to 201.58.171.234 if you had set it to 192.168.0.1.

Even if this works, however, if you are unable to access the DI524's configuration pages, you will be unable to properly configure its wireless settings. Although you may be able to connect wirelessly, your network will be completely vulnerable to outside attack, because it will be using the default SSID and no encryption.

--
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
.