Thứ Hai, November 17th, 2008 | Tác giả:

I’d never really had the need to connect to a VPN until this weekend. After connecting, I found that my Internet access was rather non-functional except to the VPN in question. A colleague happened to be on hand (he’d given me the access details in the first place) and he quickly suggested this workaround.

Today, a client had the same issue. Perhaps this problem is more common than I first thought.

When connecting to the VPN, Windows updates the default gateway on your desktop to reflect the VPN’s settings. Most likely, however, you only need to access specific subnets on the VPN and you want all unrelated traffic to use youroldsettings.

It turns out that its a simple checkbox that needs to be unchecked. The jist (sp.??) of finding the setting: Right-click the VPN in Network Connections -> Properties -> Internet Protocol (TCP/IP); [Properties] ; [Nâng cao], and uncheck the “[ ] Use default gateway on remote network”.

Then click the usual OK/Apply/Yes-of-course-your-dialogue-ness (all the while reading and absorbing any warnings appropriately) until you’re back to your Network Connections window. Right-click the VPN connection and disable / re-connect.

You should be able to confirm that the Default Gateway does not change by running the command-line app ipconfig before and after enabling the VPN connection. Look specifically for the line labelledDefault Gateway”.

[edit reason=moore”]…

It turns out that a possible reason for this setting being the default setting is for security. If your desktop happens to be compromised or inadvertently routing traffic, connecting to the VPN might expose the supposedlyprivatenetwork to the Internet.

Chia sẻ
Thể loại: mạng, cửa sổ
Bạn có thể làm theo bất kỳ phản ứng với cụm từ này thông qua RSS 2.0 nuôi. Bạn có thể lại một phản ứng, hoặc trackback từ trang web của riêng bạn.
Để lại một trả lời » Đăng nhập