DHCP vs. Static

My SQL*Server 7 server was working fine this morning... All of a sudden
anyone that is set up using DHCP to get IP Settings can't connect to any
databases... If I change them to a static IP Address it works fine...
Can't remember the exact message but it was something along the lines of
"SQL Server not found or access denied".....
I can get the full message if required...
Sounds like the DHCP server is dispensing the wrong information, possibly
about the DNS server. The error is usually a name resoultion problem, i.e.
the client cannot resolve the server name to its network address.
After a client acquires it ip address via DHCP, run ipconfig /all form a
command prompt and compare the values with a client that has a static ip
address.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||> Sounds like the DHCP server is dispensing the wrong information, possibly
> about the DNS server. The error is usually a name resoultion problem, i.e.
> the client cannot resolve the server name to its network address.
It is dispensing the right information. I am thinking that the corporate
weenies changed
something somewhere and it is causing us problems...
Funny thing is, machines that have a static ip address and the same DNS
Servers entered manually
work just fine.
What I did for now was remove the DNS Servers from the DHCP settings and am
doing a
ipconfig /release
ipconfig /renew
after this is done and the DNS servers aren't set on the DHCP enabled
machines, everything works fine...
Of course any internet stuff is broken....
What could change to cause a situation like that?

> After a client acquires it ip address via DHCP, run ipconfig /all form a
> command prompt and compare the values with a client that has a static ip
> address.

DHCP vs. Static

My SQL*Server 7 server was working fine this morning... All of a sudden
anyone that is set up using DHCP to get IP Settings can't connect to any
databases... If I change them to a static IP Address it works fine...
Can't remember the exact message but it was something along the lines of
"SQL Server not found or access denied".....
I can get the full message if required...Sounds like the DHCP server is dispensing the wrong information, possibly
about the DNS server. The error is usually a name resoultion problem, i.e.
the client cannot resolve the server name to its network address.
After a client acquires it ip address via DHCP, run ipconfig /all form a
command prompt and compare the values with a client that has a static ip
address.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||> Sounds like the DHCP server is dispensing the wrong information, possibly
> about the DNS server. The error is usually a name resoultion problem, i.e.
> the client cannot resolve the server name to its network address.
It is dispensing the right information. I am thinking that the corporate
weenies changed
something somewhere and it is causing us problems...
Funny thing is, machines that have a static ip address and the same DNS
Servers entered manually
work just fine.
What I did for now was remove the DNS Servers from the DHCP settings and am
doing a
ipconfig /release
ipconfig /renew
after this is done and the DNS servers aren't set on the DHCP enabled
machines, everything works fine...
Of course any internet stuff is broken....
What could change to cause a situation like that?

> After a client acquires it ip address via DHCP, run ipconfig /all form a
> command prompt and compare the values with a client that has a static ip
> address.