im running 2k and 2k3 servers at work. they synch with eachother just fine and the dns is working fine on both but the 2k3 server doesnt show up in network neighborhood and win me and 98 clients cant connect to it. any ideas? wins and dns were tested and are fine. the other server is the master browser and its working....
Sometimes I think I'd be better off dead. No, wait, not me, you.
You should just be able to type in your domain name with your 98 computer and it'll search out the domain.. granted you have the right clients and protocols installed.
You are trying to run a domain?
If you don't have a domain.. make sure you have user accounts set up on the server and workstation, then use the UNC from the run command to connect to the server's share.
2K3 has a lot more security in place. Win98/me weren't really designed to work on domains.
You might want to disable the 2k3 firewall to see if that helps out. 98 doesn't have the security to authenticate against 2k3 which is probably causing your problem. You can probably see the 98 machine from your server though.
best bet is to check your configuration of your protocals. sounds to me like the 98/me machines might not be seeing the 2k3 server due to a different configuration.
if i remember correctly, ME and 98's TCP/IP protocal does NOT come with NETBIOS over IP on by default. and win2k3 comes by default with TCP/IP as it's main networking protocal with netbios ON. the 2k server probably has TCP/IP with netbios on as well as Netbuei. and the Clients with 98 / ME have netbuei on. this would allow the 98 / ME machines to see the 2K server through Netbuei but not see the 2k3 machien through.
Netbuei is not the most desired protocol because it requires the machines to constantly broadcast over the network. My recommendation is to remove NetBuei from every server / Computer and use TCP/IP with NetBIOS activated
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.