Setting up local network with router.

  • Thread starter Thread starter mm
  • Start date Start date
M

mm

Setting up local network with router. I have a win98 computer on
board, but I can't get the win2000 computer to work. It doesn't
communicate with the other computer (except a tiny bit with some
settings, and it won't access the net.) Is there something unusual
about win2000?

I'll give lots more details tomorrow if you want, but I thought there
might be someone that is well known and often causes trouble.

It's a D-Link DI-524 router.
 
Setting up local network with router. I have a win98SE computer on
board, but I can't get the win2000 computer to work. It doesn't
communicate with the other computer (except a tiny bit with some
Click to expand...

And the win2000 isn't recognized by the router, like the win98SE is.
 
You'll want tcp/ip bound to the adapter. Please post unedited

ipconfig /all


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Setting up local network with router.   I have a win98 computer on
board, but I can't get the win2000 computer to work.  It doesn't
communicate with the other computer (except a tiny bit with some
settings, and it won't access the net.)   Is there something unusual
about win2000?  

It's a D-Link DI-524 router.
Click to expand...

I have the exact same router, but that's likely not the problem. I
speculate that the two PCs are at IP addresses that are not on the
same subnet. Do "ipconfig /all" on both machines and post the results
back here.

I prefer to set up each PC to use DHCP. In network properties, select
Internet Protocol (TCP/IP) and click on Properties. Set each PC to
obtain an IP address and a DNS server automatically. The DI-524 will
then assign them both compatible addresses.

I prefer to then go to the router's setup and manually assign a fixed
IP address for each machine on the network, but that's optional if
you're not comfortable modifying the router config. But highly useful
to make sure each machine always comes up at the same IP address
regardless of the order things are turned on.

Steve Hendrix
 
I have the exact same router, but that's likely not the problem. I
Okay.

speculate that the two PCs are at IP addresses that are not on the
same subnet. Do "ipconfig /all" on both machines and post the results
back here.
Okay.

I prefer to set up each PC to use DHCP. In network properties, select
Internet Protocol (TCP/IP) and click on Properties. Set each PC to
obtain an IP address and a DNS server automatically. The DI-524 will
then assign them both compatible addresses.
Click to expand...

I have both computers set to obtain those two things automatically.
When connected to the router, everything works for the win98 computer,
but for the win2000 computer, it doesn't work.

When the win2000 is connected directly to the DSL modem, no router,
that works fine!

Here is the ipconfig when connected to the DSL modem, which works:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : red
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : myhome.westell.com

Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : 3Com 3C920B-EMB Integrated
Fast Ethernet Controller
Physical Address. . . . . . . . . : 00-26-54-08-AB-8F

Ethernet adapter Local Area Connection 1:
Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : NVIDIA nForce MCP
Networking Adapter
Physical Address. . . . . . . . . : 00-0C-6E-13-85-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.47
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
Lease Obtained. . . . . . . . . . : Monday, September 14, 2009
6:15:59 PM
Lease Expires . . . . . . . . . . : Tuesday, September 15,
2009 6:15:59 PM

Connected to the router instead, which doesn't work, I get:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : red
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : 3Com 3C920B-EMB Integrated
Fast Ethernet Controller
Physical Address. . . . . . . . . : 00-26-54-08-AB-8F

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce MCP
Networking Adapter
Physical Address. . . . . . . . . : 00-0C-6E-13-85-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.171.234
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
I prefer to then go to the router's setup and manually assign a fixed
IP address for each machine on the network, but that's optional if
you're not comfortable modifying the router config. But highly useful
Click to expand...

I might do that**, but as I understand you, I first have to get the
prior step to work.
to make sure each machine always comes up at the same IP address
regardless of the order things are turned on.
Click to expand...

**Yes, I can see how that could be a problem that would cause me to do
it your way. :)
 
You probably have a crossover cable when connected to modem. You need a
straight cable to connect to router.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
You probably have a crossover cable when connected to modem. You need a
straight cable to connect to router.
Click to expand...

I doubt a crossover cable is the problem, as the D-Link router has
automatic crossover as needed. Could be that that feature can be
turned off, but I doubt you would have done that.

However, I'd still focus on the physical connection. The ipconfig you
show when connected to the router shows a default Windows-supplied IP
address that it uses when it can't find a DHCP server. Ain't gonna'
work! I note also that:

A) You have a motherboard ethernet connection that you aren't using.
What happens if you connect thru that? More likely, you're going to
need to disable the onboard ethernet in the BIOS setup screen; I've
seen those interfere.

B) The Nvidia ethernet card shows up as "Lan Connection 1" when
connected to the modem, but just as "Lan connection" when connected to
the router.

Somehow you're not connecting to the router at all, probably a cable
or connector problem. Any chance you're trying to plug into the WAN
side of the D-Link?

Steve Hendrix
 
I have the exact same router, but that's likely not the problem. I
speculate that the two PCs are at IP addresses that are not on the
same subnet. Do "ipconfig /all" on both machines and post the results
back here.

I prefer to set up each PC to use DHCP. In network properties, select
Internet Protocol (TCP/IP) and click on Properties. Set each PC to
obtain an IP address and a DNS server automatically. The DI-524 will
then assign them both compatible addresses.

I prefer to then go to the router's setup and manually assign a fixed
IP address for each machine on the network, but that's optional if
you're not comfortable modifying the router config. But highly useful
to make sure each machine always comes up at the same IP address
regardless of the order things are turned on.

Steve Hendrix
Click to expand...

Steve and everyone, I have another strange question. I read on a
couple webpages thatmy ISP, Verizon, uses DHCP in the western part of
the US, and PPPoE in the eastern part. I'm in the east, Baltimore.

In addition, when I figured out how to log into my Westell DSL modem,
it said it had a PPP connection.

Also, the westell datasheet for the westell modem Verizon gave me says
"ProLine employs industry-proven Point to Point Protocol over Ethernet
(PPPoE) for connectivity, and local networks are easily supported
through the use of Network Address Translation (NAT) and Dynamic Host
Control Protocol (DHCP). ProLine eliminates the need to load PPPoE on
each of the networked computers."

BUT!!!! On the Home/Wan page of the router url, I am supposed to
choose my WAN settings "Please select the appropriate option to
connect to your ISP." and I don't know why but I have been using
"Dynamic IP Address" (DHCP?), about which it says "Choose this option
to obtain an IP address automatically from your ISP. (For most Cable
modem users)".

So since I don't have cable but I have DSL, how come my router at
least is not using "PPPoE Choose this option if your ISP uses PPPoE.
(For most DSL users)"?

Of course, when I tried to use that, and changed nothing else, none of
the internet programs could retrieve data.

What are you using?


(I"m also not using "Static IP Address Choose this option to
set static IP information provided to you by your ISP."
or
"Others PPTP (for Europe use only)
BigPond Cable (for Australia use only)", but that I
understand. :) )
 
mm wrote:

Of course, when I tried to use that, and changed nothing else, none of
the internet programs could retrieve data.

What are you using?
Click to expand...

Home DSL connections normally (if there is any such thing as "normal")
use PPPOE and it certainly sounds that way in your case. You need to
setup the router to a static IP (perhaps 192.168.0.1 or whatever the
default is). Setup the WAN portion of your router with PPPOE and your
login credentials. The LAN portion should be set up as a DHCP server and
the workstations to Get an IP automatically.

Somewhere in the router setup you will need to set the address of at
least a primary DNS server and preferably a secondary. This should be
whatever your ISP provides. In the workstations the DNS server is set to
point to the router IP (this may be done automatically if you set DHCP -
I can't recall).

If you had the router set up (on the WAN) to DHCP, it may be configured
with may be some other settings that don't suit PPPOE. If I were you I'd
read the manual and set it back to factory defaults before doing the
setup. Usually they assume your will setup with PPPOE and set the other
options to something that will at least work. Mostly, from factory
default, the setup is simple - just a matter of configuring the PPPOE.
 
You're mixing apples and oranges with PPPoE and DHCP. Let me try to
simplify (well, at least clarify) a bit:

There are three separate LAN segments (networks) involved in what
you've described so far:

1) The network between your DSL modem and your internet service
provider. This is the place where PPPoE is involved. This segment
should also be set to automatically get an IP address from the ISP; I
believe but I'm not sure, that this is automatically implied in PPPoE;
it's similar to using DHCP. This will determine the IP address seen by
the outside world for your entire location.

2) The network segment between the DSL modem and the D-Link router.
The DSL modem acts as a DHCP server for this segment (even though it's
a DHCP client on the Internet side), and probably assigns itself an
address like 192.168.1.1. If everything is at factory defaults, it
will probably assign something like 192.168.1.50 as the WAN-side
address of the D-Link. This cable should be plugged to the WAN port of
the D-Link.

3) The network on the LAN side of the D-Link (the four similar plugs
on the back of it, plus the wireless network). Here's where you
probably need to change the factory settings. On the D-Link, try
setting the LAN side address to something like 172.16.0.1, subnet to
255.255.255.0. Now your PCs will be assigned starting at 172.16.0.50
or something like that and incrementing upward in the last number.

Both the DSL modem and the D-Link router act as NAT routers. Suppose I
use my PC at 172.16.0.50 to request a web page from www.google.com.
DNS is used in a chain to find that the IP address is 64.233.169.104;
the chain thru the segments isn't of particular interest here. Now the
PC requests a web page from 64.233.169.104. The request goes to the
"gateway" configured into the PC via DHCP, 172.16.0.1 - thus the
request goes to the D-Link router. The router sees that we're looking
for a publicly routable address that isn't on our network segment, so
"translates" the address to the next gateway up the line, and sends it
to 192.168.1.1 - the DSL modem, while noting that the request came
from 172.16.0.50. The same NAT process takes place in the DSL modem,
which also notes that the request came from 192.168.1.50 (the WAN-side
address of the router). The request now goes out onto the public
internet. When the reply comes back from Google, the DSL modem looks
to see who requested it, and sends the reply to 192.168.1.50 (the
router). Similarly, the router then translates the address back to who
requested it, 172.16.0.50, and sends it to your PC.

The segment between the DSL modem and the router needs to be on a
different subnet than the network between your PCs and the router, and
the modem needs to be plugged to the WAN port of the router. This
whole process is why a NAT router inherently makes a pretty decent
firewall. If an unsolicited packet comes in from the internet, the
router has no place to send it, so the packet gets discarded. Port
forwarding is another whole topic, and is how you'd configure things
to allow access to a server you might wish to put up on your network.

Steve Hendrix
 
Back
Top