• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 811
  • Last Modified:

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?
0
Kozzn
Asked:
Kozzn
  • 2
2 Solutions
 
TyBeattyCommented:
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.

Thanks,
Tyson
0
 
KozznAuthor Commented:
Tyson,

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.
0
 
TyBeattyCommented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now