• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Server 2003 to 2008R2 Migration

J

jbont

Junior Member
I have just migrated from a Server 2003 standard to Server 2008R2 standard. The migration has gone great. All of the roles have transferred over and by all accounts everything seems to work correctly. BUT when the old 2003 server is removed from the network the new 2008 server drops almost 50% of the packets to the internet gateway. The new server can PING all of the other device on the local network without dropping any packets. Other workstations on the network can PING the internet gateway without dropping a single packet. When the old server is on the local network the new server can PING the gateway without dropping any packets. I have spent a couple of days trying to get to the bottom of this. Please help!!
 
Are you pinging by name or IP? It really shouldn't matter, but I could see Windows doing stupid shit with DNS even just for a ping.
 
Having done about a bazillion migrations, one thing I notice is that even after DCPROMOing the losing server down (you did DCPROMO down the old server right?), DNS is a mess. It still has remnants of the old server.

MSFT recommends running the Internet Connection Wizard (ICW) on the winning server after the losing server is DCPROMOed down.

I usually just do into DNS and get rid of anything old server but be really careful and take your time. You have to dig several levels deep when doing this.

Be sure you are running a proper reverse DNS zone.

Also, check your DHCP to see what you are handing out for DNS servers. Make sure only your current DCs are listed and you are not handing out any public DNS - even as secondary or tertiary. DCs only. Check the DNS Search Domain you're handing out as well.

I like to use GRCs DNS Benchmark software to test my DNS environment. Anything less than 100% usually indicates you have a problem somewhere.
 
IPV6 and Flow control are network settings i'd take a close look at.

It is not acceptable to disable IPV6 on server's any more but may be necessary if your hardware infrastructure can't handle it.

Flow control, well your managed switch you can set it up or not but i strongly suggest NOT enabled if it is not a iscsi target.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top