I've seen this before. While I don't have a specific answer, I believe it's
an issue with the specific hardware your using. In other words ask the
manufacturer of the network interface or just plug them into a hub.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
<(E-Mail Removed)> wrote:
> Hello
> I have set up three machines (IBM xseries 345) running
> server 2003 which will be used for a firewall, application
> server and DB server. I configured the machines with two
> nics on the firewall (one onborad and a netxtreme 1000t),
> two on the application ser (one onboard and a netxtreme),
> and one on the db server (onboard). The firewall and
> application server are connected with a xover cable and
> the app ser uses the firewall as a default gateway. The
> second nic on the app ser is connected to the db ser with
> a xover cable. The db uses the second NICs IP as a
> default gateway.
>
> Ping sequence/direction:
>
> good bad
> -> ->
> fire app|app db
> <- <-
> good good
>
> so the db can talk to the app, but the db can't talk to
> the db. The firewall and the app are good.
>
> If you throw all these machines on one switch then they
> communicate nicely. But why don't they communicate with
> xover cables? Is there a problem with server 2003 dealing
> with two nics? Firewall/antivirus software is not running
> on any machine.
>
> Any suggestions?
>
> Nick
|