Resolving internal hostnames after authentication with Juniper firewall

Dear experts,

After installing a Juniper 5GT firewall(by our company firewall guys), we have some troubles with dns resolving.
When we start a vpn connection outside our lan from the internet,  on a client with netscreen remote software, we authenticate with the Juniper firewall with a vpnlogin user configured on the Juniper. When i check on the client the networksettings (ipconfig /all), i see we received the 2 internal dns servers from our lan.
When I ping or rdp a server on our lan with his hostname (not FQDN), it won't work; when I try it with the FQDN it works.
Problem we have now is that on the clients laptops, all share mappings are made with the hostname, so in this case, he has to re-map the drives with the FQDN.
I can edit the local 'host' file with the hostnames and ip's but is it possible to configure the firewall (or dns) to add the domainsuffix to the clients network settings? so that resolving with the hostnames will work?

A second option i was thinking about,  
before we installed the juniper, we made a vpn pptp connection over another firewall to a vpn pptp server in our lan.
So when we started the vpn session, we were immediately authenticated in our domain and could access all shares, outlook(exchange).

I thought to do it now just like before, start a vpn pptp session, but afther authenticating with the Juniper,

So, after i authenticated with the Juniper,I tried to make a vpn pptp connection to the internal IP of the vpn pptp server and  it worked, but after 5sec. my connection was dropped with the juniper...
Is this a securitysetting on the netscreen client?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You can hand out the the DNS Suffix with DHCP.  I would assume you have DHCP sitting somewhere handing out the addresses.  Most all DHCP Servers have the option to also assign DNS Suffix.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
KozznAuthor Commented:

It's the juniper firewall which assign the dns server ip's to the client, but I don 't think the juniper can assign a domain suffix to the client.
Bummer.  That is the most common place to do it.  I am not overly familiar with Juniper FWs, but depending on the config if you are able you could also specify the Suffix's via a Group Policy.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.