server not accessible

  • Thread starter Thread starter Patrick D.
  • Start date Start date
P

Patrick D.

Guest
Hi,

I have a webserver (windows 2003 standard) within a virtual system.

The server wasn't reachable during a critical amout of time and I need to
checkout if the reason came from my virtual instance or not.

Beside the fact, that the event logs don't show any errors, there is one
thing which is strange for me: The security event log usually shows daily
events 552 (user: system, source: security), bot NOT during the two days,
when the server was not accessible.
In fact there is no entry in eventlog/security at all during the time, when
I couldn't access my server.

The server IS accessible now, because of a reboot by the hoster.

If you wouldn't see any errors in the log files, what would you think about
a virual webserver, which was not accessible?
Shouldn't it rather be the host-system or a different source "outside" the
virtual instance?

(of course I didn't switch the settings of the firewall)

Thanks a lot for your ideas.

Patrick
 
RE: server not accessible

Patrick,
What "virtual system" are you using? There are known issues with certain
versions of VMWare and NIC cards doing just what you've described that would
temporarily be fixed with a reboot.

"Patrick D." wrote:

> Hi,
>
> I have a webserver (windows 2003 standard) within a virtual system.
>
> The server wasn't reachable during a critical amout of time and I need to
> checkout if the reason came from my virtual instance or not.
>
> Beside the fact, that the event logs don't show any errors, there is one
> thing which is strange for me: The security event log usually shows daily
> events 552 (user: system, source: security), bot NOT during the two days,
> when the server was not accessible.
> In fact there is no entry in eventlog/security at all during the time, when
> I couldn't access my server.
>
> The server IS accessible now, because of a reboot by the hoster.
>
> If you wouldn't see any errors in the log files, what would you think about
> a virual webserver, which was not accessible?
> Shouldn't it rather be the host-system or a different source "outside" the
> virtual instance?
>
> (of course I didn't switch the settings of the firewall)
>
> Thanks a lot for your ideas.
>
> Patrick
 
RE: server not accessible

Hi and thanks a lot for your answer:

In fact I cannot access the virtualisation system. I have admin access to
the virtual server, that's it. This is a virtual hosting solution, a virtual
dedicated server for webhosting.
The system, which the hoster is using, is Citrix Xen Server.
The thing is, that I would like to "guess" if it is a possible problem of
the hoster. I cannot see any harmful entries on my virtual server.

What would you do to know the "truth"?

Patrick

"dwhagerman" wrote:

> Patrick,
> What "virtual system" are you using? There are known issues with certain
> versions of VMWare and NIC cards doing just what you've described that would
> temporarily be fixed with a reboot.
>
> "Patrick D." wrote:
>
> > Hi,
> >
> > I have a webserver (windows 2003 standard) within a virtual system.
> >
> > The server wasn't reachable during a critical amout of time and I need to
> > checkout if the reason came from my virtual instance or not.
> >
> > Beside the fact, that the event logs don't show any errors, there is one
> > thing which is strange for me: The security event log usually shows daily
> > events 552 (user: system, source: security), bot NOT during the two days,
> > when the server was not accessible.
> > In fact there is no entry in eventlog/security at all during the time, when
> > I couldn't access my server.
> >
> > The server IS accessible now, because of a reboot by the hoster.
> >
> > If you wouldn't see any errors in the log files, what would you think about
> > a virual webserver, which was not accessible?
> > Shouldn't it rather be the host-system or a different source "outside" the
> > virtual instance?
> >
> > (of course I didn't switch the settings of the firewall)
> >
> > Thanks a lot for your ideas.
> >
> > Patrick
 
Back
Top