This section provides a deeper level of instruction for troubleshooting connectivity issues. This section is provided for a company’s helpdesk, or IT department to help diagnose deep connectivity issues.
Issue: Cannot see the session in Sessions Near Me
Step 1:
1. Make sure your colleague has started the session.
2. Try discovering the Session again. If this does not resolve the issue, continue to the next step.
Step 2:
1. Make sure you are connected to the network
2. Try discovering the Session again. If this does not resolve the issue, continue to the next step.
Step 3:
1. Ensure that Windows Firewall is configured correctly. For detailed instructions, see "To ensure that Windows Firewall is configured correctly" below.
2. Try discovering the Session again. If this does not resolve the issue, continue to the next step.
Step 4:
1. Ensure that the computers are on the same subnet. For detailed instructions, see "To confirm the computers are on the same subnet" below. To ensure a user is signed into Windows People Near Me
2. Ensure the computers can "see" each other. For detailed instructions, see "To ensure a user is signed into Windows People Near Me" below.
a. If the computers can see each other and the computers are not on the same subnet, Sessions near me will not work. Try using a file or e-mail invitation instead.
b. If the computers can see each other and the computers are on the same subnet, then multicast might be turned off on your network. Please contact your system administrator.
c. If the computers can’t see each other re-check the firewall (or try turning it off) and try again. If the problem persists, contact your system administrator.
Issue: Cannot see any people near me
Step 1:
1. Ensure both people are signed-in to People Near Me. For detailed instructions, see "To ensure a user is signed into Windows People Near Me" below.
2. Try discovering the people again. If this does not resolve the issue, continue to the next step.
Step 2:
1. Make sure you are connected to the network.
2. Try discovering the people again. If this does not resolve the issue, continue to the next step.
Step 3:
1. Ensure that Windows Firewall is configured correctly. For detailed instructions, see "To ensure that Windows Firewall is configured correctly" below.
2. Try discovering the people again. If this does not resolve the issue, continue to the next step.
Step 4:
1. Ensure that the computers are on the same subnet. For detailed instructions, see "To confirm the computers are on the same subnet" below.
2. Ensure the computers can "see" each other. For detailed instructions, see "To ensure a user is signed into Windows People Near Me" below.
a. If the computers can see each other and the computers are not on the same subnet, Sessions near me will not work. Try using a file or e-mail invitation instead.
b. If the computers can see each other and the computers are on the same subnet, then multicast might be turned off on your network. Please contact your system administrator.
c. If the computers can’t see each other re-check the firewall (or try turning it off) and try again. If the problem persists, contact your system administrator.
Issue: Cannot connect even though I can see the session in Session Near Me
Step 1:
1. Ensure that Windows Firewall is configured correctly. For detailed instructions, see "To ensure that Windows Firewall is configured correctly" below.
2. Try connecting to the Session again. If this does not resolve the issue, continue to the next step.
Step 2:
1. Ensure DFSR is enabled through LUA on your computer. For detailed instructions, see "To confirm Distributed File System Replication (DFSR) is enabled through LUA" below.
2. Try connecting to the Session again. If this does not resolve the issue, continue to the next step.
Step 3:
1. Ensure the PNRP cloud is initialized properly. For detailed instructions, see "To confirm the Peer Name Resolution Protocol (PNRP) cloud is initialized properly" below. If PNRP is configured correctly, then go to the next step. If PNRP is not configured correctly, contact your system administrator.
2. Ensure you can resolve a PNRP name. For detailed instructions, see "To confirm the PNRP can resolve PNRP names" below. If PNRP cannot resolve, contact your system administrator.
Issue: Invitations are not received even though I can see people near me
Step 1:
1. Ensure they have invitations turned on in the configuration. For detailed instructions, see "To confirm an application invitation is correctly configured" below.
2. Try inviting the user again. If this does not work, please continue to the next step.
Step 2:
1. Ensure that Windows Firewall is configured correctly. For detailed instructions, see "To ensure that Windows Firewall is configured correctly" below.
2. Try inviting the user again. If this does not work, please continue to the next step.
Step 3:
Your system administrator may have blocked application invite via Group Policy. Please try joining the session through "Sessions near me" or contact your system administrator.
 Note
If you are still experiencing problems using Windows Meeting Space, you should try rebooting your computer.
Issue: User cannot use file or e-mail-based invitation to join a meeting
Step 1:
1. Ensure that each user has a link-local IPv6 address, and determine whether each user has a global IPv6 address.
2. If the user who is inviting others has a global IPv6 address, and the user who is being invited does not, then the user who is being invited must obtain a global IPv6 address to join the meeting. If the user who is inviting others has only link-local connectivity, and the user who is being invited is not on the same local subnet, then the user who is inviting others must obtain global connectivity and restart the meeting, or the user who is being invited must connect to the same local subnet to join the meeting..
Step 2:
1. Ensure that Windows Firewall is configured correctly. For detailed instructions, see "To ensure that Windows Firewall is configured correctly" below.
2. Try inviting the user again. If this does not work, please continue to the next step.
Procedures for advanced networking troubleshooting
The following procedures provide possible solutions for resolving networking troubleshooting issues.
 To ensure a user is signed into Windows People Near Me
-
1. Click Start, and then click Control Panel.
2. Click Network and Internet.
3. Click People Near Me.
4. Select Sign in to People Near Me, and click OK.
|
To ensure that Windows Firewall is configured correctly
-
1. Click Start, and then click Control Panel.
2. Click Network and Internet.
3. Under Windows Firewall, click Allow a program through Windows Firewall.
4. On the Exceptions tab, click Add program.
5. In the Programs list, select Windows Meeting Space, and then click Browse and navigate to %installdrive%\windows\system32 and select p2phost.exe. Click OK.
6. Make sure the programs you want to allow are selected in Programs and services.
|
The following procedures are to ensure computers can see each other:
To ensure you have a link-local IPv6 address
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type IPConfig and make sure you have an IP address that is similar to fe80::5efe:157.59.138.63%2. A link-local address always begins with fe80.
a. If your IP address is similar, go to the procedure, "To confirm you can ping the IP address of a computer".
b. If your IP address is not similar, ensure that your network device is properly installed and your computer has the most recent drivers installed.
|
To determine whether you have a global IPv6 address
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type IPConfig and make sure you have an IP address that begins with 2001:, 2002:, 2003:, 2400:, 2404:, 2600:, 2604:, 2608:, 260C:, 2610:, 2800:, 2A00:, or 2601:.
a. If your IP address is similar, go to the procedure, "To confirm you can ping the IP address of a computer".
b. If your IP address is not similar, contact your network administrator on how to obtain a global IPv6 address.
|
To confirm you can ping the IP address of a computer
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type ping -6 , such as:
-
ping -6 fe80::5efe:157.59.138.63%2
|
4. If the results are similar to the following, you should attempt to ping the computer again from a different computer. If the results remain the same, then your computers can see each other.
-
C:\Documents and Settings\user>ping -6 fe80::5efe:157.59.138.63%2
Pinging fe80::5efe:157.59.138.63%2 with 32 bytes of data:
Reply from fe80::5efe:157.59.138.63%2: time<1ms
Reply from fe80::5efe:157.59.138.63%2: time<1ms
Reply from fe80::5efe:157.59.138.63%2: time<1ms
Reply from fe80::5efe:157.59.138.63%2: time<1ms
Ping statistics for fe80::5efe:157.59.138.63%2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
|
5. If the results are similar to the following, you should return to the Advanced Troubleshooting section to continue diagnosing your issue.
-
C:\Documents and Settings\user>ping -6 fe80::5efe:157.59.138.52%2
Pinging fe80::5efe:157.59.138.52%2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for fe80::5efe:157.59.138.52%2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
|
|
To confirm the computers are on the same subnet
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type tracert -h 1 -d and then type the IP address with which you want to compare subnets.
4. If the results are the same as you requested, then you are on the same subnet. If the results are not the same, then you are not. See below for an example showing computers are on the same subnet:
-
C:\Documents and Settings\tmanion>tracert -h 1 -d 157.59.138.63
Tracing route to 157.59.138.63 over a maximum of 1 hops
1 <1 ms <1 ms <1 ms 157.59.138.63
Trace complete.
|
a. Example showing computers are on the same subnet:
-
C:\Documents and Settings\tmanion>tracert -h 1 -d 157.54.56.187
Tracing route to 157.54.56.187 over a maximum of 1 hops:
1 <1 ms <1 ms <1 ms 157.59.136.1
Trace complete.
C:\Documents and Settings\tmanion>
|
|
To confirm an application invitation is correctly configured
-
1. Click Start, and then click Control Panel.
2. Click Network and Internet.
3. Click People Near Me.
4. On the Settings tab, confirm that Display a notification when an invitation is received is selected. Click OK.
|
To confirm the Peer Name Resolution Protocol (PNRP) cloud is initialized properly
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type netsh and press Enter.
4. Type p2p and press Enter.
5. Type pnrp and press Enter.
6. Type cloud and press Enter.
7. Type show names and press Enter.
8. The results should be similar to the following. If the state is active for Global_, and the number of cache entries is 45 or greater, then the PNRP is properly initialized.
netsh p2p pnrp cloud>show names
Scope Id Addr State Name
----- ----- ----- ---------------- -----
1 0 3 Active Global_
Synchronize server: PNRPSEEDSERVER.CORP.MICROSOFT.COM;pnrpv2.ipv6.microsoft.
com
Use Server: Used
Use SSDP: Used
Use Persisted cache: No addresses
Cloud Configured Mode: Auto
Cloud Operational Mode: Full Participant
IP Addresses: [2001:4898:0028:0003:1dd6:d474:479a:1289]:3540
[3ffe:8311:ffff:f70f:0000:5efe:9d3b:8856]:3540
Number of cache entries: 45
Estimated cloud size: 0
Number of registered names: 3
Throttled resolves: 0
Throttled solicits: 0
Throttled floods: 0
Throttled repairs: 0
P2P Name: 0.Pnrpauto-2982303958306963458
Identity: 1115c80f3c33aa01c8c25a76562f693f532a499d.PnrpProtocolV2
Comment: PnrpAutoService
PNRP ID: 01f4098de8c77588ac746fc71ba5e9a1.2001489800280003ed93abd8bffc88e
f
State: OK
IP Addresses: 127.0.0.1:80 tcp
P2P Name: 0.214578948
Identity: 1115c80f3c33aa01c8c25a76562f693f532a499d.PnrpProtocolV2
Comment: Local Machine Id
PNRP ID: bcf3ddc0cfb1efb77c8698779e0559da.77006600550044004f0aaf7ee20a41b
9
State: OK
P2P Name: 0.NHTest
Identity: 1115c80f3c33aa01c8c25a76562f693f532a499d.PnrpProtocolV2
Comment: nhortonamd.ntdev.corp.microsoft.com
PNRP ID: 7f82af7b026dc717cbdfd87eaa7a24af.fec000000000f70f8bc779f3a86b1af
9
State: OK
IP Addresses: [fec0:0000:0000:f70f:0000:5efe:9d3b:8856]:8350 udp
[2001:4898:0028:0003:0240:f4ff:febb:312e]:8350 udp
157.59.136.86:8350 tcp
netsh p2p pnrp cloud>show names
Scope Id Addr State Name
----- ----- ----- ---------------- -----
1 0 3 Alone Global_
Synchronize server: PNRPSEEDSERVER.CORP.MICROSOFT.COM;pnrpv2.ipv6.microsoft.
com
Use Server: Used
Use SSDP: No addresses
Use Persisted cache: No addresses
Cloud Configured Mode: Auto
Cloud Operational Mode: Full Participant
IP Addresses: [2001:4898:0028:0003:1dd6:d474:479a:1289]:3540
[3ffe:8311:ffff:f70f:0000:5efe:9d3b:8856]:3540
Number of cache entries: 0
Estimated cloud size: 0
Number of registered names: 2
Throttled resolves: 0
Throttled solicits: 0
Throttled floods: 0
Throttled repairs: 0
P2P Name: 0.Pnrpauto-2982303958306963458
Identity: 1115c80f3c33aa01c8c25a76562f693f532a499d.PnrpProtocolV2
Comment: PnrpAutoService
PNRP ID: 01f4098de8c77588ac746fc71ba5e9a1.2001489800280003ed93abd8bffc88e
f
State: OK
IP Addresses: 127.0.0.1:80 tcp
P2P Name: 0.214578948
Identity: 1115c80f3c33aa01c8c25a76562f693f532a499d.PnrpProtocolV2
Comment: Local Machine Id
PNRP ID: bcf3ddc0cfb1efb77c8698779e0559da.77006600550044004f0aaf7ee20a41b
9
State: OK
|
To confirm the PNRP can resolve PNRP names
-
1. Press the Windows logo key + R.
2. In the Run dialog box, type CMD to open Command Prompt.
3. Type netsh and press Enter.
4. Type p2p and press Enter.
5. Type pnrp and press Enter.
6. Type peer and press Enter.
7. Type add registration 0.testingpnrp and press Enter.
8. If you see OK, then PNRP can resolve PNRP names. If you do not see OK, then PNRP cannot resolve names.
9. On a different computer, press the Windows logo key + R.
10. In the Run dialog box, type CMD to open Command Prompt.
11. Type netsh and press Enter.
12. Type p2p and press Enter.
13. Type pnrp and press Enter.
14. Type peer and press Enter.
15. Type resolve 0.testingpnrp and press Enter.
16. You should see the IP address returned. If the IP address is not returned, then PNRP is not resolving names.
|
To confirm Distributed File System Replication (DFSR) is enabled through LUA
-
1. To provide users access to the WMI DFSR namespace (before file replication can work), right-click Computer, and then click Manage.
2. Click to expand Services and Applications, and click WMI Control.
3. Right-click WMI Control, and click Properties.
4. On the Security tab, click to expand Root.
5. Click to expand MicrosoftDfs, and click Security at the bottom of the page.
6. Add Interactive group, and click OK.
7. Click to allow Execute Methods, Provider Write, and Enable Account privileges. Click OK.
| Logging bugs and feedback
When you log bugs, use the instructions on the Microsoft Beta Web site (http://go.microsoft.com/fwlink/?LinkId=46992). We are also interested in feature requests and general feedback about Windows Meeting Space.
Additional resources
Product support for Windows Vista is provided through the beta newsgroups. To access the newsgroups, use the instructions that are provided on the Microsoft Beta Web site at (http://go.microsoft.com/fwlink/?LinkId=46994). Members of the Windows Meeting Space team will monitor newsgroups, so you can post your questions and issues there. Beta testers who are part of the TAP Beta program can also contact their appointed Microsoft development team member for assistance.
If you are a beta tester and part of the special Technology Adoption Program (TAP) beta program, you can also contact your appointed Microsoft development team member for assistance.
Windows Peer-to-Peer Networking (http://go.microsoft.com/fwlink/?LinkId=59669)
|
