Windows Server 2008 Network Issues - Unable to contact IP driver error code 1753

Hi,

Having even more issues with our Exchange 2007 Windows 2008 server. Currently e-mail is working fine although the system attendent process won't start. I can browse the internet from the server but I cannot ping from it (including pings to 127.0.0.1), or connect to it remotely.

I want to see if there is anything I can do to fix it as Microsoft support say they think the TCP-IP stack has become corrupted, and that all I can do to fix this is to is re-install the OS. I haven't tried a new network card as yet, but if it's a stack issue this obviously won't help.

Thanks in advance.

padiap
Ping-Error.JPG
Network-Card.JPG
Network---Sharing-Center.JPG
padiapAsked:
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.

padiapAuthor Commented:
Hi dariusg,

Appreciate the quick response and apologies for my delayed reply. Those fixes look likely to resolve the issue. I will attempt them next week (currently working on some mailbox migrations) and get back to you with the results.

Cheers,

padiap
padiapAuthor Commented:
Hi dariusg,

Thanks again for the links. I attempted the Microsoft support link and I can now ping successfully. However for some reason I can't add/remove/see any roles installed on the server. I will be giving the other links a try asap and will then post the results.

Cheers,

padiap
JavaScript Best Practices

Save hours in development time and avoid common mistakes by learning the best practices to use for JavaScript.

Darius GhassemCommented:
Just let me know.
padiapAuthor Commented:
Hi dariusg,

I ran the ip reset and rebooted but the old issue then came back. I then tried re-running the winsock reset which unfortunately didn't make a difference as it did last time.

Cheers,

padiap
Darius GhassemCommented:
Once you did the reset did you restart the computer?
padiapAuthor Commented:
Hi dariusg,

Sure did, a couple time just to be sure. Then re-ran the winsock reset (as stated above). 24 hours later I re-ran the winsock reset again and I can ping in/out again but still having the other networking issues. Might have to bite the bullet and rebuild.

Cheers,

padiap

Experts Exchange Solution brought to you by

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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.