Shortly after I posted the question about DHCP not being able to assign DNS
servers to clients over RAS, I found the solution in the Microsoft
Knowledge Base.
Apparently, it's been a bug since NT 3.51. The cause is not having a DNS
server listed for the TCP/IP protocol. Putting one in and ( remember to do
this... ) rebooting your PC will do the trick. I've tested this workaround
and it works.
Hope anyone with the same problems be relieved with this.
- Danny Sinang