Re: Network setup problem.
- From: "Jim Carlock" <anonymous@xxxxxxxxx>
- Date: Fri, 05 May 2006 03:34:18 GMT
"George Jetson" <georgeg@xxxxxxxxxx> wrote:
Thanks for the info. I work in the maintenance dept. at the apt
complex. Someone from the main office on the other side of
the state came down last Friday to upgrade the equipment,
but couldn't get it to work. So he left, with a promise to come
back to get it going. He hasn't come back yet. The residents
are starting to bug me to get it running again, so I thought I
would see if I could at least get one of the computers running.
I took a look at the setup, but figured I should know what I
was doing before I started unplugging patch cords.
Switches and hubs work on a seperate layer of the network.
They work with Mac addresses (well the switch does), where-
as routers work on a higher layer (the IP address).
Do the following.
(1) Open a command prompt (cmd.exe).
(2) Type IPCONFIG /RELEASE *
(3) Type IPCONFIG /RENEW *
(4) Type IPCONFIG /ALL
The IPCONFIG /RELEASE * tells the computer to release the
IP address configured. Sometimes network cards assign a bogus
IP address instead of 0.0.0.0. So we want to see 0.0.0.0 or a
valid IP address. The IPCONFIG /RENEW will tell you if the
computer is getting a valid IP address.
If all the computers are getting IP addresses from the router,
then you'll likely see something like:
10.x.x.x for each computer where x can represent any number
between 0 and 255. Feel free to post back with the results of
the IPCONFIG /RENEW. IP numbers should be okay to post,
but I'd avoid posting the MAC address which appears similar
to: 00-00-00-00-00-00 (six two character digits representing
hexadecimal addresses).
When things get sent from a computer to another computer, an
application creates a packet to send to another system and
starts building a list of information so the packet can return
properly. The application adds whatever data it needs, then
moves down adds the routing information, then the IP address,
then the MAC address, then sends it out to the switch which
sends the data directly to the router. This brings up a point
whereby one port on the switch provides a way to uplink
to a modem or router. So that's possibly something you need
to check. Perhaps you're plugged into an uplink where you
should be plugged into a downlink. Typically the uplinks allow
you to stack switches to allow for more connections. Usually
one port on the farthest right or left is an uplink port.
When a switch gets a packet of information it only looks at
the MAC address and routes it to the appropriate system
based upon the MAC address. When a router gets a packet
it looks at the IP address of the package to get delivered.
They're two totally different layers, switches handling MAC
addresses and routers handling IP addresses.
A switch gets confused if two network cards hook up to it
with the same MAC address.
A router gets confused if two systems have the same IP
address.
Personally, I'd check to see which cable is plugged into the
uplink port on the switch and check that out.
Hope that helps.
Jim Carlock
Post replies to the group.
--
Raleigh Swimming Pool Builders http://www.aquaticcreationsnc.com/
.
- References:
- Network setup problem.
- From: George Jetson
- Re: Network setup problem.
- From: Rick
- Re: Network setup problem.
- From: George Jetson
- Re: Network setup problem.
- From: Rick
- Re: Network setup problem.
- From: George Jetson
- Network setup problem.
- Prev by Date: Re: CISCO Re: Firewall Admin Needed!
- Next by Date: Re: Daemon Alert - Nokia
- Previous by thread: Re: Network setup problem.
- Next by thread: Limiting connection scope
- Index(es):
Relevant Pages
|
