Dual NICs in Server 2003

[BornStar]

I am running a Windows Server 2003 box with dual NICs. One NIC is connected to a 100Mb hub and the other one is connected to a 1Gb switch. This server operates as our web filter and our backup server so we need to keep the connections the way they are (the web filter uses the connection to the hub and the backup software uses the gigabit connection). The problem I'm running into is multiple times a minute I get an error in the event log that a machine with the same name has been found. I'd like to stop these from happening but I can't seem to come up with a suitable way. Does anyone have any advice on how to fix this?

Thanks.

 

[InlineFive]

Does the machine have two gateways? Is it one machine on two networks or one machine on one network?

 

[BornStar]

It's one machine on one network, unfortunately.

 

[InlineFive]

Originally posted by: BornStar18
It's one machine on one network, unfortunately.

Then why do you need to have it connected twice...

 

[BornStar]

Originally posted by: InlineFive

Originally posted by: BornStar18
It's one machine on one network, unfortunately.

Then why do you need to have it connected twice...

The web filter needs to be connected to the hub so that it sees all traffic that goes out to the Internet. The backup software needs to be placed on the gigabit connection so we don't go over our backup window. In the future I intend to virtualize the web filter but I don't have the time for that right now.

 

[nweaver]

without understanding the web filtering, it's hard to say...

you might be able to unbind some protocols from the 100Mb interface to eliminate this issue, but since I have no clue what this web filtering software does/how it works, that's hard to say. Some, that just listen to the packets, you can unbind all protocols from (including TCP/IP) if it's s "sniffing" type application.

 

[BornStar]

Originally posted by: nweaver
without understanding the web filtering, it's hard to say...

you might be able to unbind some protocols from the 100Mb interface to eliminate this issue, but since I have no clue what this web filtering software does/how it works, that's hard to say. Some, that just listen to the packets, you can unbind all protocols from (including TCP/IP) if it's s "sniffing" type application.

I think you just hit it. I should have paid attention to the fact that the filtering software installs its own protocol. I just unbound TCP/IP from the interface and we'll see if it has any long term effects. Thanks for your help.