Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

Cannot See Shared Folders

Installed a new computer using the same "connectcomputer" procedure that I used on existing computers.  However, on the new computer, I don't see any shared folders or the network server in My Network Places.  The other computers are fine.  Also, I ran an IPCONFIG on the new computer and the configuration info is consistent with the other computers.

MichaelDJ
0
MichaelDJ2000
Asked:
MichaelDJ2000
  • 5
  • 4
  • 2
  • +1
3 Solutions
 
MichaelDJ2000Author Commented:
Note the following:
1) I can successfully ping the server from the new computer.
2) The new client is assigned the same permission template as existing clients (who can see shared folders)

MichaelDJ
0
 
Olaf De CeusterCommented:
Hi Michael,

Please check in the TCP/IP properties if the primary DNS is your Server IP address. If not change it and restart the machine.
Under explorer can you search for your server (under computers). If yes you can open the server and map drives from here to suit.
Also make sure your network card has the latest drivers and your cabling is OK.
You could also: (probably the best) after upgrading your network drivers: Rejoin a workgroup, delete the computer in question from the server (You might have to this in AD users and computers) create a new computer account with the wizard on the server console.
After restarting the workstation run the connectcomputer wizard again.
If this does not work: Please post an IPconfig/all of the workstation and server.
Good luck.
OlafDC

0
 
MichaelDJ2000Author Commented:
IPconfig info follows:

NETWORK-SERVER  IPconfig info:
Ethernet Adapter LAN:  
DHCP Enabled: No
IP Address:   192.168.1.2
Subnet Mask: 255.255.255.0
Default Gateway: blank
DNS Servers:   192.168.1.2
Primary WINS Server:   192.168.1.2

WORKSTATION IPconfig info:
IP Routing Enabled: No
WINS Proxy Enabled: No
Ethernet Adapter LAN:  
DHCP Enabled: Yes
Autoconfiguration Enable: Yes
IP Address:   192.168.1.46
Subnet Mask: 255.255.255.0
Default Gateway:   192.168.1.2
DHCP Server:   192.168.1.2
DNS Server:   192.168.1.2
Primary WINS Server: :   192.168.1.2
NetBIOS over Tcpip: Disabled
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
MichaelDJ2000Author Commented:
Also, I can successfully ping from the workstation using the network-server name as well as the IP
address.  Does this help narrow it down?

MichaelDJ
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
MichaelDJ,

NetBIOS over TCP/IP should not be disabled on the workstation.  But I'm wondering, since you didn't post a complete IPCONFIG /ALL from your server do you have a second NIC on the server?

Can you please post the complete IPCONFIG /ALL?  (To do this, open a command prompt and enter IPCONFIG /ALL.  Then, right click on the title bar of that window to access edit > select all, then hit the ENTER key to copy.  Then, place your cursor in the Add Comment window for EE, and use CTRL-V to paste.

Jeff
TechSoEasy
0
 
MichaelDJ2000Author Commented:
IPconfig/all for Network Server and the problem Workstation:

Windows IP Configuration

Host Name:  NETWORK-SERVER
Primary Dns Suffix:  godoersenterpriseinc.local
Node Type: Unknown
IP Routing Enabled: Yes
WINS Proxy Enabled: Yes
DNS Suffix Search List:  godoersenterpriseinc.local

Ethernet Adapter WAN:

Connection-specific DNS Suffix:
DHCP Enabled: No
IP Address:   68.163.73.228
Subnet Mask: 255.255.255.0
Default Gateway: 68.163.73.1
DNS Servers:   192.168.1.2
NetBIOS over Tcpip: Disabled

Ethernet Adapter LAN:

Connect ion-specific DNS Suffix:
DHCP Enabled: No
IP Address:   192.168.1.2
Subnet Mask: 255.255.255.0
Default Gateway:
DNS Servers:   192.168.1.2
Primary WINS Server:   192.168.1.2

Windows IP Configuration

Host Name:  Verification
Primary Dns Suffix:  godoersenterpriseinc.local
Node Type: Broadcast
IP Routing Enabled: No
WINS Proxy Enabled: No
DNS Suffix Search List:  godoersenterpriseinc.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix: godoersenterpriseinc.local
DHCP Enabled: Yes
Autoconfiguration Enable: Yes
IP Address:   192.168.1.46
Subnet Mask: 255.255.255.0
Default Gateway:   192.168.1.2
DHCP Server:   192.168.1.2
DNS Servers:   192.168.1.2
Primary WINS Server: 192.168.1.2
NetBIOS over Tcpip: Disabled
0
 
Olaf De CeusterCommented:
Hi Michael,

From the problem workstation: Open command prompt and type: nslookup yourservername and press enter.
Do you get the server IP address?
OlafDC
0
 
Hypercat (Deb)Commented:
You need to enable NetBIOS over TCP/IP on the workstation and on the internal NIC of the server. This is why network browsing is not working at this point.  This should be done also on all of the other workstations (if not already done) if you want them to be able to browse using Network Places.  If they are just using mapped drives, they should be OK.

Hope this helps!
0
 
Olaf De CeusterCommented:
Ignore the nslookup. You've answered that already by being able to ping the servername
Can you as Jeff suggest: Enable Netbios over TCP on the workstation. Control panel, network connections, right click on your lan card, left click properties, under general tab: double click on TCp/IP, click on advanced, go to the Wins tab, tick enable betbios over Tcp, click OK 3 times.
OlafDC
0
 
MichaelDJ2000Author Commented:
My understanding was that Netbios needed to be enabled for older OSs, but that it did not have to be enabled for Windows Server 2003. By enabling Netbios on the Server and Workstations, I won't trigger any other 'problems'?  (obviously, i'm a novice at this)
0
 
Olaf De CeusterCommented:
If you have WINS running (You have) you should have it running. It certainly can't do any harm.
OlafDC
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Internally, there are still things which use both NETBIOS and WINS.  (Exchange, for instance).  This is why you have it enabled everywhere except on your WAN NIC where it should be disabled.

Jeff
TechSoEasy
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now