Strange Remote desktop connection problem
Our setup is the following :
A remote site, hosting 2 physical servers (Windows 2003 R2 SP2) lets call them sgood and sbad . Each one has a different Public IP, although theyre behind the same router.
Our company uses sgood and sbad for similar purposes, all of them using remote desktop connections.
Normally our users would start rdp in any or both servers, and use some applications, including office 2007. We have been using this scheme for years.
For reasons we still dont understand, this week, connections from inside the company to sbad, started having problems, while connections made to sgood still worked. The strange thing is that connections started from outside the office to both sbad and sgood work just fine, so the only problem we have is related to connections to sbad from inside the office.
The problem seems to lessen while the number of users connected goes down, but this is puzzling because weve had much higher workloads and theres never been a problem.
We suspected on the firewall/router, changed it and still have the problem. Remember that any connection from outside the office works fine.
Resetting the server, firewalls, routers didnt help. Packet monitoring between both ips, shows normal 3389, and other standard protocols used in this type of connection.
We may discard a network interface problem since on one hand, connections from outside the office work fine, and on the other, connections from inside the office to sgood, work just fine.
I suspect of a routing problem betwen office ip, and sbad ip, is that possible ?
Any ideas ?
A remote site, hosting 2 physical servers (Windows 2003 R2 SP2) lets call them sgood and sbad . Each one has a different Public IP, although theyre behind the same router.
Our company uses sgood and sbad for similar purposes, all of them using remote desktop connections.
Normally our users would start rdp in any or both servers, and use some applications, including office 2007. We have been using this scheme for years.
For reasons we still dont understand, this week, connections from inside the company to sbad, started having problems, while connections made to sgood still worked. The strange thing is that connections started from outside the office to both sbad and sgood work just fine, so the only problem we have is related to connections to sbad from inside the office.
The problem seems to lessen while the number of users connected goes down, but this is puzzling because weve had much higher workloads and theres never been a problem.
We suspected on the firewall/router, changed it and still have the problem. Remember that any connection from outside the office works fine.
Resetting the server, firewalls, routers didnt help. Packet monitoring between both ips, shows normal 3389, and other standard protocols used in this type of connection.
We may discard a network interface problem since on one hand, connections from outside the office work fine, and on the other, connections from inside the office to sgood, work just fine.
I suspect of a routing problem betwen office ip, and sbad ip, is that possible ?
Any ideas ?
kavlins
Is that Cisco routers at both sites ? If yes , how do u connect to remote site from inside and outside office ? Cisco VPN Client ? Give more info....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What troubleshooting did you attempt with the 50b? I would try running a packet capture, and then exporting that capture to a pcap file for viewing in Wireshark. I would also manual set the interface speed of the NIC on the server in question to the desired speed. I have seen autonegotiate fail occassionaly and produce strange results.
Checkout the following Fortinet Knowledge center article on using the built in sniffer to the product.
http://kc.forticare.com/default.asp?id=1186&Lang=1&SID=
You will need the Perl libraries installed in order to change the output into a pcap file for use in Wireshark.
Checkout the following Fortinet Knowledge center article on using the built in sniffer to the product.
http://kc.forticare.com/default.asp?id=1186&Lang=1&SID=
You will need the Perl libraries installed in order to change the output into a pcap file for use in Wireshark.