Unable to RDP to Main Server Internally Only

I am going crazy here.
I am unable to mstsc to the private IP of main server when I am locally on the lan.
If I mstsc to public IP address, I can log on to the server

I can mstsc to any computer on the LAN but the Server, I can mstsc from Server back to my laptop

Any questions please ask, I have never dealt with this, remote assistanct/rdp is turned on.
Thanks to anyone who responds.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

is port 3389 listening on the internal lan IP?

use netstat -a -n on the server to determine this.  The output should say it is listening on that port on the LAN IP.  If not, check the Windows Advanced Firewall settings and make sure it isn't blocked.

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
suttons27Author Commented:
says Established, but does not say Listening
suttons27Author Commented:
Thank You "The Cleaner", I will award you the points, but don't want to close the answer just yet, hoping you could possible respond to one more question.

I just went and opened port 3389 on advanced firewall, tested...works fine.

My alt question, what would have caused that? An update? Just akward that it just stopped all of a sudden, the new system has been up and running for several months.

Thanks, once again.
Not that I'm aware of (update wise).  I've got servers running R2 that have been patched completely and don't have this issue.  Possibly 3rd party software could interfere, such as Symantec or other A/V products, but they typically don't change the Windows Firewall rules themselves.
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.