|
tech
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
RE: Not able to log into Win2K serversuggestion did the trick. I also tried to name the workgroup the same as the pre-dot name of the domain to no avail. I appreciate your assistance. Have a great day. Show quote "Desmond Lee" wrote: > NT rely on WINS to resolve NetBIOS names whereas Win 200x use DNS. > Also, TCP/IP forwarding is by default disabled in Win 2000. > See > http://support.microsoft.com/default.aspx?scid=kb;en-us;230082 > > > If you do not have WINS on the networks, consider putting the Win 200x > server-IP in the %systemroot%\system32\drivers\etc\lmhosts file on the NT > machines. > > Do let us know if this helps. > > Thanks! > > > "Craig S" wrote: > > > I have a multihomed Win2K server. > > > > NIC1 to corporate WAN - this side OK > > NIC2 to small isolated LAN - this side PROBLEMS > > > > Each NIC bound to a different subnet/IP addressing scheme. > > > > The Win2K server is a member of the corporate domain. > > > > The NT4 workstations are members of a Workgroup named "Workgroup." They can > > ping the Win2K server. They cannot see the server when browsing the network > > and cannot log into the server. Drives cannot be mapped by server name or IP > > address. > > > > I need to enable the NT4 workstations to see and log into the Win2K server. > > > > Any suggestions? > > > > Thank you! |
|||||||||||||||||||||||