|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
When I'm on my business network and VPN into my dedicated webserver
which resides physically at and on part of my ISP's network, I can't surf or use the web..as though no DNS. Could someone give me some pointers on where and what I should start to look to resolve this problem. My webserver(win2000) has one nic card set on my ISP's network. When I VPN in, my ip is the 169.XXX of windows. I've tried setting the the VPN connection DNS to dynamic from the web server and my local network. No difference. I thought I had read where using windows default 169.xxx I can't |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
When you establish a VPN, by default you are not able to browse the
web. When you create PPtP or L2TP VPN, by default, you create a "Private" connection to your destination or end point of your VPN. Hence, you would not be able to browse the internet. This is a limitiation of using a client to gateway VPN solution. Hope that shine some light on things. JSP Deere wrote: > When I'm on my business network and VPN into my dedicated webserver > which resides physically at and on part of my ISP's network, I can't > surf or use the web..as though no DNS. > > Could someone give me some pointers on where and what I should start to > > look to resolve this problem. > > > My webserver(win2000) has one nic card set on my ISP's network. When I > VPN in, my ip is the 169.XXX of windows. > > > I've tried setting the the VPN connection DNS to dynamic from the web > server and my local network. No difference. > > > I thought I had read where using windows default 169.xxx I can't |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Joel thanks for you quick response.
So there are no workarounds for a client? If so, then I will need to establish a vpn connecton between by network firewall and my remote web server? thanks mark joel.spicuzza@gmail.com wrote: > When you establish a VPN, by default you are not able to browse the > web. When you create PPtP or L2TP VPN, by default, you create a > "Private" connection to your destination or end point of your VPN. > Hence, you would not be able to browse the internet. This is a > limitiation of using a client to gateway VPN solution. > > Hope that shine some light on things. > > JSP > > Deere wrote: > > When I'm on my business network and VPN into my dedicated webserver > > which resides physically at and on part of my ISP's network, I can't > > surf or use the web..as though no DNS. > > > > Could someone give me some pointers on where and what I should start to > > > > look to resolve this problem. > > > > > > My webserver(win2000) has one nic card set on my ISP's network. When I > > VPN in, my ip is the 169.XXX of windows. > > > > > > I've tried setting the the VPN connection DNS to dynamic from the web > > server and my local network. No difference. > > > > > > I thought I had read where using windows default 169.xxx I can't |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Deere,
You are correct with going the hardware route. From a client connection side, it's a black or white choice. Either VPN with no Internet browsing, or just the opposite. By establishing a connection from your firewall device to the destination device, you essentially have a split tunnel VPN. This will allow direct secure connection to your web server at your ISP, and simultaneous connection to your local network and public Internet. Feel free to contact me directly at my Gmail account, and I can steer you further in greater detail, and more securely than a public newsgroup. CAIO! Joel Deere wrote: > Joel thanks for you quick response. > > So there are no workarounds for a client? If so, then I will need to > establish a vpn connecton between by network firewall and my remote web > server? > > thanks > mark > > > > joel.spicuzza@gmail.com wrote: > > When you establish a VPN, by default you are not able to browse the > > web. When you create PPtP or L2TP VPN, by default, you create a > > "Private" connection to your destination or end point of your VPN. > > Hence, you would not be able to browse the internet. This is a > > limitiation of using a client to gateway VPN solution. > > > > Hope that shine some light on things. > > > > JSP > > > > Deere wrote: > > > When I'm on my business network and VPN into my dedicated webserver > > > which resides physically at and on part of my ISP's network, I can't > > > surf or use the web..as though no DNS. > > > > > > Could someone give me some pointers on where and what I should start to > > > > > > look to resolve this problem. > > > > > > > > > My webserver(win2000) has one nic card set on my ISP's network. When I > > > VPN in, my ip is the 169.XXX of windows. > > > > > > > > > I've tried setting the the VPN connection DNS to dynamic from the web > > > server and my local network. No difference. > > > > > > > > > I thought I had read where using windows default 169.xxx I can't |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
When you set up a VPN, you normally give it an IP address on the same subnet
as the VPN server side. If this is an ISP and you have only one IP address, assuming a pptp VPN, the workaround is to uncheck the "Use default gateway on remote network" box in the client options. Then your routing table's default route will stay pointed at your local router. ....kurt "Deere" <meh47960@gmail.com> wrote in message news:1158782823.735955.86360@h48g2000cwc.googlegro ups.com... > When I'm on my business network and VPN into my dedicated webserver > which resides physically at and on part of my ISP's network, I can't > surf or use the web..as though no DNS. > > Could someone give me some pointers on where and what I should start to > > look to resolve this problem. > > > My webserver(win2000) has one nic card set on my ISP's network. When I > VPN in, my ip is the 169.XXX of windows. > > > I've tried setting the the VPN connection DNS to dynamic from the web > server and my local network. No difference. > > > I thought I had read where using windows default 169.xxx I can't > |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
"Kurt" <lorentzenkurt@nospam.hotmail.com> wrote in message
news:12h6mscls5s6e07@corp.supernews.com... > When you set up a VPN, you normally give it an IP address on the same > subnet as the VPN server side. If this is an ISP and you have only one IP > address, assuming a pptp VPN, the workaround is to uncheck the "Use > default gateway on remote network" box in the client options. Then your > routing table's default route will stay pointed at your local router. Also, on the client side VPN "interface" there are options almost identical to the ones on the NIC->IP properties for a real NIC interface. There you can override and adjust what options will be used with that interface such as Default Gateway, DNS server, WINS server etc. This dialog is found 'behind' the main configuration or on an adjacent tab, perhaps by pressing the Advanced button depending on the OS. BTW, such also appears within "RRAS" when setting up a server VPN connection, and not just one the ordinary client settings such as XP. -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] > ...kurt > > "Deere" <meh47960@gmail.com> wrote in message > news:1158782823.735955.86360@h48g2000cwc.googlegro ups.com... >> When I'm on my business network and VPN into my dedicated webserver >> which resides physically at and on part of my ISP's network, I can't >> surf or use the web..as though no DNS. >> >> Could someone give me some pointers on where and what I should start to >> >> look to resolve this problem. >> >> >> My webserver(win2000) has one nic card set on my ISP's network. When I >> VPN in, my ip is the 169.XXX of windows. >> >> >> I've tried setting the the VPN connection DNS to dynamic from the web >> server and my local network. No difference. >> >> >> I thought I had read where using windows default 169.xxx I can't >> > > |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
Yes, Herb makes a good point. There are quite a few options, such as
allowing the client to specify it's own ip address, that can be configured on the server side. ....kurt "Herb Martin" <news@LearnQuick.com> wrote in message news:%23lJn8Yi3GHA.2228@TK2MSFTNGP03.phx.gbl... > "Kurt" <lorentzenkurt@nospam.hotmail.com> wrote in message > news:12h6mscls5s6e07@corp.supernews.com... >> When you set up a VPN, you normally give it an IP address on the same >> subnet as the VPN server side. If this is an ISP and you have only one IP >> address, assuming a pptp VPN, the workaround is to uncheck the "Use >> default gateway on remote network" box in the client options. Then your >> routing table's default route will stay pointed at your local router. > > Also, on the client side VPN "interface" there are options > almost identical to the ones on the NIC->IP properties for > a real NIC interface. > > There you can override and adjust what options will be > used with that interface such as Default Gateway, DNS > server, WINS server etc. > > This dialog is found 'behind' the main configuration or > on an adjacent tab, perhaps by pressing the Advanced > button depending on the OS. > > BTW, such also appears within "RRAS" when setting > up a server VPN connection, and not just one the ordinary > client settings such as XP. > > > > -- > Herb Martin, MCSE, MVP > Accelerated MCSE > http://www.LearnQuick.Com > [phone number on web site] > >> ...kurt >> >> "Deere" <meh47960@gmail.com> wrote in message >> news:1158782823.735955.86360@h48g2000cwc.googlegro ups.com... >>> When I'm on my business network and VPN into my dedicated webserver >>> which resides physically at and on part of my ISP's network, I can't >>> surf or use the web..as though no DNS. >>> >>> Could someone give me some pointers on where and what I should start to >>> >>> look to resolve this problem. >>> >>> >>> My webserver(win2000) has one nic card set on my ISP's network. When I >>> VPN in, my ip is the 169.XXX of windows. >>> >>> >>> I've tried setting the the VPN connection DNS to dynamic from the web >>> server and my local network. No difference. >>> >>> >>> I thought I had read where using windows default 169.xxx I can't >>> >> >> > > |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
Kurt...BINGO... ""the workaround is to uncheck the "Use default
gateway on remote network" box in the client options"" that did it..thanks for everyones contributions..my knowledge base has increased. |
|
![]() |
| Outils de la discussion | |
|
|