Search results for query: *

I've been pounding on this one for 2 days with no luck at all. I'm trying to install a wireless adapter into an HP computer running WinXP Pro and every time the installation fails with a "system cannot find the file specified" message. I've so far tried this with 3 different adapters; WMP11v4...

I was using ProSafe all along but for whatever reason it just started working. The tracert still does the same thing so maybe there was another problem along the line somewhere? Who knows, I'm just glad that it works now!

Just as an update to this, I finally got it to connect from home->work using ProSafe client. I haven't a clue what I did to "fix" it, but it suddenly works now and I can transfer files and share printers and such. Thanks to everyone who tried to help me even though I was barking up the wrong...

I can't "see" them like browsing in the Network Neighborhood thing, but I can put \\192.168.222.101 into the address bar of windows explorer and it will show me the shared drives and printers on the *.222.101 computer, which is across the VPN. This works fine for what I need, I just can't use...

By the way, in case I made it unclear, I used the same router to try the connection on both ends, so it can't be an issue with the router blocking the connection. The opposite end each time has been a Linksys router that does support VPN passthrough. The only difference in the home and office...

I am the network admin at work, so I can make any changes I need to fix this. Is there a different way to verify the route besides using ICMP? Like a TCP tracert? Or perhaps some other way to see where and why exactly the VPN tunnel (using TCP/UDP) is failing?

If your router supports VPN Passthrough you shouldn't need to open any ports. Just enable the type of VPN you are using. Otherwise it depends on the type of VPN you are setting up. I assume you are using XP's built-in VPN so that would be PPTP, and would use TCP port 1723. This does open up...

The VPN works one direction; that is, I can initiate it from only one side, the office side. Once I establish the tunnel, I can communicate both ways, which I assume is because both computers are using the same (working) path. By default, the path from home to work is not valid. Right now my...

It isn't getting to the firewall at work. The traffic stops at an att.net address (12.123.210.18) or whatever is suppose to be after that in the route. After AT&T's computers, it should go to a set of Alltel.net addresses which is the ISP we use at work. Is there some way to specify a certain...

Well it started because I was trying to start a VPN tunnel TO the office, but it never would connect, but it did when I reversed it and tunneled TO the house. I also cant do remote desktop or access a web server or anything like that unless I first establish a VPN tunnel from the office and use...

I've been having an issue between my home and office computers. This all started when I was trying to set up a VPN, which I eventually did, but this problem is still bugging me. I can do a tracert from the office to my home computer no problem, but whenever I try to do it from home to work, it...

Check IP addresses? Is it a broadband connection at the hotel? Maybe the DHCP server is assigning an IP that is incompatible with the VPN?

Port forwarding is when you want outside traffic using a certain port to reach a certain machine on the inside network. IE, if you are running a mailserver on one computer you tell the router to forward port 25 traffic to the computer running the server application. If I understand what you...

You may want to change the FQDN or IP settings, just make sure you replace both ends with the same names or IPs. Also make sure that each end has a different subnet than the other end and the virtual link. In my case, Office LAN is using 192.168.111.x Home LAN is using 192.168.222.x Virtual...

Here are my Netgear FVS318v3 settings: IKE Policy Configuration General Policy Name Michael Direction/Type Remote Access Exchange Mode Aggressive Mode Local Local Identity Type FQDN Local Identity Data fvs318v3 Remote Remote Identity Type FQDN Remote Identity Data michael.payne...

Just as an update, I kept tinkering with the Netgear and I finally got it connected using the ProSafe client. Also, I got the Linksys RV042 to do IPSec with the GreenBow VPN client. If you're still interested in your netgear I'll post the details on how I did it. Thanks to everyone who gave...

I havent tried to sell it yet. I actually left it hooked up on one end so I could try to get it working eventually, and today (Saturday) I've had to come in to work because the POS thing has stopped connecting to the net. I re-hooked up the linksys that I used before buying the netgear and...

I got fed up with the Netgear and bought a Linksys RV042. Within a couple hours I was transferring files across a PPTP VPN from my home to office. Set up the connection in XP, connects perfectly, no extra client software needed. Around $150 for the router and I can connect 5 clients through...

I'm having the same problem. Netgear FVS318v3 router and ProSafe client. Client and router say they are connected but no pings go through to the network behind the router. I can ping the WAN IP of the router though. Any new ideas?