Problems 2003 -> 2008 R2 Update

A

AlliumPorrum

New member
Joined
Jan 2, 2011
Messages
3
Location
Finland
I just upgraded (or; re-installed) my olde goode 2003 server to 2008 R2, and everything seems to be quite OK now. But, for some reason I just cannot get any connection to my server outside from my D-Link firewall. I've been using some services like SVN, FTP, Tversity and Remote Desktop thru my firewall with my 2003 server, and everything worked just fine. After the 2008 R2 installation everything is working OK inside my own network, but I cannot get any connections from internet to my new server. List of things I already did:

- all ports are forwarded from D-Link just like before, and I checked that the port numbers are OK
- checked that all the services are allowed on Windows firewall
- I also added the needed ports manually to the firewall, just to be sure
- checked that the IP- address in my DynDNS service is correct, I'm using the update client on my server
- tried even to turn my Comodo virus software off

But nothing works, when I try to connect any of my services with dyndns name, i just get the "connection failed" error.

Any ideas what to do?? Is there something totally different with 2008 R2 that I should understand to do to allow connections from outside world??
 
Now I found out lots of discussions about RDS CAL's and such. Is it really so that it is impossible to get remote connection to R2 server without paying more license fees to M$??
 
You should still be able to get your 2 administrative sessions without paying for more licenses. Check your event logs. If the connection is making it to the server and being denied at the server, there should be a log entry. Check your firewall again. Make sure you have the target IP address correct in addition to the ports being forwarded. You may need to install a program like Netmon or wireshark to view the packets coming in and see what is going on.
 
Matt said:
You should still be able to get your 2 administrative sessions without paying for more licenses. Check your event logs. If the connection is making it to the server and being denied at the server, there should be a log entry. Check your firewall again. Make sure you have the target IP address correct in addition to the ports being forwarded. You may need to install a program like Netmon or wireshark to view the packets coming in and see what is going on.
Click to expand...

Very good point Matt, thanks!

Indeed there isn't any log entries on server when connecting thru DynDNS and D-Link, so the problem must be on on either of them. I re-re-re-checked the IP & port settings from D-Link, and they must be OK (for example, RD is forwarded on port 3389 and Tversity to 41952, these are the defaults and has not been changed). And I havent' changed them since the old 2003 server either. I don't think that is any other setting on D-Link that would prevent these connections..?

Is it possible that there is some new limitations or changes with the DynDNS service?? Should I be able to use it with https protocol or RD with 2008 R2? I also tried to copy the current IP address from DynDNS update client for the connection address but it did not help, so maybe the problem isn't here neither.
 
The DynDNS service should not care what service is being used. It's only function is to provide resolution of host name to an IP address. If you can do an NSLOOKUP from a command prompt on your remote client computer of your dyndns name and it returns the proper IP address, then any program running on that client should work. But if you can't resolve the hostname properly through nslookup, then something is either wrong with DynDNS or with whatever DNS service your client is using for name resolution.
 
Back
Top