ITHelper80
asked on
Windows 95 cannot access network share on 2003 server
I have just installed 2003 server as our FS, everything is working fine expcept I have three Win 95 (I know...I know) that cannot access any shares on the 2003 box. They are however able to access shares on the resst of my 2000 boxes. I have a 2000 domain and the machines can logon to the domain. WINS and DNS is set on both the server and client. Any suggestions?
ASKER
Thanks for the comments. I tried both but still no go. I can ping the server by DNS, however I cannot browse it by DNS or IP.
Hi,
Don't know if this is applicatble to you but I recently switched my domain from NT PDC to 2003 and I know for that reason that Win95 cannot interact with Windows 2003 as there is now backward compatibility. But if you use wins and LMHOSTS you should at least be able to access the Win 95 workstation from another pc. But to my knowledge you wont be able to access the 2K3 from the 95 Workstation.
http://support.microsoft.com/kb/555038/en-us
This explains how to resolve this.
Regards,
Johan
Don't know if this is applicatble to you but I recently switched my domain from NT PDC to 2003 and I know for that reason that Win95 cannot interact with Windows 2003 as there is now backward compatibility. But if you use wins and LMHOSTS you should at least be able to access the Win 95 workstation from another pc. But to my knowledge you wont be able to access the 2K3 from the 95 Workstation.
http://support.microsoft.com/kb/555038/en-us
This explains how to resolve this.
Regards,
Johan
There are also some server name length limitations for 9x, try ensure network names are 15 characters or less
if you are not worried about the security of those folders
you can set the security permissions to allow 'Everyone' and 'Guest'
with full or whatever access levels you like
you can set the security permissions to allow 'Everyone' and 'Guest'
with full or whatever access levels you like
do you have a workgroup set up & does the 95 box have it configured in it's network neighborhood?
run winipcfg & make sure it is getting all network info correctly, like ip addr, dns, wins, dhcp, etc.
when you create a share on an nt box you have to set share permissions for any domain userid using win9x, they can't be authenticated on the 2k3 svr from a non-nt-based o/s.
run winipcfg & make sure it is getting all network info correctly, like ip addr, dns, wins, dhcp, etc.
when you create a share on an nt box you have to set share permissions for any domain userid using win9x, they can't be authenticated on the 2k3 svr from a non-nt-based o/s.
ASKER
The 95 machines are on a domain and they can login successfully. The share is only three letters so thats not an issue, I checked the permissions and the everyone group has full control for the shares in question. Any other ideas?
ASKER
I figured the problem out. The WINS server had the wrong IP address for our FS. Thanks for the help though!
Hi,
I am happy that you were able to resolve the problem sorry that I could not be of more assistance. Projects keeping me busy :-)
Regards,
Johan
I am happy that you were able to resolve the problem sorry that I could not be of more assistance. Projects keeping me busy :-)
Regards,
Johan
give yourself the points!! hehe
hey ithelper, since you resolved this, you can request a refund in community support.
the customer solved it on 5/10, so i posted the link from EE help on Closing
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1. make sure you are using a name and password that exists on the 2003 Box.
2. make sure you have appropriate IP addresses, and can ping the 2003 box.
Probably #1,
Good Luck,