We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Server 2000 issues on 2008 R2 domain

Medium Priority
316 Views
Last Modified: 2012-05-11
Hi All.

I have recently just upgraded our 2003 domain to 2008 R2.  Everything was fine before hand.

However, after the upgrade, I have a single 2000 member server which is being difficult.  This is what is happening:
1) Connections to the shares on the Server 2000 via IP address are slow, and timeout when scripts are used, and occasionally machines will not connect to the share.
2) Connections to the same shares via DNS work perfectly
3) Non-Domain machines are unable to connect to the shares at all.

Everything was fine before I did the upgrade, and extremely puzzled as to why this would have changed.  Any help will be appreciated.
Comment
Watch Question

AwinishSenior Solution Architect

Commented:
Windows 2000 lifetime period is over & even if you take up the issue with Microsoft, they will not be helping you as there might be issue but there is no more patches released & from security risk, you server can pose a threat to your environment due to missing patches in win2000.

I would suggest update the NIC card & server with latest firmware & driver might help you to resolve issues.

Commented:
I have seen an issue like this before I think on your servers you need to have qos installed not sure why this is.  I have fixed an issue with 2003 servers and 2008 servers doing this.

Author

Commented:
Hi Guys, sorry for the delay getting back, and thank you for your feed back.

I have been able to isolate the problem causing the above, and it is the firewall.

The RPC is trying to communicate accross our subnets, and is being blocked by our firewall.  The RPC is trying to communicate between ports 49152 - 65535.  I understand that this port ranges have been reduced from 1024 - 65535.

I can see from our firewall that port 1025 was open previously, but this does not seem to be sufficient from my understanding of the process.

Would anyone be able to recommend a best practice in reducing these ports down to allow through the firewall, and possibly know why this would have changed?

Thank you
Senior Solution Architect
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.