cant obtain correct IP address

[chris]

Please forgive the lame question but Im a SQL DBA/ Developer not a Network
Admin. Ive got a 2 computer home network. 1 server and 1 pc. The server has
both DNS and DHCP. Typically the NIC is set to "obtain IP automatically".
Right now though the IP address the pc obtains from the server is not one
specified in the IP address scope on DHCP. So I cant even ping the server. I
can hardcode the address in on the NIC to an address specified in the scope
and then I can connect but thats not a permanent solution. Its probably
worth mentioning that Ive got another NIC that connects to the internet and
that ones not having any problems. Probably also worth mentioning that this
server is WIN2K3 but I couldnt find a forum for that version. So Network
Guru's, any clue as to why am I obtaining an address outside of the scope I
specified?

TIA, Chris

 

[David H. Lipman]

Is the address 169.254.x.y ?

If so it is NOT getting an address, it is using IPAutoConfiguration.

If you have a two node network, there is NO need to setup a DNS server or a DHCP server.
Just statically setup the IP stack of each platform.

If you are connecting these two platforms to Broadband Internet such as Cable or DSL, get a
cable/DSL Router such as the Linksys BEFSR41. It has a built-in DHCP server so it will
provide a private address range and it won't be needed on the server, it has a 4 port 10/100
Ethernet switch to connect the server and 1 PC (Router can share internet WAN address with
upto 253 platforms).

As for DNS, if this is NOT connected to the Internet there is absolutely NO reason to have a
DNS server. If you are connected to the Internet, then let the systems use the ISP provided
DNS server addresses.

Dave



| Please forgive the lame question but Im a SQL DBA/ Developer not a Network
| Admin. Ive got a 2 computer home network. 1 server and 1 pc. The server has
| both DNS and DHCP. Typically the NIC is set to "obtain IP automatically".
| Right now though the IP address the pc obtains from the server is not one
| specified in the IP address scope on DHCP. So I cant even ping the server. I
| can hardcode the address in on the NIC to an address specified in the scope
| and then I can connect but thats not a permanent solution. Its probably
| worth mentioning that Ive got another NIC that connects to the internet and
| that ones not having any problems. Probably also worth mentioning that this
| server is WIN2K3 but I couldnt find a forum for that version. So Network
| Guru's, any clue as to why am I obtaining an address outside of the scope I
| specified?
|
| TIA, Chris
|
|

 

[Colin Nash [MVP]]

If he is running Active Directory on the 2003 Server, then yes DNS is
required.

 

[Colin Nash [MVP]]

This is hard to troubleshoot without more information: what are is the
range specified in the scope, and what IP address are you getting? It's all
private non-routable IPs, don't be shy

Also, explain the topology-- how do the computers link together?

 

[chris]

Is the address 169.254.x.y ?

No.

If so it is NOT getting an address, it is using IPAutoConfiguration.

I want it to obtain an address.

If you have a two node network, there is NO need to setup a DNS server or

a DHCP server. Just statically setup the IP stack of each platform.

Im using these for my learning purposes.

If you are connecting these two platforms to Broadband Internet such as

Cable or DSL,

The pc is the only box I care about connecting to the internet at this point
and that part is working fine.

 

[chris]

My bad. Yes, it is getting 169.254.x.y. Does this change stuff?

 

[chris]

My DNS/ DHCP server is 192.168.1.254. The scope is 192.168.1.1 -
192.168.1.10. The address being assigned is 169.254.119.87. (I apologize for
saying it wasnt 169.254.x.y earlier. Im guessing this is the problem bit
dont know how to fix) The topology is just a cable between 2 NIC's. No hub/
router/ etc.

 

[SaltPeter]

My DNS/ DHCP server is 192.168.1.254. The scope is 192.168.1.1 -
192.168.1.10. The address being assigned is 169.254.119.87. (I apologize for
saying it wasnt 169.254.x.y earlier. Im guessing this is the problem bit
dont know how to fix) The topology is just a cable between 2 NIC's. No hub/
router/ etc.

In a situation like yours, using a static ip_address would be a far better
solution. Specially since this is a server with the specified services.
Consider what happens if 169.254.119.87 is assigned to the server but client
receives ip from dhcp scope. Client now resides in a different subnet. Which
means that the RRAS connection representing the router needs to enable IP
forwarding.

Since a dhcp server can't allocate itself an ip_address, make your life a
little simpler and make the server's address static (in the same subnet as
dhcp scope without conflict). example: 192.168.1.11.

On most networks, such a server is considered to have a static ip by
requirement.

There are a host of strange behaviours that occur as well when a server's ip
changes as far as DNS, netbios and other services are concerned. I'll not
get into that or i'll be here for hours.

 

[John Wunderlich]

The topology is just a cable between 2 NIC's. No hub/
router/ etc.

In that case, the cable had better be a special "cross" cable. A
normal straight-thru cable will not work in this situation.

HTH,
John