One way network discovery(Server08R2)

korsen · 03-08-2010, 01:03 PM

Ok, referring to the current setup which was resolved here: http://forum.whatismyip.com/f8/serve...ng-probs-t826/

I was able to enable and start the proper services to have the "Turn Network Discovery On" remain in the On position. Before I was able to, the network was capable of discovering the laptop on the internal network once I shared it.

Having my own file or drive shared to everyone before and after enabling the network discovery on the server, in neither case can the laptop see my server or it's file. Clearly I don't want to set public sharing because we all know it's better to be able to set permissions on user access.

In the past, I was able to simply set the drive as shared and it would appear, but also in the past, I didn't have this setup referred to in the post above. So all the associated options under the network management are set, and as a server role, the only service installed under File Services is the File Server - the rest are not installed. Checking the descriptions of the rest of them tell me they're not necessary. Link Layer is enabled under all network adapters, discovery and sharing are set under network management on both computers, and from the server->laptop I have no problem sending or receiving files.

From the laptop, opening any folder and putting in \\Tower does nothing. Putting it into a web browser can't find the file (duh) and I noticed the laptop is under WORKGROUP, even though under the network connections it states it's connected to the Tower.FEnd network. I wonder if under the My Computer properties changing it from a workgroup WORKGROUP to my domain will allow it access. I'll have to check that when the laptop isn't busy doing something more important. This thread might become moot under that one change :P But as it stands, I've done everything I can think of and have prayed to google to deliver me from the heathen packet headers :P Nothing. I'll update the post after I change the laptop from workgroup to domain (if that's possible from my setup, I can't remember off the top of my head.)

wimiadmin · 03-08-2010, 01:30 PM

Depending on the version of OS you're running on the laptop will determine if you can join a domain or not.

Even though a computer (your laptop in this case) isn't part of a domain, if it's connected to the same network, it will be able to access shared folders from other computers.....but will be prompted for a network username/pass before given access.

From the laptop, can you ping the IP that your tower is on? If you can ping the IP but not the name then try \\192.168.x.x instead of \\Tower

Computers can be in different workgroups on the same network as well and still share resources it just takes a few more clicks to find them in the My Computer window.

AboveTheLogic · 03-08-2010, 02:57 PM

I think the WORKGROUP discovery stuff relies on WINS, but I'm not sure.

Do you have WINS setup?

I assume that these machines can all ping each other by IP address...

korsen · 03-08-2010, 05:24 PM

The computers can ping each other fine, and AFAIK I do NOT have WINS installed on my server. The laptop is using Vista btw. I'll try accessing via IP and report back.

EDIT: Accessing via \\IP doesn't work, nor generate an error.

AboveTheLogic · 03-08-2010, 11:34 PM

hmm

do you have matching username/passwords on the two machines?

0siris · 03-09-2010, 09:42 AM

I don't see any specific share names mentioned. I think that's significant. A Windows Server, if *all* you do is turn on file sharing, is going to only have "administrative" shares. Administrative shares are hidden from plain "Network Neighborhood" browsing. So, at best, you'd get a blank display.

korsen, Have you actually setup a folder share?

Also, as has already been mentioned, a Windows workgroup doesn't have a central user database. It's individual to each computer. So you either need to use a username on the server machine (Tower, in your example), or make sure you're using an identical username (and password) on both the workstation and the server.

0siris · 03-09-2010, 09:47 AM

Quote:

Originally Posted by AboveTheLogic

I think the WORKGROUP discovery stuff relies on WINS, but I'm not sure.

Do you have WINS setup?

I assume that these machines can all ping each other by IP address...

NetBIOS, yes. WINS, not necessarily. Starting with (I think) Windows 2000, Windows networking included NetBIOS over TCP/IP, and...

korsen, I just thought of something. Wasn't your setup to try and get an Active Directory domain going? If you got that working, and something is showing a workgroup, not the domain, then that explains the inability to reach the shares. Make sure that all computers are joined to the domain. The computers have to login to the domain just like the people do. Either one not so, and domain browsing will be denied.

korsen · 03-09-2010, 11:38 AM

I recently found a forum post on the net where someone clicked on "What is network discovery?" (which can be found as a help link in the advanced network settings) and there might have been a single service that was disabled that I hadn't seen mentioned. After going back and enabling the services it automatically turned on, and I'll have to look at it when I get home but there might've been an extra service I enabled which allowed me to actually browse my cousin's computer via Hamachi VPN. I haven't had a chance to try accessing my server via the internal network but I have a few things to try.

Yes, I do have a share folder setup already. So for the moment, I can browse other computers, but I haven't tested enough things to see if I can browse my own from another person's computer. The password/usernames are not the same - they weren't in the past when it worked previously and I don't intend to set them that way now.

I'll update this post in approx 3-4 hrs once I get home. Currently in school.

03-08-2010, 01:03 PM	#1
korsen Junior Member Join Date: Feb 2010 Posts: 13	One way network discovery(Server08R2) Ok, referring to the current setup which was resolved here: http://forum.whatismyip.com/f8/serve...ng-probs-t826/ I was able to enable and start the proper services to have the "Turn Network Discovery On" remain in the On position. Before I was able to, the network was capable of discovering the laptop on the internal network once I shared it. Having my own file or drive shared to everyone before and after enabling the network discovery on the server, in neither case can the laptop see my server or it's file. Clearly I don't want to set public sharing because we all know it's better to be able to set permissions on user access. In the past, I was able to simply set the drive as shared and it would appear, but also in the past, I didn't have this setup referred to in the post above. So all the associated options under the network management are set, and as a server role, the only service installed under File Services is the File Server - the rest are not installed. Checking the descriptions of the rest of them tell me they're not necessary. Link Layer is enabled under all network adapters, discovery and sharing are set under network management on both computers, and from the server->laptop I have no problem sending or receiving files. From the laptop, opening any folder and putting in \\Tower does nothing. Putting it into a web browser can't find the file (duh) and I noticed the laptop is under WORKGROUP, even though under the network connections it states it's connected to the Tower.FEnd network. I wonder if under the My Computer properties changing it from a workgroup WORKGROUP to my domain will allow it access. I'll have to check that when the laptop isn't busy doing something more important. This thread might become moot under that one change :P But as it stands, I've done everything I can think of and have prayed to google to deliver me from the heathen packet headers :P Nothing. I'll update the post after I change the laptop from workgroup to domain (if that's possible from my setup, I can't remember off the top of my head.)

03-08-2010, 01:30 PM	#2
wimiadmin Administrator Join Date: May 2008 Location: Pigeon Forge, TN Posts: 858	Depending on the version of OS you're running on the laptop will determine if you can join a domain or not. Even though a computer (your laptop in this case) isn't part of a domain, if it's connected to the same network, it will be able to access shared folders from other computers.....but will be prompted for a network username/pass before given access. From the laptop, can you ping the IP that your tower is on? If you can ping the IP but not the name then try \\192.168.x.x instead of \\Tower Computers can be in different workgroups on the same network as well and still share resources it just takes a few more clicks to find them in the My Computer window. __________________ Brian Please Search Before Posting

03-08-2010, 02:57 PM	#3
AboveTheLogic Super Moderator Join Date: Jul 2008 Location: Los Angeles Posts: 475	I think the WORKGROUP discovery stuff relies on WINS, but I'm not sure. Do you have WINS setup? I assume that these machines can all ping each other by IP address... __________________ Internet IP vs. Local IP Port Forwarding

03-08-2010, 05:24 PM	#4
korsen Junior Member Join Date: Feb 2010 Posts: 13	The computers can ping each other fine, and AFAIK I do NOT have WINS installed on my server. The laptop is using Vista btw. I'll try accessing via IP and report back. EDIT: Accessing via \\IP doesn't work, nor generate an error. Last edited by korsen; 03-08-2010 at 05:37 PM.

03-08-2010, 11:34 PM	#5
AboveTheLogic Super Moderator Join Date: Jul 2008 Location: Los Angeles Posts: 475	hmm do you have matching username/passwords on the two machines? __________________ Internet IP vs. Local IP Port Forwarding

03-09-2010, 09:42 AM	#6
0siris Super Moderator Join Date: Nov 2009 Location: IL, USA Posts: 156	I don't see any specific share names mentioned. I think that's significant. A Windows Server, if all you do is turn on file sharing, is going to only have "administrative" shares. Administrative shares are hidden from plain "Network Neighborhood" browsing. So, at best, you'd get a blank display. korsen, Have you actually setup a folder share? Also, as has already been mentioned, a Windows workgroup doesn't have a central user database. It's individual to each computer. So you either need to use a username on the server machine (Tower, in your example), or make sure you're using an identical username (and password) on both the workstation and the server.

03-09-2010, 11:38 AM	#8
korsen Junior Member Join Date: Feb 2010 Posts: 13	I recently found a forum post on the net where someone clicked on "What is network discovery?" (which can be found as a help link in the advanced network settings) and there might have been a single service that was disabled that I hadn't seen mentioned. After going back and enabling the services it automatically turned on, and I'll have to look at it when I get home but there might've been an extra service I enabled which allowed me to actually browse my cousin's computer via Hamachi VPN. I haven't had a chance to try accessing my server via the internal network but I have a few things to try. Yes, I do have a share folder setup already. So for the moment, I can browse other computers, but I haven't tested enough things to see if I can browse my own from another person's computer. The password/usernames are not the same - they weren't in the past when it worked previously and I don't intend to set them that way now. I'll update this post in approx 3-4 hrs once I get home. Currently in school.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode