Destini- I dont think this will fix it but it is worth a try. Make sure that the windows IPSec client is not enabled. Look at your services that are running. If the IPSec client is running, turn it off and set it to manual so it doesn't restart when you reboot. Then try a connection.
You might want to look into a "hardware" VPN solution. Linksys and a lot of other SOHO companies now have routers that have "client to router" vpn support.
"remote host not respoding" error normally means there is no IP conectivity to the Nortel switch. Try to ping your destination address. The switch should initially respond to pings...then it will stop responding..this is a feature built into the code on the switch. If you get any...
In my last post I wrote "On the switch look at /profiles/groups/hours." THIS IS WRONG. Look at /profiles/hours. Sorry about that. Let me know if this helps.
Some suggestions:
You can set predetermined times during which you can permit a group of users access. You might have to create a seperate group for this user. On the switch look at /profiles/groups/hours. Once you have that setup apply the rule you define to whatever group by going to...
In responce to blin2000.....DannyDS is not trying to browse the network neighborhood. He is simply trying to map a drive. If he cant do it by IP address than he more than likely wont be able to do it via WINS name. He needs to tshoot is IP conectivity first. Also....he only needs to worry...
Danny
I would first be concerned with the fact that you can't map a share using an IP address. I would tshoot this first and then worry about the WINS. This might be as simple as bugz1's tip on you not having file sharing enabled. I will check for your reply on this and go from there.
You...
It's working because the older client does not incorporate features for the NAT traversal feature. The reason the new client is not working with your D-Link is because of a problem with the NAT chip in the router. D-Link is working on this issue. Below is kernel reporting when initing the...
Fish...check this out. It might help.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/columns/cableguy/Default.asp
Also...you are using PPTP.....not L2TP as mentioned in a earlier thread.
If you are using Ucallwa's suggestion you need to make sure that you are using the UDP port that your contivity switch is using for NAT traversal. It is under /Services/IPSec on the Nortel contivity switch. If you are the admin of the contivity switch you can solve all your D-link users...
Maybe a firmware upgrade on the AP will solve the problem.?.? Just a thought. Also check with your sys admin and make sure NAT traversal is enabled on the Nortel Contivity switch.
This is probably what is going on. The Contivity Extranet Switch (CES) that you are tunneling to does not have split tunneling enabled. This means all traffic (including internet destined) will be routed down the vpn tunnel. If split tunneling is turned off on the CES than there is no way for...
You need to see if the Nortel contivity switch you are connecting to is configured for split tunneling. If it is not than this is probably the cause of you not being able to reach your printer. Can you get to the internet after you tunnel in? And if you can is your internet traffic being...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.