This computer can't connect to the remote computer

One of my clients has recently updated their firewall to a SonicWall.  Prior to the inclution of the firewall we could connect using RDP without any problem.

When we connect now we get a connection error as detailed in the title.  
we connect from a glasgow office on the public ip of our client.  if someone out side our office connects it works fine.  inside the office we can connect using the same method to other clients without any issue. we use a watchguard firewall and on the client side they have created a rule allowing our public ip access to a server within their lan on port 3389 but still no joy.  Even when 3389 is open to all our ip still has a problem connecting.
anthonyhoulihanAsked:
Who is Participating?
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
 
lavazzzaCommented:
If I am reading this right, you can access this particular machine from everywhere but the Glasgow office.  They are running a Sonicwall firewall with an access rule allowing 3389 connections from any address and still they cannot be reached by your office, which uses a watchguard FW, in glasgow.  I would first check all outbout ACL's on the Glasgow side and see what, if anything, is blocked.  It has been a while since I fiddled with a Watchguard, but I know that it can perform egress filtering.

We know that the issue is not on the Client side since it is fully capable of PAT'ing for other offices.  And while it would seem that the change of firewall on your client's network would be the cause, it could be a coincidence.
0
 
anthonyhoulihanAuthor Commented:
I agree on the last comment however the outbound rule is to allow everything. I maybe should have said that we also connect from the glasg

news from the client

the client setup the IP of the glasgow office to be an address object then allowed 3389 to the internal server from the created 'Address object'.  I asked them to delete that address object and tested..... low and behold it works just fine!  So now just to figure out how to lock down the sonic wall to just our IP addy.......... Well I suppos that's up to them to sort out but thank you for the comment and in this case...... turned out to be the client side firewall!!!!
0
 
lavazzzaCommented:
wow, I wonder if when they created a rule on thier firewall to allow specifically your network that they actually denied it? go figure.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.