Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite
-
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@wirestyle22 said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@EddieJennings did you resolve your issue?
Most likely so. It appears that offline files is the clue I needed. I can do some more testing tomorrow.
YOu don't use Offline files though right?
I do. For the internal office people, the main profile folders (Desktop, Documents, etc.) are redirected to network storage. When you have folder redirection, I believe Offline files are enabled by default.
Okay, but you don't have to have Offline files enabled, do you have users coming in and out with laptops from officess?
Yes, me.
The folks who have laptops and occasionally come into the office, don't have folder redirection enabled. I'm the only person who would be affected by this; thus, I think my work around will just be using UNC paths if I need to get to file shares when I'm at home and connected to the VPN.Now you've lost me. I didn't really understand your earlier thing either between the two different UNCs you posted - can you expand up on that?
-
@dashrender Yes. When I'm connected to the remote access VPN and Offline files are enabled, this condition occurs.
\\mydomain.com\shares\theITDeptSharefails.
\\serverName\theITDeptShareworks. -
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dashrender Yes. When I'm connected to the remote access VPN and Offline files are enabled, this condition occurs.
\\mydomain.com\shares\theITDeptSharefails.
\\serverName\theITDeptShareworks.Right, so the question is - why is your machine not resolving mydomain.com?
You could likely easily solve this with a host file entry for mydomain.com (though perhaps not if the IP stack doesn't see mydomain.com as a valid host name, not sure).
-
I guess it does work
-
Lot of good things to try in this thread.
-
Thanks to @Dashrender for the assist. It looks like the problem was authentication. I authenticated to the VPN using domain\username rather than using the User Principal Name. Doing the latter allowed me to reach DFS shares.
-
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
Thanks to @Dashrender for the assist. It looks like the problem was authentication. I authenticated to the VPN using domain\username rather than using the User Principal Name. Doing the latter allowed me to reach DFS shares.
Woops, that's crazy but definitely there is an issue with DNS.
-
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
Thanks to @Dashrender for the assist. It looks like the problem was authentication. I authenticated to the VPN using domain\username rather than using the User Principal Name. Doing the latter allowed me to reach DFS shares.Woops, that's crazy but definitely there is an issue with DNS.
huh?
-
@dashrender said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
Thanks to @Dashrender for the assist. It looks like the problem was authentication. I authenticated to the VPN using domain\username rather than using the User Principal Name. Doing the latter allowed me to reach DFS shares.Woops, that's crazy but definitely there is an issue with DNS
huh?
If the user cannot login with UPN there is an issue with DNS.... As you should be able to use domain.com.
-
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dashrender said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@dbeato said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
@eddiejennings said in Passing traffic between a remote access VPN and Site-to-site VPN on an Edge Router Lite:
Thanks to @Dashrender for the assist. It looks like the problem was authentication. I authenticated to the VPN using domain\username rather than using the User Principal Name. Doing the latter allowed me to reach DFS shares.Woops, that's crazy but definitely there is an issue with DNS
huh?
If the user cannot login with UPN there is an issue with DNS.... As you should be able to use domain.com.
User can login with UPN. They were using the old domain\username method rather than UPN, which apparently caused problems with accessing stuff via the DFS namespace.
