The few times I worked with the smb server that came with VMWare, I was not impressed. I dont know what they did to it, but I would recommend not using it, and instead using a real samba install. It seems to work better. Jay -----Original Message----- From: tclug-list-admin at mn-linux.org [mailto:tclug-list-admin at mn-linux.org]On Behalf Of Amy Tanner Sent: Tuesday, July 17, 2001 2:57 PM To: tclug-list at mn-linux.org Subject: [TCLUG] vmware's samba server - woes Any of you used the samba server provided with vmware 2.0? i'm trying to get it setup. my linux box can see the shares but the vmware/win2k box can't. the vmnet address vmware assigned to the samba server is 192.168.50.1 [root at coug smb]# smbclient -L 192.168.50.1 added interface ip=192.168.25.37 bcast=192.168.25.255 nmask=255.255.255.0 added interface ip=192.168.50.1 bcast=192.168.50.255 nmask=255.255.255.0 Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.0.6] Sharename Type Comment --------- ---- ------- HostFS Disk VMware host filesystem public Disk Public IPC$ IPC IPC Service (VMware host) atebbe Disk Home directories Server Comment --------- ------- COUG VMware host Workgroup Master --------- ------- WORKGROUP COUG but from windows box i try this from dos: net view \\192.168.50.1 ...and i get System Error 53 occurred. The network path not found. I've been going through the test steps in the samba diagnosis.txt file... Any ideas? -- Amy Tanner amy at real-time.com _______________________________________________ tclug-list mailing list tclug-list at mn-linux.org https://mailman.mn-linux.org/mailman/listinfo/tclug-list