dhcp

Hello, we have 6 nodes at work on a LAN that's
routered to a cable router/modem to WAN. The
linksys router has 5 ports and one uplink and one
data port of which goes to the cable modem/router
provided by Brighthouse Road Runner which it
has 4 ports. In other words we have a router and
then we also have an ISP provided cable modem/router
with 4 ports. We run the 5th and 6th nodes by
running an uplink cable from the uplink on the
linksys router to port 1 on the cable modem/router.
We leave the 5th port on the linksys empty since
we are using the uplink.
Here's the problem. We can all see each other
including the problem node. We can all get online to
the internet with the exception of the one problem node.
Not a rotating node problem as we reboot etc. but rather
the same node always can see the rest of the Lan but "no"
online internet or email. So I checked the problem node's
settings. They are the same "except" that his tcp settings have
dhcp off, and it has the alternate address hard coded
as 192.168.1.225. The rest of us by the way upon
pinging all have ip addresses in the 101 thru 105 range.
So I set the problem node to dhcp and took off the
alternate hard code. Rebooted and then he cannot
see us (or get online) nor can we see him. Does
anybody have any clues as to what is going on?

I assume the "problem child" is now configured correctly? Since switching
it to DHCP, did you check that it's using the same IP scope, same gateway,
same DNS server(s), etc., w/ ipconfig.exe??

If it looks kosher, then I suggest flushing its routing tables w/ the
following command:

netsh interface ip delete arpcache

This will force it to reaquire routing information and "learn" the network
topology anew (sometimes network changes are not immediately reflected in
the local PC's routing tables, which can then lead to odd problems like
these).

Jim


"G" <NoMail@NoSpam> wrote in message news:(E-Mail Removed)...
> Hello, we have 6 nodes at work on a LAN that's
> routered to a cable router/modem to WAN. The
> linksys router has 5 ports and one uplink and one
> data port of which goes to the cable modem/router
> provided by Brighthouse Road Runner which it
> has 4 ports. In other words we have a router and
> then we also have an ISP provided cable modem/router
> with 4 ports. We run the 5th and 6th nodes by
> running an uplink cable from the uplink on the
> linksys router to port 1 on the cable modem/router.
> We leave the 5th port on the linksys empty since
> we are using the uplink.
> Here's the problem. We can all see each other
> including the problem node. We can all get online to
> the internet with the exception of the one problem node.
> Not a rotating node problem as we reboot etc. but rather
> the same node always can see the rest of the Lan but "no"
> online internet or email. So I checked the problem node's
> settings. They are the same "except" that his tcp settings have
> dhcp off, and it has the alternate address hard coded
> as 192.168.1.225. The rest of us by the way upon
> pinging all have ip addresses in the 101 thru 105 range.
> So I set the problem node to dhcp and took off the
> alternate hard code. Rebooted and then he cannot
> see us (or get online) nor can we see him. Does
> anybody have any clues as to what is going on?
>
>

>I assume the "problem child" is now configured correctly?
>Since switching it to DHCP, did you check that it's using the
>same IP scope, same gateway, same DNS server(s), etc.,
>w/ ipconfig.exe??
----
Thanks for the reply, you sound like you really know this stuff.
See our Lan was setup by a co-worker's friend before we had
our cable modem/router installed for internet. He did it free etc
and they haven't called him back since he lives in another town.
So between us (we know enough to be dangerous) we are
trying to learn how to get it going since it's just the one node.
We don't really know how to use ipconfig other than reporting
data back from it, and setting up the Lan with dhcp.
---
>If it looks kosher, then I suggest flushing its routing tables w/
>the following command:
>netsh interface ip delete arpcache
>This will force it to reaquire routing information and "learn" the
>network topology anew (sometimes network changes are not
>immediately reflected in the local PC's routing tables, which can
>then lead to odd problems like these). Jim
Thanks again, I will try this Monday at work. This is all new stuff
to me. Can you tell me a book you would recommend to learn
basis network maintence like this?

Don't have any specific books in mind, but a good start is to visit:

http://www.practicallynetworked.com/

It's geared towards the home or small office user. I suggest reviewing some
of the Troubleshooting / Tutorials on the left hand side. There's enough
available at this site that you should be able to grasp some basic
networking concepts.

Jim


"G" <NoMail@NoSpam> wrote in message news:(E-Mail Removed)...
> >I assume the "problem child" is now configured correctly?
> >Since switching it to DHCP, did you check that it's using the
> >same IP scope, same gateway, same DNS server(s), etc.,
> >w/ ipconfig.exe??
> ----
> Thanks for the reply, you sound like you really know this stuff.
> See our Lan was setup by a co-worker's friend before we had
> our cable modem/router installed for internet. He did it free etc
> and they haven't called him back since he lives in another town.
> So between us (we know enough to be dangerous) we are
> trying to learn how to get it going since it's just the one node.
> We don't really know how to use ipconfig other than reporting
> data back from it, and setting up the Lan with dhcp.
> ---
> >If it looks kosher, then I suggest flushing its routing tables w/
> >the following command:
> >netsh interface ip delete arpcache
> >This will force it to reaquire routing information and "learn" the
> >network topology anew (sometimes network changes are not
> >immediately reflected in the local PC's routing tables, which can
> >then lead to odd problems like these). Jim
> Thanks again, I will try this Monday at work. This is all new stuff
> to me. Can you tell me a book you would recommend to learn
> basis network maintence like this?
>
>

Here's another VERY basic networking tutorial, just coincidentally received
the link today when visiting hardocp.com:

http://www.pcstats.com/artvnl.cfm?articleID=1427

Just quickly skimmed it, looks very, very basic, but you gotta crawl before
you can walk, so perhaps it's worth a quick read.

Jim


"G" <NoMail@NoSpam> wrote in message news:(E-Mail Removed)...
> >I assume the "problem child" is now configured correctly?
> >Since switching it to DHCP, did you check that it's using the
> >same IP scope, same gateway, same DNS server(s), etc.,
> >w/ ipconfig.exe??
> ----
> Thanks for the reply, you sound like you really know this stuff.
> See our Lan was setup by a co-worker's friend before we had
> our cable modem/router installed for internet. He did it free etc
> and they haven't called him back since he lives in another town.
> So between us (we know enough to be dangerous) we are
> trying to learn how to get it going since it's just the one node.
> We don't really know how to use ipconfig other than reporting
> data back from it, and setting up the Lan with dhcp.
> ---
> >If it looks kosher, then I suggest flushing its routing tables w/
> >the following command:
> >netsh interface ip delete arpcache
> >This will force it to reaquire routing information and "learn" the
> >network topology anew (sometimes network changes are not
> >immediately reflected in the local PC's routing tables, which can
> >then lead to odd problems like these). Jim
> Thanks again, I will try this Monday at work. This is all new stuff
> to me. Can you tell me a book you would recommend to learn
> basis network maintence like this?
>
>

Thank you very much!
Could I also use the following to do the same thing?
------------------------------
'ipconfig /release' then 'ipconfig /renew'
(for XP and 2000) or 'ipconfig /release_all'
then 'ipconfig /renew_all' (for 98/ME).
instructing all network adapters to drop their current
IP addresses and attempt to acquire new ones.
Type 'ipconfig /all' again and see if this
resolved the problem.
-----------------------------
instead of the
------------------------------
netsh interface ip delete arpcache