Efficient 5861 setup

That's it, I am giving up! Can anyone help me set up one of those
BT-badged Efficient 5861s. I just got one off eBay and I can't even get
to the web interface. I ordered my ADSL from plus.net and I'm awaiting
activation but I thought I could at least get to the modem setup in the
meanwhile. The modem came with a yellow Ethernet cable (not the red one
mentioned in the manual -- is that important?) and a console
cable-to-serial adapter.

I reset it, connected the Ethernet cable to port 1 and followed the vague
instructions of the online pdf manual (and the info at
<http://www.farina1.com/5861/>). The PWR and LINK lights are green; the
TEST and LANT lights are blinking green. There is now a Local Area
Connection 2 icon on the System Tray which claims there is a connection
at 10Mbps.

I tried to connect to 192.168.254.254 via a browser (after I disabled the
proxy for this address), telnet and the GUI application. No luck! It's
probably something to do with the TCP/IP stack, subnets, DHCP, or
generally the Local Area Connection 2 connectoid setup in Network and
Dialup Connections (Win2K).

Any ideas? I take it I don't have to wait until the line is activated to
get to the modem setup.

TIA

--
Michael Klontzas
Before enlightenment / chopping wood / carrying water
After enlightenment / chopping wood / carrying water
Zen Proverb

On Wed, 27 Aug 2003 16:04:40 +0100, Peter Watson <(E-Mail Removed)>
wrote:

>In article <(E-Mail Removed)>, Michael-from0
>@glocal.demon.co.uk says...
>>
>> I tried to connect to 192.168.254.254 via a browser (after I disabled the
>> proxy for this address), telnet and the GUI application. No luck! It's
>> probably something to do with the TCP/IP stack, subnets, DHCP, or
>> generally the Local Area Connection 2 connectoid setup in Network and
>> Dialup Connections (Win2K).
>>
>What IP settings have you put in your PC? What is the output of typing
>'ipconfig' in a Command window?

C:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.62.120
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

C:\>ping 192.168.254.254

Pinging 192.168.254.254 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 192.168.254.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

>Try manually setting your PC IP address to 192.168.254.253 with a subnet
>mask of 255.255.255.0 and then try 'ping 192.168.254.254' in a Command
>window...

are you sure you 192.168.254.253 (instead of 192.168.254.254)?

********** [after changing IP to 192.168.254.253]

C:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.254.253
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

C:\>ping 192.168.254.254

Pinging 192.168.254.254 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.254.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.254.253

Pinging 192.168.254.253 with 32 bytes of data:

Reply from 192.168.254.253: bytes=32 time<10ms TTL=128
Reply from 192.168.254.253: bytes=32 time=10ms TTL=128
Reply from 192.168.254.253: bytes=32 time<10ms TTL=128
Reply from 192.168.254.253: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.254.253:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 2ms

C:\>telnet 192.168.254.253
Connecting To 192.168.254.253...Could not open a connection to host on
port 23 :
Connect failed

C:\>telnet 192.168.254.254
Connecting To 192.168.254.254...Could not open a connection to host on
port 23 :
Connect failed

----------
Err, now what?

--
Michael Klontzas
Before enlightenment / chopping wood / carrying water
After enlightenment / chopping wood / carrying water
Zen Proverb

In article <(E-Mail Removed)>, Michael-from0
@glocal.demon.co.uk says...
>
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . :
> Autoconfiguration IP Address. . . : 169.254.62.120
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . :
>
this means that your PC was set to obtain an IP address automatically
via DHCP but it couldn't find a DHCP server. In summary either the
Router is not configured as a DHCP server or you have a defective
Ethernet lead.

> ********** [after changing IP to 192.168.254.253]
>
> C:\>ipconfig
>
> Windows 2000 IP Configuration
>
> Ethernet adapter Local Area Connection 2:
>
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.254.253
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
> C:\>ping 192.168.254.254
>
> Pinging 192.168.254.254 with 32 bytes of data:
>
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.

this means that either the Router isn't on 192.168.254.254 or you have a
defective Ethernet lead.

I'm not familiar with the Router you've got, but does the manual have
any info about access via the console serial port?

Where did the Router come from? Is it from an ex-BT installation?

Have a look at:

http://www.eusty.nildram.co.uk/flash.htm

and the other pages on the site for some more help...

Peter

Michael Klontzas <Michael-(E-Mail Removed)> wrote:

> On Wed, 27 Aug 2003 17:51:54 GMT, "obsidian"
> <(E-Mail Removed)> wrote:
>
> >If what Peter says produces no results, try
> >setting your computer to DHCP mode
>
> sorry to be thick, but how do you do that?
>

Hi,
I'm not familier with this router, but the BT badged ones have crippled
firmware in them that does not use a web interface. You can upgrade the
router to the standard firmware by following these instructions
http://www.farina1.com/5861/5861-Configuration.htm Once you have done this,
the web interface should be available for configuration. Hope that helps.

--

Martin

On Wed, 27 Aug 2003 22:15:56 +0100, Martin Cooper <(E-Mail Removed)>
wrote:

>Michael Klontzas <Michael-(E-Mail Removed)> wrote:
>
>> On Wed, 27 Aug 2003 17:51:54 GMT, "obsidian"
>> <(E-Mail Removed)> wrote:
>>
>> >If what Peter says produces no results, try
>> >setting your computer to DHCP mode
>>
>> sorry to be thick, but how do you do that?
>>
>
>Hi,
> I'm not familier with this router, but the BT badged ones have crippled
>firmware in them that does not use a web interface. You can upgrade the
>router to the standard firmware by following these instructions
>http://www.farina1.com/5861/5861-Configuration.htm Once you have done this,
>the web interface should be available for configuration. Hope that helps.

I was reassured by the seller the router was flashed with the latest
firmware and of course the crippling theory doesn't explain why telnet
and GUI wouldn't work. However a combination of upgrading to the latest
firmware all over again (just in case), rebooting the PC and resetting
ZoneAlarm did the trick! I am not sure which one(s) of these had an
effect (apart from setting up the IP address properly as Peter suggested)
but ZA was indeed quietly blocking things in the background for no
apparent reason. Resetting ZA allowed the pieces to fall in the right
place. Now web interface, telnet and GUI seem to work fine. I'll be sure
when ADSL is actually activated.

Thanks everyone for your help. Much appreciated.

--
Michael Klontzas
Before enlightenment / chopping wood / carrying water
After enlightenment / chopping wood / carrying water
Zen Proverb

On Thu, 28 Aug 2003 01:47:47 +0100, Michael Klontzas
<Michael-(E-Mail Removed)> wrote:

>I was reassured by the seller the router was flashed with the latest
>firmware and of course the crippling theory doesn't explain why telnet
>and GUI wouldn't work. However a combination of upgrading to the latest

Yes it would, telnet and GUI access are not available with the BT
firmware.

>firmware all over again (just in case), rebooting the PC and resetting
>ZoneAlarm did the trick! I am not sure which one(s) of these had an

Glad you got it sorted.
--
Andy Norman (E-Mail Removed)
http://www.norman.cx/

On Thu, 28 Aug 2003 01:47:47 +0100, Michael Klontzas
<Michael-(E-Mail Removed)> wrote:
>I'll be sure when ADSL is actually activated.

Well, now ADSL is activated and surprise-surprise, I can't get it to
work! I have the feeling I'm close though because the router appears to
connect and reports info it picks up from plus.net. Can anyone guess what
I'm doing wrong?

Here are the facts:
* Efficient 5861 router (BT badged but flashed to latest firmware
v5.3.140, so it now works as it's meant to, complete with web/telnet
interface, GUI configuration etc); Win2K; Realtek RTL8029(AS) PCI
Ethernet Adapter.

* Under 'Network and Dial-up Connections' I have various dialup
connectoids for different ISPs and a 'Local Area Connection 2'
connectoid. Attempts to 'Make New Connection' over LAN are ignored by
Win2K. The info in 'Local Area Connection 2' is:
Connect using:
Realtek RTL8029(AS) PCI Ethernet Adapter
Components (all ticked):
Clients for Microsoft Networking
File and Printer Sharing for Microsoft Networks
Internet Protocol (TCP/IP)
Use the following IP address:
IP address: 192.168.254.253
Subnet mask: 255.255.255.0
Default gateway: 192.168.254.254
Use the following DNS server addresses:
(blank but not greyed-out)
(the 'obtain automatically options' cause the
router to become unreachable)

* Router configuration summary (as reported by the router):
LAN IP Address 192.168.254.254
WAN Data PVC 0*38
WAN Protocol PPP
#WAN Connection Speed DOWN 576Kb/s : UP 285Kb/s
Bridging disabled
IP Routing enabled
# WAN IP Address 81.174.180.126
WAN Gateway 0.0.0.0
# DNS Server Address 212.159.13.49 : 212.159.13.50
Address Translation disabled

'#' indicates info the router picked up automatically, so I must be doing
something right. The info appears to be valid too:
212.159.13.49 --> pth-cdns-01.plus.net
212.159.13.50 --> pth-cdns-02.plus.net
81.174.180.126 --> glocal.plus.com

Pinging 81.174.180.126 (i.e. my host) works, however anything beyond that
fails as unreachable or because DNS resolution doesn't work.

Any ideas?

TIA

--
Michael Klontzas
Before enlightenment / chopping wood / carrying water
After enlightenment / chopping wood / carrying water
Zen Proverb

On Tue, 02 Sep 2003 02:53:44 +0100, Michael Klontzas
<Michael-(E-Mail Removed)> wrote:

> Use the following DNS server addresses:
> (blank but not greyed-out)

That will cause you problems.

> (the 'obtain automatically options' cause the
> router to become unreachable)

Probably because you haven't setup DHCP on the router.

>212.159.13.49 --> pth-cdns-01.plus.net
>212.159.13.50 --> pth-cdns-02.plus.net
>81.174.180.126 --> glocal.plus.com
>
>Pinging 81.174.180.126 (i.e. my host) works, however anything beyond that
>fails as unreachable or because DNS resolution doesn't work.

So it looks like the root of your problem is that you PC doesn't know
what it's DNS servers are.

Either you need to configure DHCP on the router and set the PC to get
it's network settings automatically, or alternatively just set the DNS
servers in the local network entry on the PC.
--
Andy Norman (E-Mail Removed)
http://www.norman.cx/

If you are using a private IP address on your LAN (your PC) which it appears
you are, you won't connect to addresses outside your subnet (ie the
internet) without NAT. You must enable address translation on the router
(NAT) or it will not work. The settings the 5861 has automatically detected
(the DNS servers & WAN IP address) are OK, there's no need to make any
alterations to those settings.

Hope This Helps

Rob



"Michael Klontzas" <Michael-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Thu, 28 Aug 2003 01:47:47 +0100, Michael Klontzas
> <Michael-(E-Mail Removed)> wrote:
> >I'll be sure when ADSL is actually activated.
>
> Well, now ADSL is activated and surprise-surprise, I can't get it to
> work! I have the feeling I'm close though because the router appears to
> connect and reports info it picks up from plus.net. Can anyone guess what
> I'm doing wrong?
>
> Here are the facts:
> * Efficient 5861 router (BT badged but flashed to latest firmware
> v5.3.140, so it now works as it's meant to, complete with web/telnet
> interface, GUI configuration etc); Win2K; Realtek RTL8029(AS) PCI
> Ethernet Adapter.
>
> * Under 'Network and Dial-up Connections' I have various dialup
> connectoids for different ISPs and a 'Local Area Connection 2'
> connectoid. Attempts to 'Make New Connection' over LAN are ignored by
> Win2K. The info in 'Local Area Connection 2' is:
> Connect using:
> Realtek RTL8029(AS) PCI Ethernet Adapter
> Components (all ticked):
> Clients for Microsoft Networking
> File and Printer Sharing for Microsoft Networks
> Internet Protocol (TCP/IP)
> Use the following IP address:
> IP address: 192.168.254.253
> Subnet mask: 255.255.255.0
> Default gateway: 192.168.254.254
> Use the following DNS server addresses:
> (blank but not greyed-out)
> (the 'obtain automatically options' cause the
> router to become unreachable)
>
> * Router configuration summary (as reported by the router):
> LAN IP Address 192.168.254.254
> WAN Data PVC 0*38
> WAN Protocol PPP
> #WAN Connection Speed DOWN 576Kb/s : UP 285Kb/s
> Bridging disabled
> IP Routing enabled
> # WAN IP Address 81.174.180.126
> WAN Gateway 0.0.0.0
> # DNS Server Address 212.159.13.49 : 212.159.13.50
> Address Translation disabled
>
> '#' indicates info the router picked up automatically, so I must be doing
> something right. The info appears to be valid too:
> 212.159.13.49 --> pth-cdns-01.plus.net
> 212.159.13.50 --> pth-cdns-02.plus.net
> 81.174.180.126 --> glocal.plus.com
>
> Pinging 81.174.180.126 (i.e. my host) works, however anything beyond that
> fails as unreachable or because DNS resolution doesn't work.
>
> Any ideas?
>
> TIA
>
> --
> Michael Klontzas
> Before enlightenment / chopping wood / carrying water
> After enlightenment / chopping wood / carrying water
> Zen Proverb

On Tue, 02 Sep 2003 08:43:57 +0100, Andrew Norman <(E-Mail Removed)> wrote:
>Either you need to configure DHCP on the router and set the PC to get
>it's network settings automatically, or alternatively just set the DNS
>servers in the local network entry on the PC.

Still at it! Frankly, I don't have a clue what is going on any more. I
tried all sorts of combinations and I'm beginning to think it's actually
the data cable. The router came with a yellow ethernet cable which I
connected to one of the four ports. The plastic bag the cable came in
says:

'1M CAT-5e PATCH LEAD (FLUSH BOOT) [YELLOW] SINGLE'

The router instructions however keep referring to some 'straight-through
cable (red label)' for this type of connection. As I found out both
straight-through and crossover cables are called 'patch leads' and both
types come in a range of colours. So, how can I tell what sort of cable I
have?

Do you think this might be causing the problem? In that case, shouldn't
any communication between PC and router, and between router and plus.net
fail completely? If it is essential and this is not a straight-through
lead, how come the router communicates with PC and ISP?

--
Michael Klontzas
Before enlightenment / chopping wood / carrying water
After enlightenment / chopping wood / carrying water
Zen Proverb