Static IP address does not work - DHCP does

[msal]

I'm trying to assign an IP address to a new server but it doesn't appear to be working. All of our workstations use DHCP to get their IP Address, and if I set this server to use DHCP, it can connect to the domain fine. If I try to give it static IP address however, I can't connect to the domain, or ping any other server/workstation. The static IP address) I try to give it is 100% identical (with the exception of the last digit of course) to the other servers that are all working fine. DNS settings are also identical. The IP address' for the servers are different to those used in DHCP for the workstations, and under the scope for the servers there are no reserved address'

Can someone please tell me I'm missing something simple.

 

[rislejay]

Are you sure the IP address is not being used anywhere else? Does the IP address fall within the subnet mask? More than likely you are using a private IP so disclosing the information won't compromise anything, bt sanitize as needed. Can you give us a known working config from one of the servers by doing an ipconfig /all from a cmd prompt? And give us the same thing from the new server with the static address?

 

[Seaspray0]

when you assign a static IP address, you must consider the following:

1. The address is within the subnet of the network you are attaching it to. The subnet mask should match the one used on your network.

2. The IP address is not currently in use and is not within the scope of your DHCP server (unless you make it unavailable in DHCP).

3. You must manually configure those settings that are handed out by DHCP (i.e. DNS, WINS, default gateway).

4. You must make a static entry for those services that do not get updated by assigning a static DNS, i.e. a static entry on your DNS server.

To troubleshoot, start with the basics. Put it back on DHCP and see if you get a valid IP address (see note) and can ping the IP address you want to assign it to. If you can't, proceed to the next step.
Assign the static IP address to the computer and see if you can ping it's own address, then ping the address of a computer on the same subnet, then if you have other subnets, ping your default gateway and then a computer on another subnet. Once you can ping everything you need to ping, move on to checking name resolution; ping the DNS name of another computer and ping the NetBios name of another computer.

note: if you see an address 169.254.x.x then you are not getting an address from your DHCP server.


A+/MCP/MCSE/MCDBA

 

[msal]

thanks for the replies.
I've actually sotred the problem now. As I said, the settings were all correct, it's just that I had it patched into a switch for DHCP clients only!! Bit of a silly mistake but all fixed now.