Can't access open port after server migration

[debiken]

Hi-

Just migrated a Windows 2003 server to 2008 R2, lots of new stuff here! I had a port open on 2003 for a type to learn app students were using. The rule in the firewall migrated over to the new server, but when I try to access it on the new server it is blocked. I cannot figure out why! Guessing it has something to do with all the new advanced security features, but I am at a loss. If anyone has experienced this or has any suggestions, please let me know!

Thanks in advance..

[SYNACK]

Check the firewall and see what profiles it is enabled for, your link may be detected as something other than waht is allowed like public instead of domain.

[debiken]

Thanks for the quick reply. I am opening port 3000, under profiles I have all (domain, public, private) selected, under Scope I have Local - Any IP Address, Allowed users ANY and allowed computers ANY. Do I need to setup something anywhere else other than Windows Firewall? We have a SonicWall appliance for blocking/allowing internet traffic but no settings were changed on it. I have the new server using the same IP address and server name as the old server had, so no .ini settings would need to be changed either. Maybe it's in the application, if it's not specifically "listening" for traffic. How can i find out if I'm able to get to port 3000?

[bart21]

i would disable the windows firewall and test

 

nick

[FN-GM]

as @bart21 says try that with Windows Firewall. Is your default gateway set right on your new server?