On 14 Jun, 19:46, Doug P <D...@discussions.microsoft.com> wrote:
> Make sure that on the internal NIC you are not specifying a default gateway.
> You can see what your default gateway is by doing a route print from the cmd
> line. We had similar problems which this fixed.
>
>
>
> "JayBee" wrote:
> > Firstly I hope I'm putting this in the right place, I'm not entirely
> > sure that it is a networking problem, but thats the best I can narrow
> > it down to.
>
> > I have a number of servers at a data centre for our company. Of these
> > servers we are having problems with just one. This one server is being
> > used as our webserver, this connects to a backend DB server.
>
> > Webserver
> > ----------------
> > Dual Woodcrest Xeon 5110 (Dual Core) CPU
> > 2Gb RAM
> > 136GB RAID 1 HDD
> > Dual BroadCom NetXtreme Gigabit Ethernet NIC's
> > Windows Server 2003 + all SP's / Updates
> > IIS 6.0
> > PHP5
> > Symantec AV Server
>
> > DB Server
> > ---------------
> > Dual Woodcrest Xeon 5110 (Dual Core) CPU
> > 4GB RAM
> > 136GB RAID 1 HDD
> > Dual BroadCom NetXtreme Gigabit Ethernet NIC's
> > Windows Server 2003 + all SP's / Updates
> > MS SQL Server 2000 Enterprise
> > MySQL 5.0
> > Symantec AV Server
>
> > Both servers are configured with an internal network and an external
> > network, all server to server communication is setup to run on the
> > internal network (192.168.0.x).
>
> > The problem occurs fairly randomly between every 12 and 24 hours. The
> > webserver loses the connection to the DB server, so our website
> > frontpage produces an error "MS OLE DB Provider for SQL Server Error
> > 80004005", we will also lose our vBulletin Forum and our Kayako
> > Support Suite. The website uses the MS SQL server and the Forum/
> > Support use MySQL.
>
> > When this problem occurs you can connect to the webserver via Terminal
> > Services. When I connect I can see no traffic moving through the
> > internal interface at all, and I can't connect to the DB server via
> > telnet. However the webserver can be pinged internally from other
> > servers and externally from the web.
>
> > I have tried uninstalling and reinstalling the network drivers, I have
> > also tried uninstalling and reinstalling TCP/IP. I have swapped the
> > disks into new identical hardware. Then as a final resort I moved all
> > the websites to a brand new server that was freshly installed.
>
> > The problem still occurs, there are no errors beaming at me in the
> > event log, there are no errors standing out in the IIS logs and I'm
> > pulling my hair out looking for a solution to a problem that I can't
> > work out.
>
> > I hope someone can help.- Hide quoted text -
>
> - Show quoted text -
Thanks for the suggestion, the network card for the internal network
only has it's IP address and subnet mask set, no default gw.
|