Nope. \\server\c$ works just fine. We have disabled NetBIOS over TCP/IP with zero problems. Windows 2003 domain Exchange 2003 Enterprise + Standard OWA Blackberry Enterprise Server YMMV
________________________________ From: David Lum [mailto:[email protected]] Sent: Tuesday, May 05, 2009 9:26 AM To: NT System Admin Issues Subject: RE: Disabling NETBIOS Wouldn't \\machinename\c$ have to be \\FQDN\c$ to work if there is no NetBIOS? For me MACHINENAME = NetBIOS name, so perhaps my thinking is just wrong? (wouldn't be the first time...). "I'm not convinced that Microsoft has completely eliminated NetBIOS dependencies from their own stuff, let alone what third-party software houses do" +1 David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Monday, May 04, 2009 7:17 PM To: NT System Admin Issues Subject: Re: Disabling NETBIOS On Mon, May 4, 2009 at 6:35 PM, Jeremy Anderson <[email protected]> wrote: > I have investigated this a bit, and I just wondered if anyone had any > opinions they would like to share. Short version: Lots of things depend on NetBIOS. That including lots of things from Microsoft. Most notably, Exchange Server 2003 and earlier. You can disable NetBIOS if you don't use any of those things, but myself, I'm not convinced that Microsoft has completely eliminated NetBIOS dependencies from their own stuff, let alone what third-party software houses do. > I have no legacy clients (but a lot of Mac's and Linux Machines) server itself. > Currently I connect \\machinename\c$, will that change? That should still work the same. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
