How about just making a redundant TCP/IP solution? Perhaps have 2 DNS
servers?

Protocols don't fail, servers that transmit and resolve fail.

This is the equivilant to saying we have a drinking water drought because it
isn't raining. It is not the drinking water that is failing it is the
weather. Now you want to replace the drinking water with sewer water
(netbeui).

Or course you can't control the weather in this scenario but you can control
the point of failure in your scenario. That is where I would focus.

-----Original Message-----
From: Morgan, Joshua [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, July 18, 2002 10:45 AM
To: NT 2000 Discussions
Subject: Sort of OT: other Protocols

I have an Isolated environment that runs SQL 2000 and Windows 2000 Servers.
This environment experienced problems the other day because of a lack of
name resolution between the Servers.
I was asked by management to look at netbeui as a backup incase standard
TCPIP name Resolution failed...
Here is what I have set up...
On each machine I have 2 Nic's, 1 nic on each machine is dedicated to IP and
1 Nic is dedicated to NetBeui.

Does anyone see any issues with this?







Joshua Morgan
PROFITLAB
Senior Network Engineer
PH: (864) 250-1350 Ext 133
Fax: (413) 581-4936
[EMAIL PROTECTED]
http://www.profit-lab.com
http://ncontrol.info

The greatest glory is not in never failing, but in rising up every time we
fall.
-- Confucius 


------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to %%email.unsub%%

------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to