Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- TCP/IP and DHCP on Win2K SP4
July 30, 2009, 1:39 am
rate this thread
I have a DSL modem with a variable IP# and it worked great for over a
year. Then it would not connect to the 'net at all. I moved the Kingston
network card through several slots and finally I found one that worked.
The driver is now installed but it still won't connect to the 'net and
the 3 usual green lights are on.
The LAN Connection Properties show the card and indicates IP address and
DNS are obtained automatically. The DHCP is enabled.
The usual address for the first attempt to connect is with IExplorer and
192.168.0.1. It can't connect and there is no ping response from that
IP#. I shut down the computer and modem and waited 1 minute and then
switched on the modem and finally the computer. Still no go. The cookies
and temp files in IE were deleted beforehand.
I have an older backup computer and it gets through the same modem and
lines as the other computer, so the problem lies with that newer
computer and not the modem or the lines. I shut down the antivirus
program and firewall while I was testing the newer computer.
Help Appreciated :-)
Re: TCP/IP and DHCP on Win2K SP4
What I'd try
1) Get two computers.
2) Connect their Ethernet interfaces with a "crossover" cable.
(There are two types of cable, "crossover" and "straight thru",
and crossover is for computer to computer. Straight thru is
from computer to router box.)
3) Examine each computer, to see what IP address it is using.
Force a value of IP address if necessary (so each machine uses
a different value).
4) Install Wireshark on each computer.
Wireshark watches both TX and RX, so you can
verify what the ping is doing. The ping command tells you
whether an answer came back, while Wireshark can see both
arriving and leaving packets.
Computers with Gigabit ethernet interfaces, don't have
to worry about cable type, since the GbE chip will usually
have MDI/MDIX and the ability to swap TX and RX on its own.
Either kind of cable will work with one of those. But on
computers with 10/100BT, it is more likely you'll need to
play cable games, and use the correct cable type as the
situation dictates. So when two 10/100BT interfaces are
involved, you need to use the correct cable type.
- » Newest MemTest86, MemTest86+ incompatible with Sandy, Ivy chipsets?
- — Next thread in » Computer Hardware
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — The site's Newest Thread. Posted in » Secure Shell Forum