I have a simple setup.
There is one (and only one) Win2k Advanced Server w/ SP3.
NetBIOS over TCP/IP is enabled.
There is only one NIC, and the whole network is on one Class-C subnet, no routers or anything fancy.
The Win2k Advanced Server is running as the only Active Directory server.
The Pre-AD Domain name is dsb-home, which is different from the AD name.
It is running as the only DNS, DHCP & WINS server.
WINS & DNS seems to have a complete list of every computer. DNS gets dynamicly updated from DHCP.
When I try to browse the domain (Using the My Network Places), I get an error message:
Microsoft Windows Network
\ / dsb-home is not accessible
X The account is not authorized to log in from this station
/ <OK>
I am logged in in as administrator.
There is a mix of Win98, Win2k Professional & snapservers. It seems the Win98 & Win2k workstations have no problems at all - they get a complete list of windows computers.
I think this is causing a problem I am having trying to backup the snapserver.
There is one (and only one) Win2k Advanced Server w/ SP3.
NetBIOS over TCP/IP is enabled.
There is only one NIC, and the whole network is on one Class-C subnet, no routers or anything fancy.
The Win2k Advanced Server is running as the only Active Directory server.
The Pre-AD Domain name is dsb-home, which is different from the AD name.
It is running as the only DNS, DHCP & WINS server.
WINS & DNS seems to have a complete list of every computer. DNS gets dynamicly updated from DHCP.
When I try to browse the domain (Using the My Network Places), I get an error message:
Microsoft Windows Network
\ / dsb-home is not accessible
X The account is not authorized to log in from this station
/ <OK>
I am logged in in as administrator.
There is a mix of Win98, Win2k Professional & snapservers. It seems the Win98 & Win2k workstations have no problems at all - they get a complete list of windows computers.
I think this is causing a problem I am having trying to backup the snapserver.