Unable to Reach Desintation when DHCP enabled, Server 2003

I also just found out that it's unable to resolve IP addresses on the other side of our VPN tunnel, which may perhaps be the root cause.  Still not sure, but I am able to of course resolve other internal IP addresses, and access all forms of network shares.  

Still it being a firewall issue seems odd, as I'm able to connect to everything using a static/reservation.

Also another thing I've tried is booting a separate machine up and trying it, it seems sporadic as the second machine came up got a new IP and worked fine.

I switched IP addresses from Machine 1(currently broken IP) with Machine 2 (working IP)

So then Machine 1 started working, and Machine 2 obviously failed.  

2 separate leases.  

"For detecting the IP used.. you could configure DHCP to detect if the IP is taken or not by someone.. In the proprieties there is a checkbox "  Was unable to find that setting.

can you please do the following and report what you find. when you have dhcp enabled, start up a command line (start\run and then type cmd and press ok)

type ipconfig /full and press enter in the black window that comes up. compare the gateway and dns server address that is listed to what you configure the computer to when you put it to static ip. also check to see that the dhcp server ip is the ip of the dhcp server you are expecting to get the ip from. this will ensure there are no rogue dhcp servers in your network (ms dhcp shuts off if it finds any other dhcp server).

Also, in windows, you can setup alternate ip (the next tab in the screen where you setup your computer to get ip assigned automatically). check to ensure there is nothing configured there. Also, if your pc is unable to get a dhcp request response, it might get itself an apipa address (169.254.x.x).
Also, do you have a firewall etc installed on your pc? these can sometimes block dhcp packets as well.

There's no firewall installed.

It's not some sort of machine specific issue, it's going to be something related to the IP address i'm getting.  

Example:

If I take the 'working' IP address from machine 2, and put it in machine 1 by reservation/static assignment, it gets out just fine.

then If I take the IP address from machine 1 that was not working, and put it on a 'known good' machine 2.  I'm unable to get out using that ip address.

08/04/2009 09:23:09.480 - Info - Network Access -       ICMP packet from LAN allowed -  192.168.45.100, 512, LAN, dantest2.domain.com-     90.***.***.**, 8, WAN -         ICMP Echo, Code: 0

08/04/2009 09:23:09.560 - Info - Network Access -       ICMP packet allowed -    90.***.***.**, 8, WAN -         192.168.45.100, 512, LAN, dantest2.domain.com-     ICMP Echo Reply, Code:   0


Is what my firewall is spitting at me.

when you get an ip that is blocked (icmp packets dont make it to the destination), are you still able to browse to websites? your ping test shows that your machine is still able to resolve google.com, just that you cannot ping, so it could be a firewall configuration issue, where it allows icmp packets for certain ips only. check to see if you can browse to www.google.com while on the "wrong" ip.

Also, what firewall are you using? Is this a simple site where you just have a few machines behind a firewall which they connects to the internet or do you have vpn connections to other locations as well?

We're using a Sonicwall TZ190.  We do use VPN, this machine isn't currently using VPN, nor do any of my VPN machine seem to have a problem.

Yes we also have a few VPN tunnels setup that don't seem to have the problem, and are not using VPN DHCP.  

I cannot browse at all, nor can I connect to anything outside of the firewall this includes our VPN tunnel facilities.  Using Googles IP address in IE does not work either.

how about changing the scope on your dhcp server so that it starts from the last good ip that you know of. see if the problem is the same when your pc gets allocated this good ip by the dhcp server.

I am guessing your traffic is being filtered.. most probably by the firewall. can you do a traceroute to www.google.com when you cannot browse and post the results. it would be interesting to see where the traffic gets to.

C:\Documents and Settings\Administrator>tracert -h 15 google.com

Tracing route to google.com [74.125.127.100]
over a maximum of 15 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

hey have you confirmed that the options that are served by the dhcp server.. gateway/dns etc are all correct?

do you have any special routes setup? do a route print on the command line