Server 2003 is going off support next year anyway. I consider my bacon saved yesterday!Sorry, Tim, but that was Adam as well. 0 This discussion has been inactive for over a year. Thread Tools Search Thread Advanced Search 19th June 2009,03:41 PM #1 ianniow Join Date Oct 2005 Location Isle of Wight Posts 144 Thank Post 9 Thanked 12 Times in 11 it will tell you will have to reconfigure later on which is ok! 0Votes Share Flag Collapse - Thanks! Send PM 22nd June 2009,09:34 AM #11 ianniow Join Date Oct 2005 Location Isle of Wight Posts 144 Thank Post 9 Thanked 12 Times in 11 Posts Rep Power 25 http://sauvblog.com/cannot-ping/cannot-ping-server-2003-from-windows-7.html
Originally I had static addressing on both (I don't want to use DHCP). Well, now to cancel the afterhours critical support case with Microsoft. Share This Page Legend Correct Answers - 10 points Log In E-mail or User ID Password Keep me signed in Recover Password Create an Account Blogs Discussions CHOOSE A TOPIC Please type your message and try again. 2 Replies Latest reply: Mar 26, 2014 10:05 PM by jalaladdin client cannot ping server2003 but server can ping client(windows xp) jalaladdin Mar 26, http://www.techrepublic.com/forums/discussions/windows-2003-firewall-not-working-conflict-with-ipnatsys/
whether you use Bridged, NAT or Host-Only networking, and whether the 192.168.1.1 IP address is unique in your network. Do you have a firewall enabled? So now I have one NIC enabled with a static address and can ping to and from the server.
The server is in a different building as part of a server farm, so if I restart, I need to get permission to go into the server room before I can I had to manually reboot it a couple of time to get it working again.[/i] Back to top graycatSF ModJoined: 29 Apr 2005Posts: 16777195Location: London, UK Posted: Tue Jul 29, 2008 Ben Lloyd replied Sep 14, 2010 The most likely cause is going to be the Windows Firewall running on the server's network connection which is preventing the inbound ping. James Ogutu replied Sep 14, 2010 Hey Germain Disable your windows firewall, try pinging the server from another client comp. , If the ping is successful, then reconfigure your firewall to
SEO by vBSEO ©2011, Crawlability, Inc. The APIPA address....wil be assigned to dial-in clients. by jtan · 10 years ago In reply to I found the solution Hey abahou,Thanks mate, totally worked. http://stackoverflow.com/questions/13644900/ipnat-sys-running-after-reboot-stopping-connection-to-server Tim 0 Chipotle OP Helpful Post jhodges at Camino Global Sep 14, 2014 at 10:15 UTC Tim3042 wrote: I get a message saying "windows firewall cannot run because
http://social.technet.microsoft.com/Forums/windowsserver/en-US/cfc1a76b-fab3-478a-b2f4-1939a559590a/... 1 Sonora OP TimLang Sep 14, 2014 at 10:50 UTC Yes, a quick search on IPNAT.sys took me to an old thread explaining to stop RRAS, start bora cheang replied Oct 18, 2010 Please recheck in windows xp client firewall make sure that it allow ping from outbound or disable windows firewall. floyddroid replied Sep 14, 2010 The fact that you can't ping the server shouldn't be an issue. Cannot even ping server, however, can ping the gateway.
Clients still unable to connect to server or internet. http://networking.ittoolbox.com/groups/technical-functional/networkadmin-l/unable-to-ping-windows-server-2003-r2-3756155 I thought by disabling the NIC that was not connected, it would have no effect on the server's configuration, but apparently it does. Creating your account only takes a few minutes. Send PM 19th June 2009,04:41 PM #5 ianniow Join Date Oct 2005 Location Isle of Wight Posts 144 Thank Post 9 Thanked 12 Times in 11 Posts Rep Power 25
Now I just need to find out what is causing IPNAT.sys to run on boot up. –Brant Sep 17 '13 at 22:53 add a comment| 3 Answers 3 active oldest votes navigate here Thanks again, Germain ICT Teacher Top Best Answer 1 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Happy Hunting. -jonH 0 Jalapeno OP Adam9204 Sep 14, 2014 at 12:16 UTC Hi, Check that something hasn't happened to your DHCP pool, i.e it's no longer configured. I explained the changes I made in my previous reply.
Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. Select forumWindowsMac OsLinuxOtherSmartphonesTabletsSoftwareOpen SourceWeb DevelopmentBrowserMobile AppsHardwareDesktopLaptopsNetworksStoragePeripheralSecurityMalwarePiracyIT EmploymentCloudEmerging TechCommunityTips and TricksSocial EnterpriseSocial NetworkingAppleMicrosoftGoogleAfter HoursPost typeSelect discussion typeGeneral discussionQuestionPraiseRantAlertTipIdeaSubject titleTopic Tags More Select up to 3 tags (1 tag required) CloudPiracySecurityAppleMicrosoftIT EmploymentGoogleOpen SourceMobilitySocial Reset Post Submit Post Operating Systems Forums Windows · 64,770 discussions Mac OS · 882 discussions Linux · 4,410 discussions Other · 196 discussions Latest From Tech Pro Research Research: Automation Check This Out Just need to be sure that I will not be creating even more problems for myself.
After rebooting the server the same issue comes back and can be resolved as above. I had tried that earlier but I kept getting the "windows firewall cannot run..(Ipnat.sys)." So that caused me more anxiety. but i can start "Routing and Remote Access" manually. Has anyone seen this behavior before, any idea what can be causing this, how to repair it? please help!Thanks Edited by Jethro Thursday, October 16,
I needed to promote this as ... Then this morning I had to reboot the server. Browse other questions tagged networking reboot windows-firewall windows-2003-webserver or ask your own question. Sorry for my poor grammar, and hope this will eliminate some of you who having the same pain as I am. =) share|improve this answer answered Oct 28 '13 at 2:54
After investigation we found that IPNAT.sys was running and that the command NET STOP IPNAT resolved the issue and everything came back. It seems that the workstation is blocking all incoming network traffic. there is no other firewall installed on this machine.Windows firewall service is disabled, and has no IPSec Policy is applied. I recall that 1) A few A 0 Sonora OP TimLang Sep 13, 2014 at 11:52 UTC I can access the internet, ping my terminal server and gateway device. this contact form For example I am not able to Remote Desktop (Remote desktop is enabled) neither to ping this machine.
I had the problem of no one being to access DNS or ping the forest root. After restarting the computer a few times, I was able to ping the server. Germain Anthony replied Oct 19, 2010 I want to list my issue as solved. Network Security Tools Network Access Control Network Auditing Patch Management Portable Storage Security Security Scanners VPNs Web Application Security Web Content Security WhitePapers Featured Products TechGenix Sites ISAserver.org The No.1 Forefront
I don't know HOW that issue began, as I had not made any changes to RRAS or Firewall. Congratulations! whew; that was a tough one. I have just gone throught the event log from start up and very early on I gat the error ipnathlp event id 32009 stating that the firewall etc could not start All rights reserved.
Any way to see what might be using ipnat.sys? Another tip - disable power saving mode on both NICs so they don't shut off in the middle of the day! The time now is 12:11 PM. You're now being signed in.
Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... I needed to promote this as a DC following a ctastrophic failure of my main DC so I need full network functionality. I searched it and found a thread within a couple minutes. When trying to get into the Windows Firewall, I got the following error: "Windows Firewall cannot run because another program or service is running that might use the network address translation
Germain Anthony replied Sep 14, 2010 Lloyd, You won't believe it but a just few moments ago I was able to ping the server. I ran the command NET STOP IPNAT.SYS and SC STOP IPNAT.SYS and got the same message again. Privacy statement © 2016 Microsoft.