This one area many people forget. If they setup a shared key as part of the authentication process. The shared key on the client is found by clicking on the "My Identity", and click onthe pre-shared key.
Main Topics
Browse All TopicsI am trying to setup remote VPN users onto a Juniper SSG-140 unit. I have netscreen-remote. I have followed the standard setup for a remote user and I cannot establish a connection with either netscreen-remote and or window VPN client. I am trying to make this as easy to use for the remote people.
The remote connections are to be setup as able to connect to the network at the main office that this unit is running at and able to communicate with the equipment on-site I would like to be able to route as if I have to tunnel back from the office to manage the remote computers from the main office once they are tunneled in.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I think this KB is very well written:
http://kb.juniper.net/KB47
it will allow you to do exactly what you want to do: multiple users with different xauth password and same IKE ID, to eas administration burden. This way you can give all of your users the same config for the netscreen remote, and just hand them a different user and password! I use this extensively without any problem!
Cheers,
]\/[arco
Also have a look at this bud
http://kb.juniper.net/KB85
I am also from a Check Point background and I found the screenos implementation a little different but it still works really well with just preshared keys.
I see there have been a few comments here and a few sufggestions, can you tell me what you have done to date and what exactly is not working now?
remember there are also logs on the NS remote client that may also assist here.
I am going over the kb but it applied for the general pages to build 4.0 and 6.0 has many of the sub options not even on the same pages and has to be built different. I would call up juniper but the person at my company that has the password information since he setup the account is out of the office.
I have full admin access to the router, for some reason juniper has not linked my email address to the support contract and the person who can auth it is un-aviliable until monday - yay for me.
I have pulled the logs from the juniper and it looks like the request is hitting the unit and just not passing auth threw phase 1
Rejected an IKE packet on ethernet0/2 from 24.***.***.153:500 to 209.***.***.118:500 with cookies 0f22cbc98b76eeb7 and 0000000000000000 because an initial Phase 1 packet arrived from an unrecognized peer gateway.
Ok so looks like your netscreen remote does not get any response to the attemps it makes to setup the vpn. It can be because of two things:
- The configurations of the netscreen remote and the juniper firewall do not match. In that case you'd see a similar log in the firewall. a 'get event' in the cli, or just browse the event log in the web interface, and you should see messages telling why the tunnel cannot be established.
- The packets sent by netscreen remote are not even arriving to the firewall. That could be because of a firewall at the netscreen remote location, router not passing ipsec traffic (can happen on some residential broadband connections), or a router blocking the traffic at the firewall location.
Let's see which two options are you in now so we can help further!
Cheers,
]\/[arco
Rejected an IKE packet on ethernet0/2 from 24.***.***.153:500 to 209.***.***.118:500 with cookies 0f22cbc98b76eeb7 and 0000000000000000 because an initial Phase 1 packet arrived from an unrecognized peer gateway.
Means that the firewall got a phase 1 packet from an unknown source.
Double check the settings on both the NSR and the firewall.
Basically, there is something different. Either the user settings are wrong on the NS remote, or the settings on the firewall are wrong.
For VPN specific info, run "get event type 536"
Oh sorry I wrote the message while you were posting the firewall log. Well usually a phase 1 error like this happens when the preshared key do not match, or when you don't have the same sets of phase 1 encription options. You've specified no perfect forward secrecy, esp, des, md5 on your juniper, make sure you've done the same on your netscreen remote (and redouble check the preshared key, AND the identity that should be staff@domain.com)
Cheers,
]\/[arco
i have added the pre shared key in that window before
I have tried my user name and the stadd@domain.com for the email address field.
I was following this KB - http://kb.juniper.net/KB47
Still nothing connecting
In the "My Identitity" screen, click on the preshared key and double check it's the same as the one you inputted on the firewall. The identity (the email address) looks fine!
Then it looks like you phase 1 in ns remote does not match with the one on your firewall. In ns remote you're using 3des and sha1, while on the firewall you're using des and md5. So in the "Authentication (Phase 1) -> Proposal 1" change Triple des with des, and sha-1 with md5.
This way you should be able to arrive to the xauth prompt, and being able to successfully access the vpn!
Cheers,
]\/[arco
Go back to basics
Do the deed at http://kb.juniper.net/KB47
Once we have this working and made sure that the basics are there, we cna then go onto xauth
I finally got a ticket open with juniper and finally took care of the issue. The issue was that the xauth and ike config setup had changed from what the kb had in to what the tech was able to assist with.
Also found out that the security profile for the remote PC kept rotating the phase1 and phase2 cyhpers on saves
Also issue with the policy that it was not routing once the tunnel was built and would drop the tunnel.
Business Accounts
Answer for Membership
by: PriceDPosted on 2009-08-14 at 21:57:20ID: 25104259
ARe you using a shared key or what type of authentication are you using?