Ooh! Ooh! Q's inline below.
At 15:21 10/12/2007 -0400, jmaccraw wrote:
Uh, that would be normal if you changed it's IP to a
10.0.0.x and were trying to
talk to it from either a 192.168.x.y network or as if
it was a 192.168.x.y node.
UNROUTABLE.
Yep. Been here/done this before. Understand. And, why I asked the Q
about what I was reading in the UManual as 'ref'. Appears not....
Router 10.0.0.1, then all clients IP > 10.0.0.1;
Though why you would use a
class A/8 private network in a house is beyond me.
Personally I just use a
192.168. range that is well above the common 0.x or
1.x.
OK. I am not married to the 10.0.0.x IP series. Just that I have used it
since
1999 and my clients and LAN have been error free that I know of.
I have created a remap spreadsheet to change my LAN from "10" to "192".
It may take a couple of days for everybody to settle down but WTF! No biggie.
When you say, "...well above the common 0.x or 1.x." do you mean something
extreme like "192.168.218.101 and up?" Can do this easily..... :)
Am I correct that the standard sub-net mask for the '192' series is
255.255.0.0?
Proper way to do things:
1. Setup your account with a pc->modem direct
connection & make sure it works.
check!
2. THEN access the modem's config & put it in bridge
mode, disable any services
it might still have on.
check! (if I am able to enable bridge mode and disable any remaining services)
3. Unplug the PC & attach a router WAN port to the
modem (linksys, dlink, etc...)
check!
4. Plug PC into the router LAN port in DHCP mode.
check! (...but what if I choose to statically assign my clients IP addies?)
And, I have already disabled my router's DHCP server/function.
5. Browse to the router's IP & login to the setup
page.
check!
6. Setup the router in PPOE mode with your username/PW
combo.
This will have to wait! Do not yet know whether I will be using PPoE.
Last time I did not. Should know for certain on the 16th.
I see no point in DHCP alone since you never know what
machine is getting what
IP and manual IP's are PITA. Better to have your own
DHCP & DNS servers that can
reserve an IP for a machine & map it to a name
consistently.
OK. Yes, I think I understand this. But my network/LAN is not yet
so complex that I have a local DNS server and DHCP server. If/when
I chose to use DHCP, I used my router as that go-to point. The
"who has what IP addy" was initially not a big deal. The lease
release/renew process got to be doggy. Had clients sit for 18 hours
off-net without a new lease. But, this was long ago before all clients
moved up to W2Kpro. So........ :)
Thanks jmaccraw. Sometimes I do not completely comprehend, but most
of the time I do find pearls needed to solve the glitch. Really good stuff!
Best,
Duncan
DHSinclair wrote:
> Yes, Wayne, do understand that the 192.168.x.x
series is one of the 3
> private IP series.
> Order went thru last night. Install kit is due here
10-16-07.
> Excitement increases!
>
> Suppose I'll have to review some more fundamentals.
Yes, the new router
> also came with a
> default IP addy of 192.168.0.1. Correct, I do see
this series used
> mostly on most network
> related equipment. Odd, but until I re-addressed
the router with a
> 10.0.0.x addy, I could not
> speak to it via the browser call of
"http://192.168.0.1/"; from any of my
> LAN clients.
> The browser just sat their and churned until it
finally timed out. I
> found this strange then and
> still do. I will re-test this again today.....
>
> DHCP is disabled in the router, btw. Maybe anal but
I like to assign
> static IPs to my LAN clients.
> I recall using DHCP back in 1999/2000 w/last router
and xdsl and the
> automatic lease release/
> renew business was problematic. Perhaps I give it a
try again for
> S&G's.... :)
>
> Maybe it matters little whatever the internal IP
addy of the new xdsl
> modem may be. Was lead
> to believe that a router is also a "bridge" via its'
WAN side port. Am
> I wrong?
> Best,
> Duncan
>
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
This email scanned for Viruses and Spam by ZCloud.net
