服务器 Gind.cn
  1. 服务器 Gind.cn
  3. 在Server 2012远程桌面服务环境中运行Bloomberg Anywhereterminal
Intereting Posts
Ubuntu上的Apache 2.2虚拟主机 邮箱数据库需要什么权限才能为所有邮箱调用FindAppointments？ 远程连接sql服务器不工作，但如果防火墙禁用它呢？ 服务器断电时，RAID BBU电池是否充电？ 如何启用HTTP环回连接？ apache 2.4是否对连接有严格的限制？ freeradius中的proxy.conf文件 你可以通过URL参数的HTTP基本authentication的用户/通行证吗？ 为什么Linux不列出我想要的IP？ Media_Wearout_Indicator 043 – 理由担心？ 如何logging进程的CPU使用情况 高networking利用率 – 系统过程 – PID 4 如何安全平稳地更新服务器上的软件包？（通过apt） 如何将数据存储在随机切断电源的机器上 http与https虚拟主机

在Server 2012远程桌面服务环境中运行Bloomberg Anywhereterminal

互联网脑信任你好！

我们有一个运行RDS的Windows 2012 R2框，并希望运行彭博桌面terminal。

我们知道其他人运行这种configuration有一个区别：
– >我们正在利用彭博的私有IPnetworking（我猜测T1上的MPLS），而不是通过开放的互联网连接。

问题：

在我们的testing环境中，彭博实例将通过互联网连接，但不通过私有IP（连接到路由器WAN端口的彭博路由器）连接。

问题：

为什么？ 真的，我真的有兴趣了解什么系统服务/ IP堆栈/差异导致私人IP连接失败。

背景：

  • 专用IP连接在Windows 7 / 8.1实例（包括虚拟机）上处于活动状态。
  • 彭博将不支持服务器版主机操作系统（与之前的两个调用在部署之前validation计划相矛盾）。 即：他们不会帮助。
  • 通过开放式互联网（orr常规广域网）连接时，系统按预期工作。
  • 我们testing了干净的2012年安装，禁用防火墙，没有GPO /域，pipe理员帐户 – 相同的行为，所以它不是RDS相关。

迄今为止试过

  • 在SonicWall路由器上validation的networking设置（同样，win 7客户端连接正常。）
  • 上述“干净安装”
  • 在服务器上手动input所需的彭博“内部”IP路由（在Win 7上没有必要，但是我会咬一口，Bloomberg有一个方便的MakeRoute GUI工具）。
  • 使用过程监视器来识别可能丢失的程序集（与正在运行的赢7箱相比）。
    • 其他的事情，我敢肯定，但战争的雾是伟大的。

“嗯，这很有趣，但…”

在查看netstat时，彭博支持对8292端口的通信非常感兴趣。

更新1：静态路由和彭博网关IP

我之前提到，我试图利用彭博社包含的工具利用静态路由，这个工具采用彭博网关的IP（192.168.100.2），并插入一系列预定义的路由到操作系统。

效用输出： 

Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.150.1 Default 199.105.176.0 255.255.248.0 192.168.100.2 1 199.105.184.0 255.255.254.0 192.168.100.2 1 205.183.246.0 255.255.255.0 192.168.100.2 1 208.134.161.0 255.255.255.0 192.168.100.2 1 69.184.0.0 255.255.0.0 192.168.100.2 1

更新2：IP地址和端口 

 **Network Address Specifications** For a private connection, the Client computer must be able to connect to ALL networks in the following Bloomberg subnets: 208.134.161.0 using the subnet mask of 255.255.255.0 205.183.246.0 using the subnet mask of 255.255.255.0 199.105.176.0 using the subnet mask of 255.255.248.0 199.105.184.0 using the subnet mask of 255.255.254.0 69.184.0.0 using the subnet mask of 255.255.0.0 The above network prefixes are advertised using RIP v2 from the Ethernet ports of the Bloomberg Routers installed at the client site. Alternatively, clients wishing not to receive RIP can configure their networks to route statically to the above prefixes through the Ethernet ports of the Bloomberg Routers. For Internet connections, the Client PC must be able to connect to the following Bloomberg subnets: 160.43.250.0 using the subnet mask of 255.255.255.0 206.156.53.0 using the subnet mask of 255.255.255.0 205.216.112.0 using the subnet mask of 255.255.255.0 208.22.56.0 using the subnet mask of 255.255.255.0 208.22.57.0 using the subnet mask of 255.255.255.0 69.191.192.0 using the subnet mask of 255.255.192.0 The Client PC must be able to connect to the following Bloomberg ports: UDP Destination Ports 48129-48137 TCP Destination Ports 8194-8198 8209-8220 8290-8294 For BRIN connections, the Client PC must be able to connect to ANY IP address on the above Bloomberg ports.

来源PDF： 运输和安全规范

NetStat输出 （注意：testing计算机在192.168.150.xnetworking上，Bloomberg专用网关是192.168.100.2）。 

 Pinging 192.168.100.2 with 32 bytes of data. Reply from 192.168.100.2 Time 3 ms TTL 255 Size 32 Reply from 192.168.100.2 Time 1 ms TTL 255 Size 32 Reply from 192.168.100.2 Time 1 ms TTL 255 Size 32 Reply from 192.168.100.2 Time 1 ms TTL 255 Size 32 Ping statistics for 192.168.100.2: Packets: Sent = 4 Received = 4 Lost = 0 Approximate round trip times in milli-seconds: Minimum = 0ms Maximum = 3ms Average = 1ms Active Connections: Proto Local Address Foreign Address State TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:443 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:593 0.0.0.0:0 LISTENING TCP 0.0.0.0:3388 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:5504 0.0.0.0:0 LISTENING TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING TCP 0.0.0.0:49165 0.0.0.0:0 LISTENING TCP 0.0.0.0:49183 0.0.0.0:0 LISTENING TCP 0.0.0.0:49187 0.0.0.0:0 LISTENING TCP 0.0.0.0:49190 0.0.0.0:0 LISTENING TCP 0.0.0.0:49191 0.0.0.0:0 LISTENING TCP 0.0.0.0:49192 0.0.0.0:0 LISTENING TCP 0.0.0.0:49266 0.0.0.0:0 LISTENING TCP 127.0.0.1:49910 127.0.0.1:49911 ESTABLISHED TCP 127.0.0.1:49911 127.0.0.1:49910 ESTABLISHED TCP 127.0.0.1:49912 127.0.0.1:49913 ESTABLISHED TCP 127.0.0.1:49913 127.0.0.1:49912 ESTABLISHED TCP 127.0.0.1:49914 127.0.0.1:49915 ESTABLISHED TCP 127.0.0.1:49915 127.0.0.1:49914 ESTABLISHED TCP 127.0.0.1:49916 127.0.0.1:49917 ESTABLISHED TCP 127.0.0.1:49917 127.0.0.1:49916 ESTABLISHED TCP 127.0.0.1:49918 127.0.0.1:49919 ESTABLISHED TCP 127.0.0.1:49919 127.0.0.1:49918 ESTABLISHED TCP 127.0.0.1:49920 127.0.0.1:49921 ESTABLISHED TCP 127.0.0.1:49921 127.0.0.1:49920 ESTABLISHED TCP 127.0.0.1:49922 0.0.0.0:0 LISTENING TCP 127.0.0.1:49923 127.0.0.1:49924 ESTABLISHED TCP 127.0.0.1:49924 127.0.0.1:49923 ESTABLISHED TCP 127.0.0.1:49925 127.0.0.1:49926 ESTABLISHED TCP 127.0.0.1:49926 127.0.0.1:49925 ESTABLISHED TCP 127.0.0.1:49927 127.0.0.1:49928 ESTABLISHED TCP 127.0.0.1:49928 127.0.0.1:49927 ESTABLISHED TCP 127.0.0.1:49929 127.0.0.1:49930 ESTABLISHED TCP 127.0.0.1:49930 127.0.0.1:49929 ESTABLISHED TCP 127.0.0.1:49931 127.0.0.1:49932 ESTABLISHED TCP 127.0.0.1:49932 127.0.0.1:49931 ESTABLISHED TCP 127.0.0.1:49933 127.0.0.1:49934 ESTABLISHED TCP 127.0.0.1:49934 127.0.0.1:49933 ESTABLISHED TCP 127.0.0.1:49935 127.0.0.1:49936 ESTABLISHED TCP 127.0.0.1:49936 127.0.0.1:49935 ESTABLISHED TCP 127.0.0.1:49937 127.0.0.1:49938 ESTABLISHED TCP 127.0.0.1:49938 127.0.0.1:49937 ESTABLISHED TCP 127.0.0.1:49939 127.0.0.1:49940 ESTABLISHED TCP 127.0.0.1:49940 127.0.0.1:49939 ESTABLISHED TCP 127.0.0.1:49941 127.0.0.1:49942 ESTABLISHED TCP 127.0.0.1:49942 127.0.0.1:49941 ESTABLISHED TCP 127.0.0.1:49943 0.0.0.0:0 LISTENING TCP 127.0.0.1:49944 127.0.0.1:49945 ESTABLISHED TCP 127.0.0.1:49945 127.0.0.1:49944 ESTABLISHED TCP 192.168.150.32:139 0.0.0.0:0 LISTENING TCP 192.168.150.32:8290 208.134.161.154:8292SYN_SENT TCP 192.168.150.32:49262 192.168.150.30:445 ESTABLISHED TCP 192.168.150.32:49263 192.168.150.30:445 ESTABLISHED TCP 192.168.150.32:49264 192.168.150.30:445 ESTABLISHED TCP 192.168.150.32:49265 192.168.150.30:445 ESTABLISHED TCP 192.168.150.32:49662 212.73.235.22:443 ESTABLISHED TCP 192.168.150.32:49950 38.113.165.101:443 TIME_WAIT TCP 192.168.150.32:49951 38.99.185.100:443 TIME_WAIT TCP 192.168.150.32:49952 192.168.150.30:135 ESTABLISHED TCP 192.168.150.32:49953 192.168.150.30:49155ESTABLISHED TCP 192.168.150.32:49955 74.125.226.48:443 ESTABLISHED TCP 192.168.150.32:49957 74.125.226.38:443 ESTABLISHED TCP 192.168.150.32:49958 74.125.141.95:443 ESTABLISHED TCP 192.168.150.32:49959 74.125.226.55:443 ESTABLISHED TCP 192.168.150.32:49960 74.125.226.35:443 ESTABLISHED TCP 192.168.150.32:49961 74.125.226.48:443 ESTABLISHED TCP 192.168.150.32:49962 74.125.226.47:443 ESTABLISHED TCP 192.168.150.32:49965 74.125.141.95:443 ESTABLISHED TCP 192.168.150.32:49968 74.125.226.47:443 ESTABLISHED TCP 192.168.150.32:49976 192.168.150.30:135 TIME_WAIT TCP 192.168.150.32:49977 192.168.150.30:49155ESTABLISHED TCP 192.168.150.32:49980 74.125.226.55:443 ESTABLISHED TCP 192.168.150.32:49981 38.113.165.101:443 TIME_WAIT TCP 192.168.150.32:49988 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:49989 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:49998 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50000 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50004 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50022 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50024 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50034 74.125.226.35:443 ESTABLISHED TCP 192.168.150.32:50042 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50054 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50059 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50089 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50110 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50113 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50126 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50127 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50128 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50133 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50134 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50135 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50148 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50151 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50183 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50193 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50209 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50225 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50226 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50229 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50246 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50247 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50248 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50262 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50266 192.168.150.1:9999 TIME_WAIT TCP 192.168.150.32:50267 192.168.150.1:9999 TIME_WAIT UDP 0.0.0.0:123 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:3389 *:* UDP 0.0.0.0:3391 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:51973 *:* UDP 0.0.0.0:51975 *:* UDP 0.0.0.0:51976 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:53451 *:* UDP 127.0.0.1:53454 *:* UDP 127.0.0.1:61376 *:* UDP 127.0.0.1:62320 *:* UDP 127.0.0.1:62321 *:* UDP 127.0.0.1:62511 *:* UDP 127.0.0.1:63318 *:* UDP 192.168.150.32:137 *:* UDP 192.168.150.32:138 *:* UDP 192.168.150.32:1645 *:* UDP 192.168.150.32:1646 *:* UDP 192.168.150.32:1812 *:* UDP 192.168.150.32:1813 *:* UDP 192.168.150.32:1900 *:* UDP 192.168.150.32:53450*:*

我的猜测是Windows 7使用IP源路由，所以数据包首先发送到彭博路由器，然后通过专用networking转发它们。服务器可能已禁用源路由，因此数据包发送到本地网关/防火墙/路由器可能没有路由表中的彭博路由器作为这些IP的路由。