Can't access Win 2003 server from Win98 1

[emance]

I recently installed a new windows 2003 server with 2 other existing windows 2000 servers. The new server is now a DC. I moved DNS to the new server along with DHCP and Wins. The workstations are a mix of Win 98 and XP Pro. XP machines are fine but my problem is with the Win98 users(10). 1/2 of the Win98 machines can map a drive to the new server and 1/2 can't. The new server doesn't show up in My Network Places on any of the Win98 machines (the 2 Win2k servers due show). I can ping the server by name and FQDN from the Win98 machnies and can ping all Win98 machines from the server. net view command fails (error 53) from all Win98 machines.

Any ideas?

Thanks in advance,


Eric

 

[markdmac]

Make sure that on the server you have set to Enable NetBIOS over TCP/IP on the WINS tab in the TCP/IP properties.

On the 98 machines, ensure that you have installed the DSCLIENT.

For some enhanced functionality for better integration with Win2K3, I suggest that you also install WSH 5.6 and WMI Core.

Lastly, budget for replacement of these machines. Computers are cheap enough these days to justify the replacement over the cost of keeping these machines running and having to support multiple operating systems.


I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[emance]

OK,

Let me first thank you for your response. As far as the Win98 machines, It was like pulling teeth to convince this company that they needed a new server. They know they need new workstations but want to wait even though it will cost more in the long run.

NetBios over TCP/IP on the server is now enabled.

I installed DSClient last year on all Win98 machines.

I was able to allow 3 more machines to map a drive but the new server still doesn't show up when browsing the network.
While trying to figure this out, I found that they are running NetBeui.

I have two problems, the first group of machines that can map a drive but can't see the new server when browsing Network Neighborhood and the second group that can't map a drive or browse the new server.

On both groups I can ping the server by Netbios name and FQDN name.

On the first group I tried Net View \\(server) and was able to connect.

I disbled NetBeui and was unable to use the net view command (error 53)

With NetBeui disabled, I received the following error while trying to browse the network: Unable to Browse...

I went to Start, Run and tried \\(server) and was able to connect.

On a second group I can't map a drive to the new server and the net use command fails (error 53)

On the second group, in the TCP/IP properties, Netbios tab, the box to allow Netbios over TCP/IP is checked but grayed out.

Please let me know if you need more info.

Thanks,

Eric

 

[emance]

Will the following artical apply to my problem?

Knowlege Base

227120

Eric

 

[ITPangaeaArchitect]

ok check it out

you've got to relax security in 2003 for 98 to work correctly

install teh support tools on your 2003 dc and run gpresult /v >c:\gpresult.txt

paste the results back here and ill tell you what you need to change

either that or paste the contents of the adm itself from sysvol

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there