Guest Ned Posted December 12, 2007 Posted December 12, 2007 I wasn't sure wher to post this, if it needs to go somewhere else, I apologize. I am running sbs 2003 SP2, I am setting up 4 dell vostro 200 workstations. I have successfully setup 3 of the 4. The 4th workstation does not allow me to map a network drive to the server. In fact when I look at the network using explore I can see all the computers on the network, but I cannot see the server. I can see the server and from the other 3 workstations. Any help is appreciated, Thanks
Guest Olaf Engelke [MVP Windows Server] Posted December 12, 2007 Posted December 12, 2007 Re: Connecting Client to Server Hello Ned, "Ned" <Ned@discussions.microsoft.com> wrote in message news:DA0162CD-A3C3-486A-980E-1A1DE3833B4E@microsoft.com... >I wasn't sure wher to post this, if it needs to go somewhere else, I >apologize. > > I am running sbs 2003 SP2, > > I am setting up 4 dell vostro 200 workstations. I have successfully setup > 3 > of the 4. The 4th workstation does not allow me to map a network drive to > the > server. In fact when I look at the network using explore I can see all the > computers on the network, but I cannot see the server. I can see the > server > and from the other 3 workstations. Any help is appreciated, > Network environment is not the most reliable thing, especially if you do not use a WINS server. All PCs already member of the domain? Could the failing machine have a bug in the TCP/IP configuration (typo in some place, wrong subnet mask, DNS server pointing to the wrong system). (What shows ipconfig /all on the client and on the server?) Can you ping the server by name and/or by IP address? What happens, if you click Start/Run and enter \\Servername\Sharename for the network drive you wish to share? Best greetings from Germany Olaf
Guest Ned Posted December 12, 2007 Posted December 12, 2007 Re: Connecting Client to Server Thanks for the quick reply, Start/Run and enter \\Servername\Sharename for the network drive allows me to see the drive. Interesting, I mapped the drive that I needed. If I expand the network I still don't see the server.... Any suggestions on how to get it to show up? Ned "Olaf Engelke [MVP Windows Server]" wrote: > Hello Ned, > "Ned" <Ned@discussions.microsoft.com> wrote in message > news:DA0162CD-A3C3-486A-980E-1A1DE3833B4E@microsoft.com... > >I wasn't sure wher to post this, if it needs to go somewhere else, I > >apologize. > > > > I am running sbs 2003 SP2, > > > > I am setting up 4 dell vostro 200 workstations. I have successfully setup > > 3 > > of the 4. The 4th workstation does not allow me to map a network drive to > > the > > server. In fact when I look at the network using explore I can see all the > > computers on the network, but I cannot see the server. I can see the > > server > > and from the other 3 workstations. Any help is appreciated, > > > Network environment is not the most reliable thing, especially if you do not > use a WINS server. > All PCs already member of the domain? > Could the failing machine have a bug in the TCP/IP configuration (typo in > some place, wrong subnet mask, DNS server pointing to the wrong system). > (What shows ipconfig /all on the client and on the server?) > Can you ping the server by name and/or by IP address? > What happens, if you click Start/Run and enter \\Servername\Sharename for > the network drive you wish to share? > Best greetings from Germany > Olaf > >
Guest Olaf Engelke [MVP Windows Server] Posted December 12, 2007 Posted December 12, 2007 Re: Connecting Client to Server Hi Ned, "Ned" <Ned@discussions.microsoft.com> schrieb im Newsbeitrag news:424230DE-0C23-46CE-A8C3-BFF4EBD0F533@microsoft.com... > Thanks for the quick reply, > > Start/Run and enter \\Servername\Sharename for the network drive allows me > to see the drive. Interesting, I mapped the drive that I needed. If I > expand > the network I still don't see the server.... Any suggestions on how to get > it > to show up? > as already said, the only reliable way is to configure WINS server on the server and have all machines including the server itself point to it in the TCP/IP properties. Usually the usage of network neighbourhood is not necessary with constant mapped drives/printers. Best greetings from Germany Olaf
Recommended Posts