Windows Server

RL Tech · Guest

Hello,

I am having a problem with my new client computer connecting to our existing
sbs2000 network. Basically it doesn't connect and i can't continue the new
client computer installation.

Our current hardware is as follows...
SBS 2000 - PDC (everything is installed and works as it should).
Windows 2000 Server - BDC (used for other server related stuff)
Windows 2000 Professional.

The new client computer is windows 2000, newly installed, with just
graphics, network card software installed. Once it has been set up, i get a
169 ip address. I've already tried to install another network card into
this computer, but i also get a 169 ip address. I've taken the computer to
another network, and a 192 address comes up (i think it was a router)...
I've used another plug (that does give me a 10 ip address), and still get a
169 ip address. I've also reinstalled the computer and the same ip address
is given. I've even rebooted the sbs 2000 server, and i still get the same
ip address.

I've tried using the existing plug on an existing computer, and the same ip
address comes up for that computer (regardless of computer).

Here is the IPCONFIG /all on the computer that doesn't connect.

Windows 2000 IP Configuration
Host Name: ws03
Primary DNS Suffic:
Node Type: Broadcast
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Local Area Connection:
Connection Specific DNS Suffix:
Description: VIA Rhine II Fast Eternet Adapter
Physical: (there is one, no need to include this)
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
Autoconfiguration IP Address: 169.254.62.112
Subnet Mask: 255.255.0.0
Default Gateway:
DNS Servers:

If you have any further questions, please don't hesitate to ask...

Thanks for any help you may be able to provide.

....Robin

Merv Porter [SBS-MVP] · Guest

You may want to update your Ethernet driver for the VIA Rhine II Fast
Eternet Adapter...

http://www.viaarena.com/default.aspx?PageID=420&OSID=3&CatID=1250&SubCatID=124

--
Merv Porter [SBS MVP]

Kathy · Guest

You can also disable APIPA (the 169 address), see
http://www.petri.co.il/disable_apipa_in_windows_2000_xp_2003.htm

This then makes it possible to see whether the PC can see the DHCP server
and start troubleshooting.

Kathy

RL Tech · Guest

Ok i've done this, but i guess i'm not sure how to start the
troubleshooting... Sorry, but networking is my weak point.. :(

Thank you for any further help you may be able to provide...

RL Tech · Guest

Hi,

I did this and it didn't make any difference... I still get the 169 ip
address..
Thank you for the suggestion...

Merv Porter [SBS-MVP] · Guest

Which device is providing DHCP for the network: the SBS 2000 server or the
Netgear router?

--
Merv Porter [SBS MVP]

Merv Porter [SBS-MVP] · Guest

Can you also post an IPconfig /all for the server?

--
Merv Porter [SBS MVP]

Kathy · Guest

I'm assuming that it is a newly built Win2k pro with sp4 patched up to date.
If that isn't the case, get it to that state. You can go to Windows Update
catalog from another machine and download sp4 and ie6 sp2, burn them to a
CD and install (if you can't get the new machine on to the network). If you
are running Norton Internet Security (or similar personal firewall), remove
it or disable it for now.

Well, now the PC should either get a correct address from the SBS server, so
you can stop now, or it will show a network address of 0.0.0.0 (no address -
can't see server) when you do an ipconfig. If that is the case, start by
checking the TCP/IP properties - make sure nothing is filled in except the
"get an address from DHCP" bit - no DNS, nothing.
Set the network card properties anything but automatic - preferably the
correct setting ;-) - so if you have 10/100 switch and everything else on
the network has a 10/100 (or better) card in it, set the PC to 100 speed and
half duplex. Make sure that the network card can't be turned off to save
power.

If it still doesn't work, check the network cables. Use cables that you
know work on another machine on that network. Also check on the server to
make sure that there are enough DHCP addresses to go round.

If it still doesn't work, I'd replace the network card.

HTH

Kathy

	Windows Server Forum Index -> Small Business Server 2000	All times are GMT
Page 1 of 1