Win2k workstation recognizes network, won't pull IP

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm in the middle of upgrading the network for a retail store which uses a
newer IBM PC as its point-of-sale/cash register. The workstation is running
Win2k, and has been operating wirelessly with the router in the back of the
store for several months through a USB wireless adapter.
Last week I ran an ethernet line around the perimiter of the store to
hardwire the connection, and this week I was given the administrator password
on the machine so I could enable the integrated ethernet adaptor. The
computer now recognizes that it is plugged in and connected to a fast
ethernet (100 Mb/s) switch, but doesn't pull an IP address. In fact, it
doesn't receive any data whatsoever. It almost seems as though what it's
sending to the switch in the back isn't getting there. I'd roughly estimate
the cable length is somewhere between 100' and 125', but it has checked out
fine on my line tester, telling me there is no problem with the terminators
or a cut in the cable somewhere.
I've never run into an issue like this, and I have no idea how to go about
resolving it. Anyone have any suggestions?
 
Larkid said:
I'm in the middle of upgrading the network for a retail store which uses a
newer IBM PC as its point-of-sale/cash register. The workstation is running
Win2k, and has been operating wirelessly with the router in the back of the
store for several months through a USB wireless adapter.
Last week I ran an ethernet line around the perimiter of the store to
hardwire the connection, and this week I was given the administrator password
on the machine so I could enable the integrated ethernet adaptor. The
computer now recognizes that it is plugged in and connected to a fast
ethernet (100 Mb/s) switch, but doesn't pull an IP address. In fact, it
doesn't receive any data whatsoever. It almost seems as though what it's
sending to the switch in the back isn't getting there. I'd roughly estimate
the cable length is somewhere between 100' and 125', but it has checked out
fine on my line tester, telling me there is no problem with the terminators
or a cut in the cable somewhere.
I've never run into an issue like this, and I have no idea how to go about
resolving it. Anyone have any suggestions?
Click to expand...

Did you perform some of the basic tests such as giving the machine
a fixed IP address, then pinging the server? "Pulling an IP address"
(which presumably means getting an address from the DHCP server)
should come as a subsequent test, after basic networking is established.
 
Remove the wireless equipment from the machine and uninstall the software
associated with it if you are replacing it with a "wired" connection.
on the machine so I could enable the integrated ethernet adaptor. The
computer now recognizes that it is plugged in and connected to a fast
ethernet (100 Mb/s) switch, but doesn't pull an IP address. In fact, it
doesn't receive any data whatsoever. It almost seems as though what it's
sending to the switch in the back isn't getting there.
Click to expand...

Switches don't give addresses. Only a DHCP service can do that. Your
Internate Sharing NAT Device probably does that, but if the machine can't
contact it via broadcasting then you won't get anywhere.
I'd roughly estimate
the cable length is somewhere between 100' and 125', but it has checked
Click to expand...
out

The length limit is 100m,...on a good day. Anything less than perfect will
cause it to be less than that.

Depending on the Tester, it may *not* tell you if there is a problem with a
Terminator. Some testers are only glorified continuity testers which will
give no indication of the quality of the termination.

You should follow Pegasus' suggestions concerning the addressing. You should
solve networking issues first, then DHCP issues second,...not both at the
same time.
 
Back
Top