Main Forum > Tweaking.com Support & Help
repair failed to start (SOLVED)
Shane:
Im sorry, I totally missed that you are trying on Windows 2003 server.
I was answering 20+ posts and so for so dang reason I spaced the version of Windows you are on.
The repairs are not testing on Windows 2003 server, and it might be that the windows 2003 server may not allow the program to make the service. Server OS have a lot of differences from the workstations, so I wouldnt recommend running the repairs on 2003.
What problems are you trying to fix on 2003?
Shane
beelectronics:
I can't ping any nodes on the network. I can ping myself, but all others I get a destination not reachable.
Cable is plugged in and I get link lights on both sides.
Tried different port on the switch.
Tried different NIC.
ran netsh winsock reset and netsh int ip reset c:reset.log
The scariest of all...
If I try to browse the network in File Explorer, I get that I don't have access to the domain. But, this machine is the domain server!!
I had one drive of a mirrored pair go out and replaced it. When I restarted, I got this problem. The mirror resynced successfully.
I'm at a loss as to what happened or how to fix it.
If you can think of something to help, it would be much appreciated.
Shane:
Ok try this, grab my technicians toolbox
http://www.tweaking.com/content/page/tweaking_com_technicians_toolbox.html
Direct download is here
http://www.tweaking.com/files/setups/tweaking.com_technicians_toolbox_setup.exe
(I havent tested this on 2003, but far as I know I am not using any APIs that are not in 2003 R2)
Open the program and go to network tools and then IP Address Scanner.
have it scan the network and let me know if ti works, should be fast. It is sending a ping to the Ip range and does them all at once so normally it takes about 3 or 4 secs to finish.
Let me know if it returns any results or not.
Shane
beelectronics:
I can't get back to the server today.
But, I did try pinging several devices before. All I got was destination host unreachable except when I pinged the server's own address. That one pinged fine. That's why I tried the cable and a different port on the switch.
I'm stumped right now.
Shane:
Thats why I want to try the toolbox and see if it works, it uses a different API and so if it works and the ping in cmd.exe doesnt then that gives me an idea where to start looking. But if the toolbox also fails using the api then that tells me it is most likly something corrupt with the network registry keys, which if that is the case then totally yanking the network card and drivers out of device manager, running all the network reset commands and rebooting should get windows to write those registry keys fresh again.
Of course "should" is the magic word lol
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version