Hi,

I have an SMC 7004ABR V2 Router, a D-Link DSL 300T ethernet modem, and
two PCs.

Both PCs can talk to the Router and each other over the lan. If the
modem is plugged directly into the PCs network cards they can access
the internet but when it is moved to the Wan socket of the router they
can't see the modem or the outside world.

I have no idea how to set this up. Does anyone know/have any guides,
helpful advice, or miracles that I could use?

My adsl account is with Pipex and has a dynamic IP address.

Thanks..

On 28 Sep 2004 in uk.telecom.broadband, Gatecrasher wrote:

The least helpful sugestion I'd make is to replace the router and
modem with a combined unit, such as one from Ebuyer or Dabe but I
guess you wouldn't want to do that at this stage... So how about
providing a list of the IP addresses being used by the kit.. most
significant, I suspect, will be "WAN" IP address for your router,
to see if this would match up with the IP subnet/mask for modem's
"LAN" IP address... Peter M.

Gatecrasher wrote:
The IP address of the DSL 300 modem is 192.168.0.1 and *CANNOT* be altered!
Make sure that your router is pointing at that.
--
paul.g.king@theobviousdsl.pipex.com
Reply address is spamtrapped. Remove theobvious for valid e-mail address

Gatecrasher wrote:
Try this installation guide (although its for the DSL-300G+ flavour):-
ftp://ftp.dlink.co.uk/dsl_routers_mo...-300g+_qig.pdf

You'll need Adobe Acrobat Reader to open it.
Use it "arse about face" ie. start at page 7 and do the router installation,
*THEN* start at page 2 and do the modem installation. Although its talking
about a DI-614 router, yours may be somewhat similar, At least its a
start...

According to
ftp://ftp.dlink.co.uk/dsl_routers_mo...tall_guides.pd
f the default IP for the DSL-300T is 192.168.1.1 and not 192.168.0.1 as per
another post of mine!
--

I've printed no end of guides off the internet this afternoon and none
seem to allow me to make any progress.

The modem ip address is 192.168.1.1 until it connects and then its
81.xxx.xxx.xxx pipex address. The router's lan ip address is
192.168.2.1 and the two pcs are at 192.168.2.100 and 192.168.2.101 .
The router can see the modem once it connected to pipex but I can no
longer access the modem and I can't get onto the net.

There appear to be a lot of other troubled users having problems with
a Dlink 300T and a router. Its the only ethernet modem I could find
at Dabs/Ebuyer.

Any suggestions are appreciated but I'm all for throwing these two
bits of kit in the bin and buying a combined router modem with a
decent firewall set up rather than risk buying another router or modem
that don't get along together.

Thanks...

"Paul King" <pauldotgdotking@nospammarconi.com> wrote in message news:<ydadnRE1x6Ba5MTcRVnygw@pipex.net>...

On 28 Sep 2004 13:43:46 -0700, nigerian_junk@yahoo.co.uk (Gatecrasher)
wrote:

What subnet mask are you using?

If you are using the most common 255.255.255.0, then the 3rd octet
needs to be the same for all devices, so you should change the PCs and
router to something between 192.168.1.2 and 192.168.1.255


--
Alex Heney, Global Villager
If winning isn't important then why keep score?

To reply by email, my address is alexATheneyDOTplusDOTcom

Gatecrasher wrote:
Are you sure? Mine's always 192.168.0.1 (granted that I'm using the 300G+
version - but it *NEVER* changes). If I input http://192.168.0.1 into the
address bar of my Internet Explorer I see the modem. If I then input the IP
of my router (192.168.1.1) I see that too! The 81.xxx.xxx.xxx IP address
from Pipex is passed by the modem to the router - that's your Internet IP
address, but their *BASIC* web-browser interface adresses remain 192.168.0.1
and 192.168.1.1 respectively (my router's IP address is alterable, the
modem's isn't). Incidentally - I run 5 PC's (3 wired and 2 wirelessly) and
their IP addresses are 192.168.1.100 to 192.168.1.104 and the subnet mask
used is 255.255.255.0

You are running your modem and router on two different LAN's! You've got the
router and both 'puters on one LAN (192.168.2.x) and the modem on another
(192.168.1.x) Unless you have a very good reason to do this then - until
it's all working - I'd simplify things by running everything on only one
LAN. Otherwise you get into all sorts of problems with subnet masking which
you probably don't need to bother about.

I'd set your modem (which isn't changeable) to 192.168.1.1. I'd then set
your router to 192.168.1.2, and setup the DHCP server for your PC's (in the
router) to 192.168.1.100 and 192.168.1.101, leaving the subnet mask as
255.255.255.0

Incidentally, and pardon me for teaching you to suck eggs if you already
know this, but you do realise that you have to switch on the modem *first*
and let it synchronise to the ADSL line BEFORE you power on the router?
Otherwise the router can get its knickers in a twist and lockout access to
the modem! That's the advice from D-Link anyway...

--
paul.g.king@theobviousdsl.pipex.com
Reply address is spamtrapped. Remove theobvious for valid e-mail address

On Tue, 28 Sep 2004 13:43:46 -0700, Gatecrasher wrote:

This I guess where you problem is, having the modem and router not in the
same subnet. Change either the modem LAN IP or the router LAN IP to be in
the same subnet.

I tried changing the IP address of the Lan to 192.168.1.50 and the
first PC to 192.168.1.100 last night but it didn't make any
difference.

Once the modem is up and running I've found it impossible to see
through the router from my PC although the router can see it and give
its IP number as an 81.xxx.xxx.xxx pipex one but I can't access the
admin web page at 192.168.1.1. The router remains accessible
throughout.

I didn't know about setting the modem up first before powering on the
router. Would the modem connect through the Wan of the router or
directly into the network card when I set it up? Might play with that
tonight if I'm allowed.


But I suspect the combination of an SMC7004ABR and a DLink 300T either
doesn't work or my newbie knowledge is insufficient to get it working.

Thanks... This is all helping to calm me down.




"Paul King" <paul.g.king@theobviousdsl.pipex.com> wrote in message news:<1096415790.ZgMu5lwgdmroBFPOQLYtOQ@teranews>. ..

Gatecrasher wrote:
Lets go back to first principles. Plug the modem DIRECTLY into the LAN port
of a PC and then - in Internet Exploder or whatever - type in
http://192.168.1.1 in the address bar to access the modem. Now *CHECK VERY
CAREFULLY* that the modem is not set in BRIDGE mode. If it is in bridge
mode, you will not be able to see it once it is connected to the router! I
use mine in bridge mode and cannot control (or fiddle with) it unless I
first disconnect it from the router WAN port and connect it to a PC
directly.
--
paul.g.king@theobviousdsl.pipex.com
Reply address is spamtrapped. Remove theobvious for valid e-mail address

Thanks for the ongoing support and I may try again over the weekend.
Incidentally, I know the modem is not in bridge mode because I tried
that with no luck and then did a factory reset.

In the meantime I've had delivered a cheap Ebuyer special, a Safecom
(Origo) 4 port router/modem. It took 5 minutes to set up and the
internet works on both PCs and they can talk to each other. I should
have gone with this option in the first place only my original
thinking was a router for the home network with a print server and a
dial up connection (SMC7004ABR). ADSL followed on a couple of days
later and led me to the DLink 300T.

Thanks...




"Paul King" <paul.g.king@theobviousdsl.pipex.com> wrote in message news:<1096543885.qN6+hwTBKG7XjZVbflCgeA@teranews>. ..

Gatecrasher wrote:
Well, at least you are now up and running (if a little more out of pocket!)

--
paul.g.king@theobviousdsl.pipex.com
Reply address is spamtrapped. Remove theobvious for valid e-mail address

I just wrote a similar request to yours - sorry I didn't check the posts
more careful, I could have piggybacked on yours :-)

In any case, should your problem be solved, please share it here - you might
just help me with my own (apparently very similar) problem.

An odd thing is that I remember that I read in my router manual to switch on
the modem last - I guess I must be mistaken, next thing I'll try is follow
the advice you've gotten here.

Roscoe

Roscoe,

I didn't get a chance to try out over the weekend the helpful advice
concering changing the subnet so can't report whether it works.

If you make any progress please do let me know either through throug
the newsgroup of via email.

Currently struggling to get my head around port forwarding and NAT so
I can use bit torrent on my Origo based router/modem.

" Roscoe" <nospam@asm.org> wrote in message news:<2sadgnF1h3e4sU1@uni-berlin.de>...