Server 2003 (x86) connectivity problems

Here is the situation…

The network had 2 servers and 15 workstations. Both servers running Server
2003 (x86) and the domain is very fresh and clean. The computers are brand
new Dell OptiPlex workstations running XP Pro. The PDC is a server I built
several years ago. Intel 845 (I think) server board, 2 GB ECC RAM, RAID 1
SATA storage. In addition to being the PDC is also hosts files, printers,
DNS, DHCP and WINS. That server has no problems as all. The problem is with
the other server which is also a domain controller except it is running Juris
(SQL Express 2005 with an IIS front end) Backup Exec 12 and Lotus Domino
Server R5.0.11. Originally that was all running on a Dell SC1500 (a P3
server) which is where the problem started. The problem is simple; the
server stops communicating with the network. According to the server and the
switch, it is connected. However, it will not accept any incoming
connections, make any outgoing connections, or even respond to a ping. When
the server experiences this problem, it’s not specific to certain computers
or all computers. It is typically only about half that can’t talk to the
server and again, it’s not consistent. Assuming it was because the server
was so old, I recently upgraded the server to an HP ML310 G5. I have
transferred Backup Exec and Lotus Domino to the new server and the problem is
already starting to appear again – although not as bad yet. I think it may
have something to do with SQL Express 2005 because the new server showed no
signs of the problem until that install. However, since I have not moved
Juris yet, all SQL is doing right now is holding the Backup Exec database.

I’m pretty confident it’s not hardware. When the problem started, they were
using a very old Cisco Catalysis switch; they now have a 24 port managed
Linksys switch with 4 Gigabit ports for the servers. Their firewall/NAT
router is a Cisco ASA 5505. The building wiring is CAT5 (some CAT5e) and the
server patch cables are CAT6 – recently replaced.

Has anybody ever seen anything like this in the past? Again, I’m pretty
sure this is something that’s being causes by SQL Express 2005 but I’ve not
been able to figure it out for over 6 months now and I just don’t know what
else to look at. I'm pretty sure the problems started when I installed SQL
SP2 on the old server.

Thanks in advance for any input.

FYI: I have tried ping/trace tests from the switch itself and the traffic
still dies at the server.

Hello Gaven,

Please post an unedited ipconfig /all from both servers so that we can exclude
DNS as a problem. Since Windows 2000 there is no longer the PDC/BDC concept.
All DC's are the same and can host the 5 FSMO roles according to some rules.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Here is the situation.
>
> The network had 2 servers and 15 workstations. Both servers running
> Server 2003 (x86) and the domain is very fresh and clean. The
> computers are brand new Dell OptiPlex workstations running XP Pro.
> The PDC is a server I built several years ago. Intel 845 (I think)
> server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to being
> the PDC is also hosts files, printers, DNS, DHCP and WINS. That
> server has no problems as all. The problem is with the other server
> which is also a domain controller except it is running Juris (SQL
> Express 2005 with an IIS front end) Backup Exec 12 and Lotus Domino
> Server R5.0.11. Originally that was all running on a Dell SC1500 (a
> P3 server) which is where the problem started. The problem is simple;
> the server stops communicating with the network. According to the
> server and the switch, it is connected. However, it will not accept
> any incoming connections, make any outgoing connections, or even
> respond to a ping. When the server experiences this problem, it's not
> specific to certain computers or all computers. It is typically only
> about half that can't talk to the server and again, it's not
> consistent. Assuming it was because the server was so old, I recently
> upgraded the server to an HP ML310 G5. I have transferred Backup Exec
> and Lotus Domino to the new server and the problem is already starting
> to appear again - although not as bad yet. I think it may have
> something to do with SQL Express 2005 because the new server showed no
> signs of the problem until that install. However, since I have not
> moved Juris yet, all SQL is doing right now is holding the Backup Exec
> database.
>
> I'm pretty confident it's not hardware. When the problem started,
> they were using a very old Cisco Catalysis switch; they now have a 24
> port managed Linksys switch with 4 Gigabit ports for the servers.
> Their firewall/NAT router is a Cisco ASA 5505. The building wiring is
> CAT5 (some CAT5e) and the server patch cables are CAT6 - recently
> replaced.
>
> Has anybody ever seen anything like this in the past? Again, I'm
> pretty sure this is something that's being causes by SQL Express 2005
> but I've not been able to figure it out for over 6 months now and I
> just don't know what else to look at. I'm pretty sure the problems
> started when I installed SQL SP2 on the old server.
>
> Thanks in advance for any input.
>
> FYI: I have tried ping/trace tests from the switch itself and the
> traffic still dies at the server.
>

I am positive it's not a DNS problem.

IPConfig of the server with the problem:
Windows IP Configuration
Host Name . . . . . . . . . . . . : krsla-domino
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit
Server Adapter
Physical Address. . . . . . . . . : 00-21-5A-FF-AE-B4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.3.5
Primary WINS Server . . . . . . . : 192.168.3.5


IPConfig of the server that's fine:
Windows IP Configuration
Host Name . . . . . . . . . . . . : krslant1
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapter (10/100) #2
Physical Address. . . . . . . . . : 00-07-E9-F6-8C-D7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.3.7

"Meinolf Weber" wrote:

> Hello Gaven,
>
> Please post an unedited ipconfig /all from both servers so that we can exclude
> DNS as a problem. Since Windows 2000 there is no longer the PDC/BDC concept.
> All DC's are the same and can host the 5 FSMO roles according to some rules.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Here is the situation.
> >
> > The network had 2 servers and 15 workstations. Both servers running
> > Server 2003 (x86) and the domain is very fresh and clean. The
> > computers are brand new Dell OptiPlex workstations running XP Pro.
> > The PDC is a server I built several years ago. Intel 845 (I think)
> > server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to being
> > the PDC is also hosts files, printers, DNS, DHCP and WINS. That
> > server has no problems as all. The problem is with the other server
> > which is also a domain controller except it is running Juris (SQL
> > Express 2005 with an IIS front end) Backup Exec 12 and Lotus Domino
> > Server R5.0.11. Originally that was all running on a Dell SC1500 (a
> > P3 server) which is where the problem started. The problem is simple;
> > the server stops communicating with the network. According to the
> > server and the switch, it is connected. However, it will not accept
> > any incoming connections, make any outgoing connections, or even
> > respond to a ping. When the server experiences this problem, it's not
> > specific to certain computers or all computers. It is typically only
> > about half that can't talk to the server and again, it's not
> > consistent. Assuming it was because the server was so old, I recently
> > upgraded the server to an HP ML310 G5. I have transferred Backup Exec
> > and Lotus Domino to the new server and the problem is already starting
> > to appear again - although not as bad yet. I think it may have
> > something to do with SQL Express 2005 because the new server showed no
> > signs of the problem until that install. However, since I have not
> > moved Juris yet, all SQL is doing right now is holding the Backup Exec
> > database.
> >
> > I'm pretty confident it's not hardware. When the problem started,
> > they were using a very old Cisco Catalysis switch; they now have a 24
> > port managed Linksys switch with 4 Gigabit ports for the servers.
> > Their firewall/NAT router is a Cisco ASA 5505. The building wiring is
> > CAT5 (some CAT5e) and the server patch cables are CAT6 - recently
> > replaced.
> >
> > Has anybody ever seen anything like this in the past? Again, I'm
> > pretty sure this is something that's being causes by SQL Express 2005
> > but I've not been able to figure it out for over 6 months now and I
> > just don't know what else to look at. I'm pretty sure the problems
> > started when I installed SQL SP2 on the old server.
> >
> > Thanks in advance for any input.
> >
> > FYI: I have tried ping/trace tests from the switch itself and the
> > traffic still dies at the server.
> >
>
>
>

Hello Gaven,

This looks ok, but i would change the loopback address 127.0.0.1 to the real
ip address of the server. You said the half of the clients can not talk to
the server, how are the symptoms of this? Any errors in the event viewer?
Are all NIC drivers up to date? Do you use fixed speed and duplex settings,
especially with CISCO switches this often solves problems in our network,
they don't like the autonegotiation setting.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I am positive it's not a DNS problem.
>
> IPConfig of the server with the problem:
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : krsla-domino
> Primary Dns Suffix . . . . . . . : domain.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : domain.local
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : HP NC326i PCIe Dual Port
> Gigabit
> Server Adapter
> Physical Address. . . . . . . . . : 00-21-5A-FF-AE-B4
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.3.7
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.3.1
> DNS Servers . . . . . . . . . . . : 127.0.0.1
> 192.168.3.5
> Primary WINS Server . . . . . . . : 192.168.3.5
> IPConfig of the server that's fine:
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : krslant1
> Primary Dns Suffix . . . . . . . : domain.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : domain.local
> Ethernet adapter Local Area Connection 2:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
> Adapter (10/100) #2
> Physical Address. . . . . . . . . : 00-07-E9-F6-8C-D7
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.3.5
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.3.1
> DNS Servers . . . . . . . . . . . : 127.0.0.1
> 192.168.3.7
> "Meinolf Weber" wrote:
>
>> Hello Gaven,
>>
>> Please post an unedited ipconfig /all from both servers so that we
>> can exclude DNS as a problem. Since Windows 2000 there is no longer
>> the PDC/BDC concept. All DC's are the same and can host the 5 FSMO
>> roles according to some rules.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Here is the situation.
>>>
>>> The network had 2 servers and 15 workstations. Both servers running
>>> Server 2003 (x86) and the domain is very fresh and clean. The
>>> computers are brand new Dell OptiPlex workstations running XP Pro.
>>> The PDC is a server I built several years ago. Intel 845 (I think)
>>> server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to
>>> being
>>> the PDC is also hosts files, printers, DNS, DHCP and WINS. That
>>> server has no problems as all. The problem is with the other server
>>> which is also a domain controller except it is running Juris (SQL
>>> Express 2005 with an IIS front end) Backup Exec 12 and Lotus Domino
>>> Server R5.0.11. Originally that was all running on a Dell SC1500 (a
>>> P3 server) which is where the problem started. The problem is
>>> simple;
>>> the server stops communicating with the network. According to the
>>> server and the switch, it is connected. However, it will not accept
>>> any incoming connections, make any outgoing connections, or even
>>> respond to a ping. When the server experiences this problem, it's
>>> not
>>> specific to certain computers or all computers. It is typically
>>> only
>>> about half that can't talk to the server and again, it's not
>>> consistent. Assuming it was because the server was so old, I
>>> recently
>>> upgraded the server to an HP ML310 G5. I have transferred Backup
>>> Exec
>>> and Lotus Domino to the new server and the problem is already
>>> starting
>>> to appear again - although not as bad yet. I think it may have
>>> something to do with SQL Express 2005 because the new server showed
>>> no
>>> signs of the problem until that install. However, since I have not
>>> moved Juris yet, all SQL is doing right now is holding the Backup
>>> Exec
>>> database.
>>> I'm pretty confident it's not hardware. When the problem started,
>>> they were using a very old Cisco Catalysis switch; they now have a
>>> 24 port managed Linksys switch with 4 Gigabit ports for the servers.
>>> Their firewall/NAT router is a Cisco ASA 5505. The building wiring
>>> is CAT5 (some CAT5e) and the server patch cables are CAT6 - recently
>>> replaced.
>>>
>>> Has anybody ever seen anything like this in the past? Again, I'm
>>> pretty sure this is something that's being causes by SQL Express
>>> 2005 but I've not been able to figure it out for over 6 months now
>>> and I just don't know what else to look at. I'm pretty sure the
>>> problems started when I installed SQL SP2 on the old server.
>>>
>>> Thanks in advance for any input.
>>>
>>> FYI: I have tried ping/trace tests from the switch itself and the
>>> traffic still dies at the server.
>>>

I'll try changing the DNS IP setting. When the problem is active, the server
and any nodes it is trying to communicate with simply cannot see each other.
At that time, said nodes can still communicate with any other device on the
network and the server can still communicate with some of the other nodes.
Absolutely nothing in event viewer. All NIC drivers are up to date. I have
tried old NIC drivers and even swapped out NIC cards in the server and
workstations. Everything is autonegotiation. I don't think you can define
gigabit speed can you? Doesn't it require autoneg?

I'm pretty sure this has something to do with SQL 2005 Express.

"Meinolf Weber" wrote:

> Hello Gaven,
>
> This looks ok, but i would change the loopback address 127.0.0.1 to the real
> ip address of the server. You said the half of the clients can not talk to
> the server, how are the symptoms of this? Any errors in the event viewer?
> Are all NIC drivers up to date? Do you use fixed speed and duplex settings,
> especially with CISCO switches this often solves problems in our network,
> they don't like the autonegotiation setting.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > I am positive it's not a DNS problem.
> >
> > IPConfig of the server with the problem:
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : krsla-domino
> > Primary Dns Suffix . . . . . . . : domain.local
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : domain.local
> > Ethernet adapter Local Area Connection:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : HP NC326i PCIe Dual Port
> > Gigabit
> > Server Adapter
> > Physical Address. . . . . . . . . : 00-21-5A-FF-AE-B4
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.3.7
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.3.1
> > DNS Servers . . . . . . . . . . . : 127.0.0.1
> > 192.168.3.5
> > Primary WINS Server . . . . . . . : 192.168.3.5
> > IPConfig of the server that's fine:
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : krslant1
> > Primary Dns Suffix . . . . . . . : domain.local
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : domain.local
> > Ethernet adapter Local Area Connection 2:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
> > Adapter (10/100) #2
> > Physical Address. . . . . . . . . : 00-07-E9-F6-8C-D7
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.3.5
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.3.1
> > DNS Servers . . . . . . . . . . . : 127.0.0.1
> > 192.168.3.7
> > "Meinolf Weber" wrote:
> >
> >> Hello Gaven,
> >>
> >> Please post an unedited ipconfig /all from both servers so that we
> >> can exclude DNS as a problem. Since Windows 2000 there is no longer
> >> the PDC/BDC concept. All DC's are the same and can host the 5 FSMO
> >> roles according to some rules.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> Here is the situation.
> >>>
> >>> The network had 2 servers and 15 workstations. Both servers running
> >>> Server 2003 (x86) and the domain is very fresh and clean. The
> >>> computers are brand new Dell OptiPlex workstations running XP Pro.
> >>> The PDC is a server I built several years ago. Intel 845 (I think)
> >>> server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to
> >>> being
> >>> the PDC is also hosts files, printers, DNS, DHCP and WINS. That
> >>> server has no problems as all. The problem is with the other server
> >>> which is also a domain controller except it is running Juris (SQL
> >>> Express 2005 with an IIS front end) Backup Exec 12 and Lotus Domino
> >>> Server R5.0.11. Originally that was all running on a Dell SC1500 (a
> >>> P3 server) which is where the problem started. The problem is
> >>> simple;
> >>> the server stops communicating with the network. According to the
> >>> server and the switch, it is connected. However, it will not accept
> >>> any incoming connections, make any outgoing connections, or even
> >>> respond to a ping. When the server experiences this problem, it's
> >>> not
> >>> specific to certain computers or all computers. It is typically
> >>> only
> >>> about half that can't talk to the server and again, it's not
> >>> consistent. Assuming it was because the server was so old, I
> >>> recently
> >>> upgraded the server to an HP ML310 G5. I have transferred Backup
> >>> Exec
> >>> and Lotus Domino to the new server and the problem is already
> >>> starting
> >>> to appear again - although not as bad yet. I think it may have
> >>> something to do with SQL Express 2005 because the new server showed
> >>> no
> >>> signs of the problem until that install. However, since I have not
> >>> moved Juris yet, all SQL is doing right now is holding the Backup
> >>> Exec
> >>> database.
> >>> I'm pretty confident it's not hardware. When the problem started,
> >>> they were using a very old Cisco Catalysis switch; they now have a
> >>> 24 port managed Linksys switch with 4 Gigabit ports for the servers.
> >>> Their firewall/NAT router is a Cisco ASA 5505. The building wiring
> >>> is CAT5 (some CAT5e) and the server patch cables are CAT6 - recently
> >>> replaced.
> >>>
> >>> Has anybody ever seen anything like this in the past? Again, I'm
> >>> pretty sure this is something that's being causes by SQL Express
> >>> 2005 but I've not been able to figure it out for over 6 months now
> >>> and I just don't know what else to look at. I'm pretty sure the
> >>> problems started when I installed SQL SP2 on the old server.
> >>>
> >>> Thanks in advance for any input.
> >>>
> >>> FYI: I have tried ping/trace tests from the switch itself and the
> >>> traffic still dies at the server.
> >>>
>
>
>

Hello Gaven,

If your NIC's and the switch support GB no problem to set it to fixed one's.
We do it on our switches and servers.

Please describe "can not see each other", how dou you realize that?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I'll try changing the DNS IP setting. When the problem is active, the
> server and any nodes it is trying to communicate with simply cannot
> see each other. At that time, said nodes can still communicate with
> any other device on the network and the server can still communicate
> with some of the other nodes. Absolutely nothing in event viewer.
> All NIC drivers are up to date. I have tried old NIC drivers and even
> swapped out NIC cards in the server and workstations. Everything is
> autonegotiation. I don't think you can define gigabit speed can you?
> Doesn't it require autoneg?
>
> I'm pretty sure this has something to do with SQL 2005 Express.
>
> "Meinolf Weber" wrote:
>
>> Hello Gaven,
>>
>> This looks ok, but i would change the loopback address 127.0.0.1 to
>> the real ip address of the server. You said the half of the clients
>> can not talk to the server, how are the symptoms of this? Any errors
>> in the event viewer? Are all NIC drivers up to date? Do you use fixed
>> speed and duplex settings, especially with CISCO switches this often
>> solves problems in our network, they don't like the autonegotiation
>> setting.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I am positive it's not a DNS problem.
>>>
>>> IPConfig of the server with the problem:
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : krsla-domino
>>> Primary Dns Suffix . . . . . . . : domain.local
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : domain.local
>>> Ethernet adapter Local Area Connection:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : HP NC326i PCIe Dual Port
>>> Gigabit
>>> Server Adapter
>>> Physical Address. . . . . . . . . : 00-21-5A-FF-AE-B4
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.3.7
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.3.1
>>> DNS Servers . . . . . . . . . . . : 127.0.0.1
>>> 192.168.3.5
>>> Primary WINS Server . . . . . . . : 192.168.3.5
>>> IPConfig of the server that's fine:
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : krslant1
>>> Primary Dns Suffix . . . . . . . : domain.local
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : domain.local
>>> Ethernet adapter Local Area Connection 2:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
>>> Adapter (10/100) #2
>>> Physical Address. . . . . . . . . : 00-07-E9-F6-8C-D7
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.3.5
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.3.1
>>> DNS Servers . . . . . . . . . . . : 127.0.0.1
>>> 192.168.3.7
>>> "Meinolf Weber" wrote:
>>>> Hello Gaven,
>>>>
>>>> Please post an unedited ipconfig /all from both servers so that we
>>>> can exclude DNS as a problem. Since Windows 2000 there is no longer
>>>> the PDC/BDC concept. All DC's are the same and can host the 5 FSMO
>>>> roles according to some rules.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Here is the situation.
>>>>>
>>>>> The network had 2 servers and 15 workstations. Both servers
>>>>> running
>>>>> Server 2003 (x86) and the domain is very fresh and clean. The
>>>>> computers are brand new Dell OptiPlex workstations running XP Pro.
>>>>> The PDC is a server I built several years ago. Intel 845 (I
>>>>> think)
>>>>> server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to
>>>>> being
>>>>> the PDC is also hosts files, printers, DNS, DHCP and WINS. That
>>>>> server has no problems as all. The problem is with the other
>>>>> server
>>>>> which is also a domain controller except it is running Juris (SQL
>>>>> Express 2005 with an IIS front end) Backup Exec 12 and Lotus
>>>>> Domino
>>>>> Server R5.0.11. Originally that was all running on a Dell SC1500
>>>>> (a
>>>>> P3 server) which is where the problem started. The problem is
>>>>> simple;
>>>>> the server stops communicating with the network. According to the
>>>>> server and the switch, it is connected. However, it will not
>>>>> accept
>>>>> any incoming connections, make any outgoing connections, or even
>>>>> respond to a ping. When the server experiences this problem, it's
>>>>> not
>>>>> specific to certain computers or all computers. It is typically
>>>>> only
>>>>> about half that can't talk to the server and again, it's not
>>>>> consistent. Assuming it was because the server was so old, I
>>>>> recently
>>>>> upgraded the server to an HP ML310 G5. I have transferred Backup
>>>>> Exec
>>>>> and Lotus Domino to the new server and the problem is already
>>>>> starting
>>>>> to appear again - although not as bad yet. I think it may have
>>>>> something to do with SQL Express 2005 because the new server
>>>>> showed
>>>>> no
>>>>> signs of the problem until that install. However, since I have
>>>>> not
>>>>> moved Juris yet, all SQL is doing right now is holding the Backup
>>>>> Exec
>>>>> database.
>>>>> I'm pretty confident it's not hardware. When the problem started,
>>>>> they were using a very old Cisco Catalysis switch; they now have a
>>>>> 24 port managed Linksys switch with 4 Gigabit ports for the
>>>>> servers.
>>>>> Their firewall/NAT router is a Cisco ASA 5505. The building
>>>>> wiring
>>>>> is CAT5 (some CAT5e) and the server patch cables are CAT6 -
>>>>> recently
>>>>> replaced.
>>>>> Has anybody ever seen anything like this in the past? Again, I'm
>>>>> pretty sure this is something that's being causes by SQL Express
>>>>> 2005 but I've not been able to figure it out for over 6 months now
>>>>> and I just don't know what else to look at. I'm pretty sure the
>>>>> problems started when I installed SQL SP2 on the old server.
>>>>>
>>>>> Thanks in advance for any input.
>>>>>
>>>>> FYI: I have tried ping/trace tests from the switch itself and the
>>>>> traffic still dies at the server.
>>>>>

I'll try to forced speed setting next time I'm in.

When I say "cannot see each other" it's pretty much just that. The two
cannot successfully get any TCP/IP traffic to the other. No file sharing, no
smtp, no ping - nothing. The lack of connectivity is experienced on both
ends.

I tried upgrading to SQL 2008 Express, I'm hoping that may help as well.

Thanks again for the input.

"Meinolf Weber" wrote:

> Hello Gaven,
>
> If your NIC's and the switch support GB no problem to set it to fixed one's.
> We do it on our switches and servers.
>
> Please describe "can not see each other", how dou you realize that?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > I'll try changing the DNS IP setting. When the problem is active, the
> > server and any nodes it is trying to communicate with simply cannot
> > see each other. At that time, said nodes can still communicate with
> > any other device on the network and the server can still communicate
> > with some of the other nodes. Absolutely nothing in event viewer.
> > All NIC drivers are up to date. I have tried old NIC drivers and even
> > swapped out NIC cards in the server and workstations. Everything is
> > autonegotiation. I don't think you can define gigabit speed can you?
> > Doesn't it require autoneg?
> >
> > I'm pretty sure this has something to do with SQL 2005 Express.
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello Gaven,
> >>
> >> This looks ok, but i would change the loopback address 127.0.0.1 to
> >> the real ip address of the server. You said the half of the clients
> >> can not talk to the server, how are the symptoms of this? Any errors
> >> in the event viewer? Are all NIC drivers up to date? Do you use fixed
> >> speed and duplex settings, especially with CISCO switches this often
> >> solves problems in our network, they don't like the autonegotiation
> >> setting.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> I am positive it's not a DNS problem.
> >>>
> >>> IPConfig of the server with the problem:
> >>> Windows IP Configuration
> >>> Host Name . . . . . . . . . . . . : krsla-domino
> >>> Primary Dns Suffix . . . . . . . : domain.local
> >>> Node Type . . . . . . . . . . . . : Hybrid
> >>> IP Routing Enabled. . . . . . . . : No
> >>> WINS Proxy Enabled. . . . . . . . : No
> >>> DNS Suffix Search List. . . . . . : domain.local
> >>> Ethernet adapter Local Area Connection:
> >>> Connection-specific DNS Suffix . :
> >>> Description . . . . . . . . . . . : HP NC326i PCIe Dual Port
> >>> Gigabit
> >>> Server Adapter
> >>> Physical Address. . . . . . . . . : 00-21-5A-FF-AE-B4
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 192.168.3.7
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . : 192.168.3.1
> >>> DNS Servers . . . . . . . . . . . : 127.0.0.1
> >>> 192.168.3.5
> >>> Primary WINS Server . . . . . . . : 192.168.3.5
> >>> IPConfig of the server that's fine:
> >>> Windows IP Configuration
> >>> Host Name . . . . . . . . . . . . : krslant1
> >>> Primary Dns Suffix . . . . . . . : domain.local
> >>> Node Type . . . . . . . . . . . . : Hybrid
> >>> IP Routing Enabled. . . . . . . . : No
> >>> WINS Proxy Enabled. . . . . . . . : No
> >>> DNS Suffix Search List. . . . . . : domain.local
> >>> Ethernet adapter Local Area Connection 2:
> >>> Connection-specific DNS Suffix . :
> >>> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
> >>> Adapter (10/100) #2
> >>> Physical Address. . . . . . . . . : 00-07-E9-F6-8C-D7
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 192.168.3.5
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . : 192.168.3.1
> >>> DNS Servers . . . . . . . . . . . : 127.0.0.1
> >>> 192.168.3.7
> >>> "Meinolf Weber" wrote:
> >>>> Hello Gaven,
> >>>>
> >>>> Please post an unedited ipconfig /all from both servers so that we
> >>>> can exclude DNS as a problem. Since Windows 2000 there is no longer
> >>>> the PDC/BDC concept. All DC's are the same and can host the 5 FSMO
> >>>> roles according to some rules.
> >>>>
> >>>> Best regards
> >>>>
> >>>> Meinolf Weber
> >>>> Disclaimer: This posting is provided "AS IS" with no warranties,
> >>>> and
> >>>> confers
> >>>> no rights.
> >>>> ** Please do NOT email, only reply to Newsgroups
> >>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>>>> Here is the situation.
> >>>>>
> >>>>> The network had 2 servers and 15 workstations. Both servers
> >>>>> running
> >>>>> Server 2003 (x86) and the domain is very fresh and clean. The
> >>>>> computers are brand new Dell OptiPlex workstations running XP Pro.
> >>>>> The PDC is a server I built several years ago. Intel 845 (I
> >>>>> think)
> >>>>> server board, 2 GB ECC RAM, RAID 1 SATA storage. In addition to
> >>>>> being
> >>>>> the PDC is also hosts files, printers, DNS, DHCP and WINS. That
> >>>>> server has no problems as all. The problem is with the other
> >>>>> server
> >>>>> which is also a domain controller except it is running Juris (SQL
> >>>>> Express 2005 with an IIS front end) Backup Exec 12 and Lotus
> >>>>> Domino
> >>>>> Server R5.0.11. Originally that was all running on a Dell SC1500
> >>>>> (a
> >>>>> P3 server) which is where the problem started. The problem is
> >>>>> simple;
> >>>>> the server stops communicating with the network. According to the
> >>>>> server and the switch, it is connected. However, it will not
> >>>>> accept
> >>>>> any incoming connections, make any outgoing connections, or even
> >>>>> respond to a ping. When the server experiences this problem, it's
> >>>>> not
> >>>>> specific to certain computers or all computers. It is typically
> >>>>> only
> >>>>> about half that can't talk to the server and again, it's not
> >>>>> consistent. Assuming it was because the server was so old, I
> >>>>> recently
> >>>>> upgraded the server to an HP ML310 G5. I have transferred Backup
> >>>>> Exec
> >>>>> and Lotus Domino to the new server and the problem is already
> >>>>> starting
> >>>>> to appear again - although not as bad yet. I think it may have
> >>>>> something to do with SQL Express 2005 because the new server
> >>>>> showed
> >>>>> no
> >>>>> signs of the problem until that install. However, since I have
> >>>>> not
> >>>>> moved Juris yet, all SQL is doing right now is holding the Backup
> >>>>> Exec
> >>>>> database.
> >>>>> I'm pretty confident it's not hardware. When the problem started,
> >>>>> they were using a very old Cisco Catalysis switch; they now have a
> >>>>> 24 port managed Linksys switch with 4 Gigabit ports for the
> >>>>> servers.
> >>>>> Their firewall/NAT router is a Cisco ASA 5505. The building
> >>>>> wiring
> >>>>> is CAT5 (some CAT5e) and the server patch cables are CAT6 -
> >>>>> recently
> >>>>> replaced.
> >>>>> Has anybody ever seen anything like this in the past? Again, I'm
> >>>>> pretty sure this is something that's being causes by SQL Express
> >>>>> 2005 but I've not been able to figure it out for over 6 months now
> >>>>> and I just don't know what else to look at. I'm pretty sure the
> >>>>> problems started when I installed SQL SP2 on the old server.
> >>>>>
> >>>>> Thanks in advance for any input.
> >>>>>
> >>>>> FYI: I have tried ping/trace tests from the switch itself and the
> >>>>> traffic still dies at the server.
> >>>>>
>
>
>