.NET 远程处理速度和 VPN
我正在开发一个项目，该项目使用 .NET Remoting 在客户端应用程序和对象服务器之间进行通信。 对于开发来说，客户端、服务器和 MSSQL 数据库都在我的本地开发计算机上运行。
当我在办公室工作时，响应能力很好。
然而，当我在家工作时，速度明显慢。 如果我断开与 VPN 的连接，它会加速（我相信，但也许这只是一厢情愿）。 如果我完全关闭无线连接，它会立即加速到全速。
我的假设是，远程流量正在通过某个点进行路由，这会减慢一切速度，尽管是我的家庭路由器和/或 VPN。
有谁知道如何强制远程流量保持完全本地化？
I'm working on a project which uses .NET Remoting for communication between the client application and an object server. For development, the client, server, and MSSQL database are all running on my local development machine.
When I'm working at the office, the responsiveness is just fine.
However, when I work from home the speed is significantly slower. If I disconnect from the VPN, it speeds up (I believe, but maybe that's just wishful thinking). If I turn off my wireless connection completely it immediately speeds up to full throttle.
My assumption is that the remoting traffic is being routed through some point that is slowing everything down, albeit my home router and/or the VPN.
Does anyone have any ideas of how to force the remoting traffic to remain completely localized?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
也许在开发过程中您可以使用 IPC 远程处理通道，该通道使用命名管道而不是 TCP。 如果您的远程通道是通过配置文件设置的，那么您甚至不需要重新编译。
我发现下面的链接在设置 IPC 通道时很有用。
http://www.danielmoth。 com/Blog/2004/09/ipc-with-remoting-in-net-20.html
Perhaps during development you could use an IPC remoting channel which uses named pipes instead of TCP. If your remoting channels are set up via a config file then you won't even have to recompile.
I found the link below was useful when setting up an IPC channel.
http://www.danielmoth.com/Blog/2004/09/ipc-with-remoting-in-net-20.html
我也遇到了同样的问题，当你断开连接时，情况会好得多。
如果您使用的是 Windows VPN，则必须更改默认设置。 连接时，它将强制连接使用远程路由器作为网关。 如果您转到连接的属性，则转到网络选项卡。 选择 TCP/IPv4 并转到属性。 在此窗口中选择“高级...”，将有一个选项用于使用远程网络上的默认网关，请确保未选中此选项。 这应该有很大帮助。
I had this same problem where immediately when you disconnect things are tremendously better.
If you are using windows VPN, you have to change a default setting. It will force a connection to use the remote router as your gateway while connected. If you go to properties for the connection, then to the networking tab. Select TCP/IPv4 and go to properties. In this window select Advanced... and there will be an option to use the default gateway on the remote network, make sure this is NOT checked. This should help immensely.
我当前的计算机上没有任何 VPN 连接，但在连接的 TCP/IP 属性中的某处有一个复选框，表明您使用远程主机作为网关或类似的东西。
这曾经给我带来了很多问题，因为我的所有流量都会通过 VPN 然后再返回，即使我想在本地执行某些操作也是如此。
I don't have any VPN connections on my current computer but somewhere in the TCP/IP properties for the connection there's a checkbox to indicate that you use the remote host as a gateway or something like that.
This once caused me alot of issues since all my traffic would go over the VPN and then back again, even when I wanted to do something locally.
去年夏天我参与了一个项目，需要对 .NET Remoting 进行一些相当大的修改。 我不记得所有细节，但如果我们有多个网络接口，我们就无法使用开箱即用的远程处理实现来可靠地检测远程处理流量来自哪一个，这会造成可怕的后果表现。 这听起来像是一个相似的问题，即使不是相同的问题。
I worked on a project last summer that required some pretty heavy modifications to .NET Remoting. I don't remember all the specifics, but if we had more than one network interface, we couldn't get the out-of-the-box Remoting implementation to reliably detect which one the Remoting traffic came from, which did horrible things to performance. This sounds like a similar, if not the same, issue.