How to connect DIRECway DW6000 to my network

I had a line-of-sight wireless DSL setup.  From the dish to their box, then CAT5 to my router (NetGear),
then router ports to my 4 computers.  OK, but that line-of-sight wireless DSL was flakey, so now I got
DIRECway satellite internet installed.  The installer won't do networking.  It works if I plug their box into
a single computer, but I can't get their box to talk to my router.

The direcway box (it's called a DW6000) came with a peice of paper saying it's IP address is which happens to be the IP (LAN) address that my router is set to.  Now, how should I
connect the two?  I can log onto the router and I've tried a few guesses at configuring, but I don't
really know the basics of networking.

Since the satellite box says it is, I tried configureing the Netgear router to be,
and then the computers on my local network are numbers like  (and 12, and 13, and 14).
Didn't work.

Then I tried just setting everything to "dyanmic", but that didn't work either.

I need some guidance.  I need a view of what the overall plan should be, and I need some way to
be able to tell which bits are working.  (one friend told me to "ping" things, but thats the only
guidance I've had so far).  I know how to ping the router, and that works.  Don't know how to
ping thru to the satellite modem box.

Anyone want to walk me through this?  Thanks!
Who is Participating?
RLGSCConnect With a Mentor Commented:

You may or may not be able to ping the satellite box, it depends on the configuration they set it to.

First, if the satellite box has an address of, then it is also a firewall/proxy/router. For safety's sake, use your own router (I assume you are referring to one of the appliance type broadband firewalls/routers that are widely available; you did not mention a make and model number).

Generally, you can nest these devices (although it can be confusing at times).

- To avoid confusion, set your router to use DHCP to assign addresses in the 192.168.1.* address block (it reduces confusion in your notes, if nothing else)

- Set your router to automatically obtain its WAN address. Connect the WAN port of your router to the LAN port of the satellite box. The satellite box will most likely assign an address to your router's external port (likely

- Check the Status page on the Management menu for your router. It should show the WAN side of the connection with an address, network mask, etc.

- You should now be able to resolve addresses of well known sites using NSLOOKUP (from the C:> prompt; try,, If you are not familiar with NSLOOKUP, you can try directly using your favorite browser to access the web pages, but it involves more infrastructure and is less clear).

Things should now work.

I hope that the above is helpful.

- Bob (aka RLGSC)
Bob's comment is the correct setup to follow (most secure).

However if you somehow fail to complete Bob's steps and give up then just do the following (as a last resort).

Perform one of your previous steps below.
>>Since the satellite box says it is, I tried configureing the Netgear router to be,
and then the computers on my local network are numbers like  (and 12, and 13, and 14).

Then add a default Gateway of  to each of your computers and  plug the satelllite into the router ports (not WAN port).  Voila! Internet should be working.  

Also on the piece of paper that the satellite came with, there should be two DNS addresses.  You need to add these in each of your computers.  
Like so many things.. so many ways....

Notice that the satellite is a private address, you can't be reached by the general internet, only those on the satillite network.. it's one of the reason's I didn't go with that type of connection and still deal with slow ISDN.

Anyway.. because of that limiting your exposure.. you could hook it to one pc.. put a second nic in that pc to the your hub.. and turn on Internet sharing...
install software like zone alarm to catch any one on the satillite network trying to get you and notify directway about it..
this should get you going...
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

tullheadAuthor Commented:

I am trying to follow your suggestions.  In trying to make the router dynamically assign addresses
in the block 192.168.1.*  I have a problem -- it seems not to do it.  I type that in, say "apply" and
after a pause the router page refreshes with the 0 back in that 3rd slot.

I have a NetGear router, quite new -- the kind with 4 wired ports and also wireless antennas.  I'm
only using the wired ports so far.

I captured 3 of the router config pages to show you how I've tried to set it up -- they can
be viewed at   ---- at the bottom of that page I circled in red
where I tried to set up the DHCP assignment of address on my local lan to be in 192.168.1.*

What to try next?

Before you can change the DHCP range, you need to change the "local address" range (, at the top of the page (not circled).

BTW, to refer to the comment by Tele Tech, it is probable that each and every customer of the satellite service is getting an address of, the service provider's box is proxying addresses.

I hope that the above is helpful.

- Bob (aka RLGSC)
yep I fully agree.. it is a private network.  And I can see the use of the router..

However that does not change the scenerio that I suggested....

This is setting up a private network within a private network...

How about changing your interanal address scheme completely  move off the 192  leave that for the router WAN port and setup a completely different internal address scheme... no conflicts.
Tele tech,

Actually, as long as the segments of the internal address space do not overmap, it is not a problem. Since the gateway is aware of what it is what, it seldom gets confused, although the humans running it are less easily dealt with (smile).

The beauty of the Internal addresses (RFC 1918, see is that the individual parts of the range, when used with appropriate subnet masks (in the case of blocks of 255 using the 192.168.x.* addresses with a mask of there is absolutely no problem with using 192.168.0.* and 192.168.1.*.

I hope that the above is helpful.

- Bob (aka RLGSC)
I realized that.. I was thinking of human use and making easier to understand the configuration and routing for trouble shooting and that he is having trouble getting the router to accept the configuration.

by seeing it in two visibly distinct configuration for "external" vs. the "internal" just makes working through it a little easier...

for those of us who do it, and yet don't like to fry the brain.....

Tele tech,

My point exactly. 192.168.0.* IS different than 192.168.1.* (or anything other range in the superblock 192.168.*.0; albeit the terminology is somewhat obsolete, RFC 1918 provides the entire group of 255 Class C networks in the range 192.168.*.* as private IPs; there is another group of Class B and Class A addresses, but the effect is sufficient if he uses 192.168.1.*).

- Bob (aka RLGSC)
tullheadAuthor Commented:
RLGSC --  It works!  Thanks for your help!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.