|
|
|
AyaNova Sales & Support
Group: Administrators
Last Login: Today @ 8:48:24 AM
Posts: 2,190,
Visits: 5,028
|
|
| Did you re-apply your driver? Did you do as suggested above 500 error means there is something wrong on the server side - it could mean hardware, it could mean drivers, it could be access rights, it could mean software, it could mean a problem with IIS and .NET - exactly what it is it doesn't say. A suggestion may be to run the .NET repair in case there is an issue with .NET and IIS such as on http://forum.ayanova.com/Topic2334-95-1.aspx?Highlight=.net+repair Or there may be a problem with IIS itself, or it may be that you do not have all of the operating systems recommended updates from Windows. Other than that, I would suggest starting from scratch and double-checking everything. Did you check your hardware? Did you check your drivers? Did you check the access - IIS, firewall, etc? Did you check IIS? Did you run a repair on .NET? Did you run a repair on IIS? DId you check for Windows updates? These are some suggestions to troubleshoot why you are experiencing an issue pinging your own ip address. Do post back and let us know what you find. - Joyce
- AyaNova Sales & Technical Support
- http://www.ayanova.com
|
|
|
|
Posted 6/15/2007 10:22:51 AM
