DNS? Certain ips don't work on my network... windows server 2000

[Aknosis]

We are running a Windows 2000 Server here at my work. I am trying to setup an ip scheme here instead of running DHCP on all of the computers. However I'm having problems when I change some of the computers IP addresses. I am also in the process of adding new computers to the network and they are reacting the same.

For example this computer wont work when I configure the IP Address to 192.168.16.61 but when I set it to 192.168.16.83 then it does work. I chose 83 because that it was got assigned by the DHCP server when it was set to go via dhcp. I've tried deleting dhcp entries and dns entries on the server to no avail. On the server I do see this computer showing up correct in both reverse lookup and forward lookup. The computer can browse the local net here just fine, connect to the server, printers etc... but when I open a browser window (specifically IE7) it gives me the dns error page.

I've tried running ipconfig /flushdns and ipconfig /registerdns again to no avail. I can also to nslookup from the command prompt and get valid ips for websites in the console but the browser still wont work.

I have changed a few computers with no problem and others I've had problems it seems that the ip # is really the only issue...

Anybody have any thoughts/ideas/help? TIA.

 

[Aknosis]

I'm getting a little bit of information due to the event log:

The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter
with settings:

Adapter Name : {C456DAB7-5CD8-4B47-8057-A4E172DC9935}
Host Name : Tech1
Adapter-specific Domain Suffix : autohaus.local
DNS server list :
192.168.16.2
Sent update to server : <?>
IP Address : 192.1.1.1

The system could not remove these PTR RRs because because of a system problem. For specific error code, see the record data displayed below.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The system failed to update and remove host (A) resource records (RRs) for network adapter
with settings:

Adapter Name : {C456DAB7-5CD8-4B47-8057-A4E172DC9935}
Host Name : Tech1
Primary Domain Suffix : autohaus.local
DNS server list :
192.168.16.2
Sent update to server : 192.1.1.1
IP Address(es) :
192.168.16.61

The reason the update request failed was because of a system problem. For specific error code, see the record data displayed below.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

[Aknosis]

My assumption is there is a problem with the dns and manually setting the ip addresses. When set to use DHCP the dns works fine OR if I set it to the same IP after it was set by dhcp. The only part that confuses me is that I was able to do it on some of the computers but not others.

I think a quick easy fix is to use DHCP with reservations...

 

[Aknosis]

Any ideas? I've tried several microsoft or other online advice to no avail. Now my dhcp is giving out addresses that dont work, I obviously f*ed something up now... but certain ips still let me go outside the network.

 

[RebateMonger]

Remember that most Servers that deliver DHCP addresses also deliver the DNS and Default Gateway information in the DHCP packets. Now that you aren't using DHCP, how are the client PCs getting their Default Gateway and DNS information?

Also, make sure that you have only A SINGLE DNS Server configured for each of your PCs. It should be your Server's DNS Server. Your Server's DNS Server should also be its OWN DNS server. Use a DNS Forwarder in your DNS Server to get Internet name resolution. It sounds to me like some of your client PCs have more than one DNS Server (both your own Server'sl DNS Server and either a router your ISP's DNS Server) listed in their TCP/IP properties.

If you HAVE to have a "static" IP address for a device, then a DHCP Reservation is the way to go. That's what I use for the Vonage P2P adapter in my office. With Reservations, you still get the DNS, Default Gateway, and Reverse DNS information delivered and updated automatically. And you have a place to find IP address information, instead of a piece of paper that you took notes on.

That said, I've never felt the need to use Static IP addresses on a Domain, except for Servers and Printers and such. I've seen WAY too many problems with IP address conflicts and nobody knowing which PC has which IP address.

 

[Aknosis]

Low and behold it was NOT a dns issue, my sonicwall firewall only allows 25 ip address (outbound). So basically when I installed a new computer and it got a DHCP address and then I gave it a static ip.... All that was required was a reboot of the firewall to "realearn" the IPs in use.

I decided to use static ips because I wanted to so I could do better tracking of what is going on in the office and just to organize the current setup. Right now I have the first 10 ips for routers and devices, 30 for our sales, 40 for our service, about 25 for printers and then a dhcp of about 50ips from .200 - 254.

Eventually I will probably just buy a new firewall/router.