Problems With Ip Configuration

TheBlueDog

Member
Joined
Jun 15, 2011
Messages
17
Location
Taiwan
Hello,
I'm new here and already start up with a problem.

I have installed Windows Server 2008RS 2 on a PC
running an AMD Athlon 64 x2 Dual Core CPU with 4GB RAM.

The installation process worked like a charm, but
the trouble started at configurating the server.

During the first config. screen where the time zone and
other tasks are set up, I clicked to set up my network
configuration and there it started.

The onboard network controller won't recieve an IP from
the router (D-Link DIR 825). DHCP on the router is enabled.

I've already tried to set up a static IP, enabled/disabled the
Windows firewall, but nothing works.

What am I doing wrong?
 
Hello,

I have updated the drivers to thge following
Windows Setup Installer (32- and 64-bit) for Yukon Controllers
File Name: setup_v11.43.1.3.zip
Date: May 26, 2011
Size: 2.1 megabytes
Description: Windows 2000, Windows XP, Windows 2003, Windows Vista, Server 2008, Server 2008 R2, Windows 7; (32- and 64-bit) Windows Setup Installer

I still don't get an IP. I've pluged the cable into the moden and tried
to set up a pppoe connection. It didn't work either.

Perhaps I should try and re-instal 2008.
 
have you already tried to change the port on the switch / router? Just to be sure there's not a problem with that port...

When you set up a static IP, is it applied correctly? If you type ipconfig /all does it show the correct IP? Can you ping another client on the same network (without pass the router)?
 
I've tried all that.

I'm pretty sure that I have applied the static IP correctly.
ipconfig/all displays a 169. .. IP

I can't ping any other client in my network or on the Inet.


I might go and buy a NIC to try if that works, but since
I'm not sure what causes the problem I kinda don't want
to waste any money on it.

What would you suggest?
 
I assume your IP is 169.254.x.y which is an APIPA address (when DHCP is not available). if you set the ip address manually (for example 192.168.1.10) does it work?
 
if you CANNOT set the static IP, and your don't have any error when you click "OK", so try to reinstall windows... but this is really really strange.
 
Strange indeed. Cost me lots of nervs already.
Will set it up again. See what happens.
Will post the result here.

Thanks for your help!!
 
I've reinstalet Win Server 2008 with the same result.
I've have also bought a network card, but it didn't work
either.

I took some screenshots
 
Open a command prompt and try the following:

(copyrights by microsoft technet)

To set a static IP address

At a command prompt, type the following:

netsh interface ipv4 show interfaces

Make a note of the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address.

At the command prompt, type:

netsh interface ipv4 set address name="" source=static address= mask= gateway=

Where:

ID is the number from step 2 above.

StaticIP is the static IP address that you are setting.

SubnetMask is the subnet mask for the IP address.

DefaultGateway is the default gateway.

At the command prompt, type:

netsh interface ipv4 add dnsserver name="" address=index=1

Where:

ID is the number from step 2 above.

DNSIP is the IP address of your DNS server.
 
It doens't want to work.
The first step

"netsh interface ipv4 set address name="" source=static address= mask= gateway="

worked.

But at the second step I got this msg back
(see picture)
 
The error message indicates that "The configured DNS server is incorrect or missing". So, first things first, how is the IP address? Can you ping inside IP and outside IP addresses?
 
The DNS is a secondary problem.

Once you successfully ran the command "netsh interface ipv4 set address name="" source=static address= mask= gateway=" and you don't have any error message, what happens if you type IPCONFIG /ALL ? And if you try to ping your router (via IP)? And if you try to ping 8.8.8.8?
 
Good morning,

I have set up the PC for a third time and followed
your steps to the dot with pretty much the same results.

The PC isn't even in my local network, so a ping to my
router was unsuccessful. So was an outbound ping to Google.
Pinging 8.8.8.8 didn't bring any results either as the
screenshots show (I had reached my upload quota, so I removed
the other shots)
 
Wait, I think you don't have the proper routing in place...

from the server, type the following and post results:

route print

Unless you have a switch (programmable) from your server and your router, or another device that knows where is your router, I think you can't reach the router, it is on another network.

So first of all type this command:

route add 0.0.0.0 mask 0.0.0.0 IP_ROUTER (which is 168....)

Let me know.
 
Hello,

here are screenshots from the "route print".

I'm a bit confused about the "route add 0.0.0.0 mask 0.0.0.0 IP_ROUTER (which is 168....)" command.
I assume I'm not to change the 0.0.0.0, but add my routers IP after IP_ROUTER, correct?
Well, my router has the 192.168.0.1

Here is my network

VDSL modem-->router (D-LINK DIR 825)[one cable goes to my switch (D-LINK DGS-1008D), another cable to the Win 2008 server]
To the switch are connected
1 Desktop client
1 WHS server (ACER Easystore h340)
1 Laptop
1 NAS (Network Atteched Storage D-LINK DNS 320)
1 EPSON Network printer
1 switch (D-LINK)

to the 2nd switch are connected
1 Laptop
1 Media Streamer

All devices are working fine. They get their IP from the router via DHCP.

How can the Win 2008 not be in the same network?
Sorry, but I kinda don't feel like giving up, yet :-)
 
So, first issue this command:

route add 0.0.0.0 mask 0.0.0.0 192.168.0.1

This will set the default route (default gw).

Now, once you can have the following situation from IPCONFIG:

ip: 192.168.0.120
mask: 255.255.255.0
gw: 192.168.0.1 (in reality this is not needed until you are on the same network).

Try to ping the following:
ping 192.168.0.120
ping 192.168.0.1
ping IP_Another_Client_On_Your_Network (for example the NAS)

If all are ok, try to ping 8.8.8.8

If not, please try the following:
Plug your server directly to one of your switches (just for a test), and try the DHCP.


Let me know.
 
Back
Top