Post-wildcard certificate installation, internal requests = "Bad

Hello,

We have successfully implemented wildcard certificates on two sites on
W2k3 SP1 IIS 6.0.

After everything was settled, we've discovered that internal secure
requests now fail with "Bad Request (Invalid Hostname)". For example,
users would use "https://10.10.1.99/data_entry/enter_data.asp".

It will work if I path my users outside and back in through IIS, but
from a risk management standpoint that is unacceptable. For example,
users now use "https://secure.website.com/data_entry/enter_data.asp".

I hope this can be done through either additional host header values,
further configuration of the SecureBindings metabase or even possibly
editing each users "Hosts" file?

Thanks.