Router install problem

[Lem]

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://speedstream or http://192.168.254.254 in your 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
in your browswer. The first thing you should see is a login screen.
Type admin in the User Name field and leave the password blank. Click OK.

2. Click the DHCP button on the left side of the screen. On the page
that comes up, click the radio button to "Disable" the DHCP server and
click the "Apply" button.

3. Click the LAN button on the left side of the screen. On the page
that comes up, next to IP address, enter 192.168.254.200
If the subnet mask is not already at 255.255.255.0, make it so.
Click the "Apply" button. At this point, you probably will lose
connectivity to the router. This is because the network interface card
in your computer (Local) has an IP address of 192.168.0.100 and the
router now has an IP address of 192.168.254.200. Because the "third
octet" is not the same (254 ¬= 0), the computer and the router are not
in the same "subnet" and thus can't talk to each other.

4. Power off the router and the computer. Connect an Ethernet cable
between the SpeedStream and one of the 4 LAN jacks on the DI-524. Leave
the Internet jack on the DI-524 open. Power up the DI-524. Wait a
minute or 2 until the lights stabilize. Now boot up the computer.

You should now have Internet connectivity on you main computer. If you
do an ipconfig /all on this computer, you should see that its IP address
is 192.168.254.x (where x is between 1 and 253, hopefully not 200). The
entries for DHCP server and Default Gateway should both be
192.168.254.254 (i.e., the SpeedStream).

5. Now you have to re-access the router's configuration screens. This
time, enter 192.168.254.200 in your browser (BTW, you should probably
write this down on a small label and stick it to the top of the router).
Login to the router as described in step 1.

a. Click the "Tools" tab, and click the "Admin" button on the
right. Set new passwords for the "admin" and "user" logins. Write
these down. Ensure that "Remote management" is DISabled. Click the
"Apply" button.

b. Click the "Home" tab and click the "Wireless" button. Select
a unique name, other than your last name or address, and enter it as the
"SSID". This will be the name of your wireless network.

c. You can leave the channel at its default of 6, but if you
experience problems, such as frequent disconnects, you might want to
change it to 1 or 11 to try to minimize interference with wifi networks
that a neighbor might have set up.

d. Set the encryption. Use the most secure encryption you have
that is compatible with your laptop's wifi adapter. From worst to best:
none, WEP 64bit, WEP 128 bit, WPA, WPA2. If your laptop is relatively
new, you probably will have at least WPA. Try to choose a "strong"
password. There are various Internet sites that can help you in this
regard. Just Google for them. Click the "Apply" button.

6. At this point, you should be able to connect from your laptop via
its wifi adapter. You also may be able to share files between the
computers, if you had previously configured "file and printer sharing"
on both. If not, you can run the "Network setup wizard" on both
computers. You might want to skip step 5(d) and try connecting with
your laptop before setting up the encryption, just to eliminate this as
a potential problem. Just make sure that you do set up encryption
before you're done. Also, just in case the wireless connection gives
you problems, you can always take your long Ethernet cable and plug it
into one of the DI-524's LAN jacks. If you have difficulty accessing
one computer from the other, make sure that you have correctly
configured all firewalls, including any antivirus with a firewall-like
feature (such as "Internet worm protection"). Always make changes to
the DI-524 using a computer with an Ethernet connection -- not one with
a wifi connection.

 

[PaulFXH]

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
in your browswer. The first thing you should see is a login screen.
Type admin in the User Name field and leave the password blank. Click OK.

2. Click the DHCP button on the left side of the screen. On the page
that comes up, click the radio button to "Disable" the DHCP server and
click the "Apply" button.

3. Click the LAN button on the left side of the screen. On the page
that comes up, next to IP address, enter 192.168.254.200
If the subnet mask is not already at 255.255.255.0, make it so.
Click the "Apply" button. At this point, you probably will lose
connectivity to the router. This is because the network interface card
in your computer (Local) has an IP address of 192.168.0.100 and the
router now has an IP address of 192.168.254.200. Because the "third
octet" is not the same (254 ¬= 0), the computer and the router are not
in the same "subnet" and thus can't talk to each other.

4. Power off the router and the computer. Connect an Ethernet cable
between the SpeedStream and one of the 4 LAN jacks on the DI-524. Leave
the Internet jack on the DI-524 open. Power up the DI-524. Wait a
minute or 2 until the lights stabilize. Now boot up the computer.

You should now have Internet connectivity on you main computer. If you
do an ipconfig /all on this computer, you should see that its IP address
is 192.168.254.x (where x is between 1 and 253, hopefully not 200). The
entries for DHCP server and Default Gateway should both be
192.168.254.254 (i.e., the SpeedStream).

5. Now you have to re-access the router's configuration screens. This
time, enter 192.168.254.200 in your browser (BTW, you should probably
write this down on a small label and stick it to the top of the router).
Login to the router as described in step 1.

a. Click the "Tools" tab, and click the "Admin" button on the
right. Set new passwords for the "admin" and "user" logins. Write
these down. Ensure that "Remote management" is DISabled. Click the
"Apply" button.

b. Click the "Home" tab and click the "Wireless" button. Select
a unique name, other than your last name or address, and enter it as the
"SSID". This will be the name of your wireless network.

c. You can leave the channel at its default of 6, but if you
experience problems, such as frequent disconnects, you might want to
change it to 1 or 11 to try to minimize interference with wifi networks
that a neighbor might have set up.

d. Set the encryption. Use the most secure encryption you have
that is compatible with your laptop's wifi adapter. From worst to best:
none, WEP 64bit, WEP 128 bit, WPA, WPA2. If your laptop is relatively
new, you probably will have at least WPA. Try to choose a "strong"
password. There are various Internet sites that can help you in this
regard. Just Google for them. Click the "Apply" button.

6. At this point, you should be able to connect from your laptop via
its wifi adapter. You also may be able to share files between the
computers, if you had previously configured "file and printer sharing"
on both. If not, you can run the "Network setup wizard" on both
computers. You might want to skip step 5(d) and try connecting with
your laptop before setting up the encryption, just to eliminate this as
a potential problem. Just make sure that you do set up encryption
before you're done. Also, just in case the wireless connection gives
you problems, you can always take your long Ethernet cable and plug it
into one of the DI-524's LAN jacks. If you have difficulty accessing
one computer from the other, make sure that you have correctly
configured all firewalls, including any antivirus with a firewall-like
feature (such as "Internet worm protection"). Always make changes to
the DI-524 using a computer with an Ethernet connection -- not one with
a wifi connection.

Thanks Lem for these detailed instructions.
As before I will try this out tomorrow morning.
However, I will just mention one thing that may cause problems. Note
that, right now, we use the internet with ONLY the SS5200 connected to
the computer. The D-Link DI524 is sitting quietly in its box doing
nothing (which is actually what it does even when it is hooked up but
that's the point of this thread).

1) When I type "ipconfig" at a DOS prompt the output includes the
following relevant to the Local connection:

Adaptador Ethernet Conexão local:

Sufixo DNS específico de conexão . :
Endereço IP de config. automática . : 169.254.142.244
Máscara de sub-rede . . . . . . . . : 255.255.0.0
Gateway padrão. . . . . . . . . . . :

As you can see, this is in Portuguese but should be readily
understandable (with the possible exception of the word "endereço"
which means "address")
However, as you can see the IP address is very different from the
expected range.

I'm not sure how significant this is, but I'll go ahead with the test
tomorrow inany case.

Thanks again
Paul

 

[Scott Lane]

<snip>
1) When I type "ipconfig" at a DOS prompt the output includes the
following relevant to the Local connection:

Adaptador Ethernet Conexão local:

Sufixo DNS específico de conexão . :
Endereço IP de config. automática . : 169.254.142.244
Máscara de sub-rede . . . . . . . . : 255.255.0.0
Gateway padrão. . . . . . . . . . . :

<snip>
Paul the 169 .254.142.244 number means the adaptor cannot see the router. I
am getting confused here, but make sure you install the software for the
wireless adaptor properly so that it can communicate with the router.
I think 169.anything means the adaptor cannot see anything to connect to.

Looks like you have good help now. Install your adaptor, make sure you can
communicate with the D-Link, configure your Speed Stream and you should be
online with the wireless.

Scott

 

[Scott Lane]

Lem wrote:

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

Lem
Thanks for the excellent help. I was wondering if Paul is going to need a
cross-over cable between the Speed Stream and the D-link? The SS manual
mentions it is necessary if connecting to a switch or a hub without an
"uplink" port.

Thank you sir.
Scott

 

[Lem]

Lem
Thanks for the excellent help. I was wondering if Paul is going to need a
cross-over cable between the Speed Stream and the D-link? The SS manual
mentions it is necessary if connecting to a switch or a hub without an
"uplink" port.

Thank you sir.
Scott

The D-Link router, like many modern home routers, has ports that
auto-detect the type of cable so that you can use either a cross-over or
a straight-through cable.

 

[Lem]

Thanks Lem for these detailed instructions.
As before I will try this out tomorrow morning.
However, I will just mention one thing that may cause problems. Note
that, right now, we use the internet with ONLY the SS5200 connected to
the computer. The D-Link DI524 is sitting quietly in its box doing
nothing (which is actually what it does even when it is hooked up but
that's the point of this thread).

1) When I type "ipconfig" at a DOS prompt the output includes the
following relevant to the Local connection:

Adaptador Ethernet Conexão local:

Sufixo DNS específico de conexão . :
Endereço IP de config. automática . : 169.254.142.244
Máscara de sub-rede . . . . . . . . : 255.255.0.0
Gateway padrão. . . . . . . . . . . :

As you can see, this is in Portuguese but should be readily
understandable (with the possible exception of the word "endereço"
which means "address")
However, as you can see the IP address is very different from the
expected range.

I'm not sure how significant this is, but I'll go ahead with the test
tomorrow inany case.

Thanks again
Paul

Well, now I'm confused. Before you start following the directions in my
last post, we have to figure out what's going on.

An IP address of the type 169.254.x.x is automatically supplied by
Windows when no DHCP server is detected. Thus my previous directions,
which assumed that the SS5200 had an operating DHCP server, won't work
(at least not yet).

Are you, by any chance, connecting the SS5200 to the computer using a
USB connection in addition to the Ethernet cable?

Do you know the userid and password required by your ISP to connect to
the Internet or did you get the SS5200 pre-configured, with the
userid/password already set into it? (Don't post this info here, just
say whether or not you know it.)

With the computer connected only to the SS5200, what happens when you
enter http://speedstream in your web browswer? What happens if you
enter 192.168.254.254?

When you go to Control Panel > Network and Internet Connections >
Network Connections, what do you see there? From your last posts, you
have at least 2 items under the heading "LAN or High-Speed Internet" --
Local and Local 3. What else is in Network Connections?

When you go to My Network Places, what do you see there?

Finally, I suggest you download the manual for the SS5200 from
http://www2.windstream.net/downloads/links/SpeedStream211.pdf It's long
and complicated, but we may need to make some changes or at least see
what the current configuration is.

 

[Scott]

Thanks Lem. According to Pauls first post he can't connect to his D-Link. I
was trying to ask him what type of wireless adaptor he has and if it is
installed properly. Apparently he doesn't have a wireless connection to his
D-Link yet. When I run ipconfig /all with a Belkin USB wireless adaptor I
get a Windows IP Configuration and an Ethernet Adaptor Wireless Network
Connection showing a Belkin 54G Wireless Network Adaptor description.

Thanks again for your help and patience.
Scott

 

[PaulFXH]

Well, now I'm confused.

Before you start following the directions in my
last post, we have to figure out what's going on.

An IP address of the type 169.254.x.x is automatically supplied by
Windows when no DHCP server is detected. Thus my previous directions,
which assumed that the SS5200 had an operating DHCP server, won't work
(at least not yet).

Are you, by any chance, connecting the SS5200 to the computer using a
USB connection in addition to the Ethernet cable?

No, there is no usb connection between the SS5200 and the computer--
just the ethernet cable alone.

Do you know the userid and password required by your ISP to connect to
the Internet or did you get the SS5200 pre-configured, with the
userid/password already set into it? (Don't post this info here, just
say whether or not you know it.)

From what I saw, the SS5200 must have been preconfigured. Afetr I

coudn't get the DI524 to work, I complained to the ISP (Velox in
Brazil). They promptly arrived at my house and produced a brand new
modem (as they refer to it--but which appears to actually be a
combined router-modem ti.e. the SS5200)). This seemed to work straight
out of the box as the guy just hooked it up and voila--everything was
fine.

With the computer connected only to the SS5200, what happens when you
enter http://speedstream in your web browswer?

This re-directs me to a page named Siemens, Speedstream Home
Networking Support. This then gives a list of links to different
products none of which, strangely, is SS5200.

What happens if you
enter 192.168.254.254?

I get an error message (in Portuguese) saying there is a network
problem and the 192.168.254.254 address is currently unavailable.

When you go to Control Panel > Network and Internet Connections >
Network Connections, what do you see there? From your last posts, you
have at least 2 items under the heading "LAN or High-Speed Internet" --
Local and Local 3. What else is in Network Connections?

These are the entries in Control Panel >Network Connections
(translated from Portuguese)

Dial-Up
Velox Connection, Connected-Shared-Protected by Firewall, VIA Rhine II
Fast Ethernet Adapter
Terra, Not connected

Local network or Highspeed Internet
Connection Local, Null or limited connection-Protected by Firewall,
VIA Rhine II Fast Ethernet Adapter
Connection Local 3, Connected-Protected by Firewall, Encore 10/100
Mbps Fast Ethernet Adapter

Perhaps I should also supply everything that shows up when I type
"ipconfig" at a DOS prompt (rather than just the stuff for the Local
Connection as I did yesterday). Here it is (unfortunately again in
Portuguese):

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 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 . :
Endereço IP . . . . . . . . . . . . : 201.58.126.100
Máscara de sub-rede . . . . . . . . : 255.255.255.255
Gateway padrão. . . . . . . . . . . : 201.58.126.100

When you go to My Network Places, what do you see there?

In My Network Places there is one entry under Internet and two under
Local Network. Both are just private stuff of no relevance to this
investigation.

Finally, I suggest you download the manual for the SS5200 from
http://www2.windstream.net/downloads/links/SpeedStream211.pdf It's long
and complicated, but we may need to make some changes or at least see
what the current configuration is.

OK, I've done that but haven't read it yet as it is a somewhat
forbidding tome.

Thanks
Paul

 

[PaulFXH]

...

read more »

I'm just going to give some further information on the details
availanle in Network Connections for the Velox connection (remember
that Velox is the name of the ISP down here):

Name of Hardware VIA Rhine II Fast Ethernet
Adapter
Type of Hardware isdn
Type of Server PPP
Transports TCP/IP
Authentication PAP
Compaction none
Framing (?) of PPP multilink Turned off
Server IP address 200.217.72.88
Client IP address 201.58.126.100

In answer to Scott's question about wireless adaptors, I really
haven't got to that stage yet. All I am trying to acheive right now is
to get an internet connection to the Desktop computer through the
SS5200 and DI-524. As the DI-524 is a wireless router and the laptop
(HP Pavilion dv1000) has a built-in wireless card, I had assumed that
if the DI-524 was operational, the laptop would be able to pick up the
internet from the router wirelessly.

 

[Lem]

I'm just going to give some further information on the details
availanle in Network Connections for the Velox connection (remember
that Velox is the name of the ISP down here):

Name of Hardware VIA Rhine II Fast Ethernet
Adapter
Type of Hardware isdn
Type of Server PPP
Transports TCP/IP
Authentication PAP
Compaction none
Framing (?) of PPP multilink Turned off
Server IP address 200.217.72.88
Client IP address 201.58.126.100

In answer to Scott's question about wireless adaptors, I really
haven't got to that stage yet. All I am trying to acheive right now is
to get an internet connection to the Desktop computer through the
SS5200 and DI-524. As the DI-524 is a wireless router and the laptop
(HP Pavilion dv1000) has a built-in wireless card, I had assumed that
if the DI-524 was operational, the laptop would be able to pick up the
internet from the router wirelessly.

I think that your Brazilian DSL connection must not use the PPPoE
protocol that is commonly used in the U.S.A. and elsewhere. I'm also
confused by the "isdn" in in the hardware description under the Velox
connection, and the indication that the Velox "Dial-up" connection is
shared with the VIA Rhine II adapter ("Local"). If anything was shared,
I would have thought it would have been your "Local 3" connection on the
Encore adapter.

Rather than try to figure out what's really going on, and risk messing
up the configuration of the SpeedStream to the point where you can't do
anything, perhaps we can attack this problem in another way.

As I understand your setup before you got the DI-524, you had your main
computer connected to the SS5200 and your laptop connected by a long
ethernet cable to a second network adapter on the main computer. I hope
this setup still works for you. If so, what appears to be going on is
that however your Internet connection works, you have successfully
shared it (probably using Windows Internet Connection Sharing) to the
second (Local 3) network adapter. This is consistent with the ipconfig
information you gave for Local 3.

When accessing the configuration pages of the DI-524, it may be simpler
to use your laptop connected to one of the LAN jacks on the DI-524
rather than using your main computer. If things work as planned, we're
going to leave the laptop connected that way, at least until you get
wireless working.

We can connect the DI-524 to the second network adapter in place of the
laptop. ICS assigns an IP of 192.168.0.1 to the network adapter facing
your internal network and assigns IP addresses in the range 192.168.0.2
through 192.168.0.254.

Thus, follow the numbered steps in my earlier post, except that when you
get to step 3, set the DI-524 IP address to 192.168.0.2. Everything
else will stay the same.

If I'm correct that you are using Windows ICS, you will be able to
connect your laptop to one of the 3 remaining LAN jacks on the DI-524,
where it will be assigned an IP address of 192.168.0.x by the DHCP
server function of ICS. It will then connect through the switch portion
of the DI-524 to your Local 3 adapter which in turn will connect to the
Internet however it is that your main computer accomplishes that.

Let me know how it goes.

 

[PaulFXH]

...

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

 

[Lem]

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.

 

[PaulFXH]

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.

Hi Lem
Still can't figure out what happened to my two posts from Wednesday.
Presumably, they got as far as some server in trouble which proceeded
to dump them. Oh well.
However, just when we thought things were starting to look a little
hopeless, a faint light is now starting to emerge at the end of this
long tunnel.
The test you suggested as a last resort above actually got me to the
login page for D-Link configurations.
I used the following parameters for the static IP address config:
IP 192.168.0.2
Subnet mask 255.255.255.0
Default gateway 192.168.0.1 although I got to the D-Link page also
when the default gateway was set to 201.58.171.234

Although this page was sitting there right in front of me inviting me
to change the routers configuration, I felt it better to wait to hear
from you before taking this bold step.

Before doing any of this on the laptop, I ran ipconfig/all at a DOS
prompt and got the following:

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.132
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. . . . . . . . . . : sexta-feira, 6 de abril
de 2007 09
:23:48
Concessão expira. . . . . . . . . . : sexta-feira, 13 de abril
de 2007 0
9:23:48

I think the Portuguese here is readily translatable (possible
exception is Node Type = Mixed where it says "Tipo de
nó . . . . . . . . . . . . : misto".

I do hope this means that perhaps we're now entering the home
straight.

Thanks
Paul

 

[Lem]

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.

Hi Lem
Still can't figure out what happened to my two posts from Wednesday.
Presumably, they got as far as some server in trouble which proceeded
to dump them. Oh well.
However, just when we thought things were starting to look a little
hopeless, a faint light is now starting to emerge at the end of this
long tunnel.
The test you suggested as a last resort above actually got me to the
login page for D-Link configurations.
I used the following parameters for the static IP address config:
IP 192.168.0.2
Subnet mask 255.255.255.0
Default gateway 192.168.0.1 although I got to the D-Link page also
when the default gateway was set to 201.58.171.234

Although this page was sitting there right in front of me inviting me
to change the routers configuration, I felt it better to wait to hear
from you before taking this bold step.

Before doing any of this on the laptop, I ran ipconfig/all at a DOS
prompt and got the following:

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.132
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. . . . . . . . . . : sexta-feira, 6 de abril
de 2007 09
:23:48
Concessão expira. . . . . . . . . . : sexta-feira, 13 de abril
de 2007 0
9:23:48

I think the Portuguese here is readily translatable (possible
exception is Node Type = Mixed where it says "Tipo de
nó . . . . . . . . . . . . : misto".

I do hope this means that perhaps we're now entering the home
straight.

Thanks
PaulPaul,

I think we *are* nearing the finish line.

At the risk of making this long thread even longer, and of giving you
information that you already may know, let me try to explain a little of
what is going on.

There are 3 blocks of IP addresses reserved for use as private networks
(local networks). The block typically used by SOHO LANs is 192.168.0.0
through 192.168.255.255. Such networks can be further subdivided into
"subnets." This is where the "subnet mask" comes in. In order to
communicate directly (without a router), computers must be on the same
subnet. With a subnet mask of 255.255.255.0, and on a LAN using the
192.168.x.y block of addresses, the subnet can be thought of as the
third octet in the address, i.e., "x" in the example. Thus, in order to
communicate directly, devices on such a LAN must have IP addresses in
which the first 3 octets are identical. That is, in your case, all IP
addresses on your LAN must be 192.168.0.y.

Each IP on the LAN must be unique. So, when you got the "conflicting
address" error, you had two devices with the same IP, probably 192.168.0.1.

IP addresses can either be set statically or automatically, using
Dynamic Host Configuration Protocol (DHCP).

Because of the way your Internet access is configured (which I don't
fully understand), your LAN consists of (1) the Encore NIC on the main
computer, (2) the DI-524, and (3) the NIC on the laptop. You have at
least two devices on this LAN that are capable of performing the DHCP
function: Windows ICS running on the Encore and the DHCP server built
into the DI-524.

You don't want two active DHCP servers on the same LAN because of the
danger that they will assign the same IP address to different devices.
Because the DHCP function of ICS can't be turned off or configured, you
must turn off the DHCP server in the DI-524 (as a practical matter, of
course, if all the computers connected through the DI-524 are set with
static IP addresses, it wouldn't matter if you left the DI-524 DHCP
server turned on).

As an aside, if you really were unable to see the DI-524 configuration
login screen when you connected the laptop with the laptop's NIC set to
obtain an IP address automatically, but could see it when you set a
static IP on the laptop, it suggests that the DI-524's DHCP server is
either already turned off or broken.

Another aspect of Windows ICS that cannot be configured is the IP
address that is set on the shared NIC, i.e., on the Encore. ICS forces
the Encore to a static IP address of 192.168.0.1. See
http://support.microsoft.com/kb/306126/ and
http://support.microsoft.com/kb/310563/en-us for more information.

Because the Encore has an IP address of 192.168.0.1 and the default IP
address of the DI-524 is also 192.168.0.1, if you connect the Encore to
one of the LAN jacks of the DI-524, you will get an error message
warning that there are conflicting devices on the network. Thus, you
need to change the IP address of the DI-524. In order to be able to
communicate with this device, its IP address must be in the same
192.168.0.x subnet. If you set the DI-524 to 192.168.0.2, you will be
able to communicate with it both from the main computer (because the
Encore's IP is 192.168.0.1) and the laptop (which you will either set to
a static IP of 192.168.0.x where x is greater than 2, or to obtain an IP
automatically).

If you set the laptop to obtain an IP automatically, the ICS DHCP
allocater will set it appropriately. This software is smart enough to
see the IP address of the DI-524 and to make the laptop's IP address
different. ICS also should set the laptop's default gateway and DNS
server to 192.168.0.1 (the address of the Encore).

So, with all of that in mind, access the DI-524 configuration system and
change its IP address to 192.168.0.x, where x is less than 254 and
neither 0, nor 1, nor whatever you might have set as a static address on
the laptop). Leaving the laptop connected to one of the DI-524 LAN
ports, connect a cable between another DI-524 LAN port and the Encore,
and things should finally work. Remember -- you can always reset the
DI-524 to its factory default if things spiral out of control.

Assuming that you can now reach the Internet through the DI-524, have
yourself a caipirinha or three and relax. You can then turn to setting
up security on your new wireless network.

You want to do at least 3 things:

- change the default SSID (the wireless network name) to something
unique (but not your name or address)
- enable the strongest encryption that is compatible with the DI-524 and
the wireless adapter on the laptop
- change the password for accessing the DI-524 configuration.

The major downside to configuring your network in the above manner is
that your main computer -- which controls your connection to the
Internet -- must be on whenever you want to connect to the Internet from
the laptop. That's why my first suggestion was to connect the DI-524
directly to the SS5200. The DI-524 has built-in computational
capability that can connect to most broadband modems. That is the
function of the WAN port. Unfortunately, I don't understand how your
computer is communicating with the SS5200, so I can't tell you how to
configure the DI-524 to do the same. If you could figure this out, the
only hardware that would need to be powered on would be the SS5200 and
the DI-524 and whichever computer you wanted to use to get to the Internet.

Good luck.

P.S. The node type of "mixed" will work, although it's not ideal. See
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

 

[PaulFXH]

Paul,

I think we *are* nearing the finish line.

At the risk of making this long thread even longer, and of giving you
information that you already may know, let me try to explain a little of
what is going on.

There are 3 blocks of IP addresses reserved for use as private networks
(local networks). The block typically used by SOHO LANs is 192.168.0.0
through 192.168.255.255. Such networks can be further subdivided into
"subnets." This is where the "subnet mask" comes in. In order to
communicate directly (without a router), computers must be on the same
subnet. With a subnet mask of 255.255.255.0, and on a LAN using the
192.168.x.y block of addresses, the subnet can be thought of as the
third octet in the address, i.e., "x" in the example. Thus, in order to
communicate directly, devices on such a LAN must have IP addresses in
which the first 3 octets are identical. That is, in your case, all IP
addresses on your LAN must be 192.168.0.y.

Each IP on the LAN must be unique. So, when you got the "conflicting
address" error, you had two devices with the same IP, probably 192.168.0.1.

IP addresses can either be set statically or automatically, using
Dynamic Host Configuration Protocol (DHCP).

Because of the way your Internet access is configured (which I don't
fully understand), your LAN consists of (1) the Encore NIC on the main
computer, (2) the DI-524, and (3) the NIC on the laptop. You have at
least two devices on this LAN that are capable of performing the DHCP
function: Windows ICS running on the Encore and the DHCP server built
into the DI-524.

You don't want two active DHCP servers on the same LAN because of the
danger that they will assign the same IP address to different devices.
Because the DHCP function of ICS can't be turned off or configured, you
must turn off the DHCP server in the DI-524 (as a practical matter, of
course, if all the computers connected through the DI-524 are set with
static IP addresses, it wouldn't matter if you left the DI-524 DHCP
server turned on).

As an aside, if you really were unable to see the DI-524 configuration
login screen when you connected the laptop with the laptop's NIC set to
obtain an IP address automatically, but could see it when you set a
static IP on the laptop, it suggests that the DI-524's DHCP server is
either already turned off or broken.

Another aspect of Windows ICS that cannot be configured is the IP
address that is set on the shared NIC, i.e., on the Encore. ICS forces
the Encore to a static IP address of 192.168.0.1. Seehttp://support.microsoft.com/kb/306126/andhttp://support.microsoft.com/kb/310563/en-usfor moreinformation.

Because the Encore has an IP address of 192.168.0.1 and the default IP
address of the DI-524 is also 192.168.0.1, if you connect the Encore to
one of the LAN jacks of the DI-524, you will get an error message
warning that there are conflicting devices on the network. Thus, you
need to change the IP address of the DI-524. In order to be able to
communicate with this device, its IP address must be in the same
192.168.0.x subnet. If you set the DI-524 to 192.168.0.2, you will be
able to communicate with it both from the main computer (because the
Encore's IP is 192.168.0.1) and the laptop (which you will either set to
a static IP of 192.168.0.x where x is greater than 2, or to obtain an IP
automatically).

If you set the laptop to obtain an IP automatically, the ICS DHCP
allocater will set it appropriately. This software is smart enough to
see the IP address of the DI-524 and to make the laptop's IP address
different. ICS also should set the laptop's default gateway and DNS
server to 192.168.0.1 (the address of the Encore).

So, with all of that in mind, access the DI-524 configuration system and
change its IP address to 192.168.0.x, where x is less than 254 and
neither 0, nor 1, nor whatever you might have set as a static address on
the laptop). Leaving the laptop connected to one of the DI-524 LAN
ports, connect a cable between another DI-524 LAN port and the Encore,
and things should finally work. Remember -- you can always reset the
DI-524 to its factory default if things spiral out of control.

Assuming that you can now reach the Internet through the DI-524, have
yourself a caipirinha or three and relax. You can then turn to setting
up security on your new wireless network.

You want to do at least 3 things:

- change the default SSID (the wireless network name) to something
unique (but not your name or address)
- enable the strongest encryption that is compatible with the DI-524 and
the wireless adapter on the laptop
- change the password for accessing the DI-524 configuration.

The major downside to configuring your network in the above manner is
that your main computer -- which controls your connection to the
Internet -- must be on whenever you want to connect to the Internet from
the laptop. That's why my first suggestion was to connect the DI-524
directly to the SS5200. The DI-524 has built-in computational
capability that can connect to most broadband modems. That is the
function of the WAN port. Unfortunately, I don't understand how your
computer is communicating with the SS5200, so I can't tell you how to
configure the DI-524 to do the same. If you could figure this out, the
only hardware that would need to be powered on would be the SS5200 and
the DI-524 and whichever computer you wanted to use to get to the Internet.

Good luck.

P.S. The node type of "mixed" will work, although it's not ideal. Seehttp://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Well, Lem, I haven't earned those caipirinhas yet but I am trying.
I went into the D-Link configuration wizard and made what I considered
to be appropriate changes to get an internet connection. However, when
I clicked to save changes and restart the DI524, it went into a stall
(up to 30 minutes). So, it just wasn't happy about something.
Incidentally, before I give in detail what I did in the wizard, I will
mention that on the tab marked DHCP in this DI524 "site", it actually
specifies the DHCP server as being enabled.
I don't know if this signifies that this DHCP server is malfunctioning
as you suggested as a possibility.
Nevertheless, I set it to Disabled before proceeding.
I then returned to the Internet Connection Wizard and set the
following:
WAN IP 192.168.0.5 (was 192.168.0.1)
Subnet mask 255.255.255.0 (was the same)
Def. Gateway 192.168.0.1

It then asked for the DNS server addresses from the ISP. I actually
called the ISP twice to confirm these numbers but after being put on
hold for lengthy periods on each occassion, I gave up on this.

Firts I used these DNS addresses which come up when I run "ipconfig/
all" on the desktop:
200.165.132.147
200.165.132.154

It then asks for some security information and then I click to save
and restart the DI524. However, this is where it stalls.

I tried again with only one DNS server address (192.168.0.1 which just
doesn't sound right but that what I get when I run "ipconfig/all" on
the laptop.
However, the result is the same....an interminable stall.

Note that it had been my intention to set the DI524 IP address to
192.168.0.5 (with a static IP of 192.168.0.2 on the laptop) which is
why I set the WAN IP to 192.168.0.5. However, I fear this is my
inexperience coming through and the WAN is something else.
After I couldn't get the configuration to proceed, I click the LAN tab
in the DI524 configuration site. Here I was surprised to find that the
DI524 IP was still set at 192.168.0.1.
So, I changed it to 192.168.0.5
Then I opened another tab and subsequently went back to the LAN tab
and was surprised to find that the DI524 IP was back at 192.168.0.1

So, I'm puzzled and would appreciate any pointers.
Thanks
Paul

 

[Lem]

Well, Lem, I haven't earned those caipirinhas yet but I am trying.
I went into the D-Link configuration wizard and made what I considered
to be appropriate changes to get an internet connection. However, when
I clicked to save changes and restart the DI524, it went into a stall
(up to 30 minutes). So, it just wasn't happy about something.
Incidentally, before I give in detail what I did in the wizard, I will
mention that on the tab marked DHCP in this DI524 "site", it actually
specifies the DHCP server as being enabled.
I don't know if this signifies that this DHCP server is malfunctioning
as you suggested as a possibility.
Nevertheless, I set it to Disabled before proceeding.
I then returned to the Internet Connection Wizard and set the
following:
WAN IP 192.168.0.5 (was 192.168.0.1)
Subnet mask 255.255.255.0 (was the same)
Def. Gateway 192.168.0.1

It then asked for the DNS server addresses from the ISP. I actually
called the ISP twice to confirm these numbers but after being put on
hold for lengthy periods on each occassion, I gave up on this.

Firts I used these DNS addresses which come up when I run "ipconfig/
all" on the desktop:
200.165.132.147
200.165.132.154

It then asks for some security information and then I click to save
and restart the DI524. However, this is where it stalls.

I tried again with only one DNS server address (192.168.0.1 which just
doesn't sound right but that what I get when I run "ipconfig/all" on
the laptop.
However, the result is the same....an interminable stall.

Note that it had been my intention to set the DI524 IP address to
192.168.0.5 (with a static IP of 192.168.0.2 on the laptop) which is
why I set the WAN IP to 192.168.0.5. However, I fear this is my
inexperience coming through and the WAN is something else.
After I couldn't get the configuration to proceed, I click the LAN tab
in the DI524 configuration site. Here I was surprised to find that the
DI524 IP was still set at 192.168.0.1.
So, I changed it to 192.168.0.5
Then I opened another tab and subsequently went back to the LAN tab
and was surprised to find that the DI524 IP was back at 192.168.0.1

So, I'm puzzled and would appreciate any pointers.
Thanks
Paul


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?

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.

 

[PaulFXH]

<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

 

[PaulFXH]

You mean you still haven't picked up enough Portuguese in the stuff I
been sending in this thread?



















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]

You mean you still haven't picked up enough Portuguese in the stuff I
been sending in this thread?





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

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