| Home | Register | Members | Search | Windows Vista Tips | File Database | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
We have some configuration issues with this system. It seems to me the SBS
is multihomed computers with two NICs (wired and wireless). It is not recommended. Also you may want to disable IPv6 on the server for troubleshooting. You may compare both VPN server and client routing table to see where the traffic will go. -- Bob Lin, Microsoft-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "Donny" <> wrote in message news  3AD6D33-015B-4865-951B-...> Here is the information from the server and also from the notebook. Sorry > for > the delay. They took it out of town for a day. > > ***From the server: > > C:\Users\svradmin>nslookup adminassist > Server: UnKnown > Address: fe80::9691:b7f6:e3da:589f > > Name: adminassist.company.local > Address: 192.168.2.36 > > C:\Users\svradmin>ping -a 192.168.2.36 > > Pinging 192.168.2.36 with 32 bytes of data: > Reply from 192.168.2.5: Destination host unreachable. > Reply from 192.168.2.5: Destination host unreachable. > Reply from 192.168.2.5: Destination host unreachable. > Reply from 192.168.2.5: Destination host unreachable. > > Ping statistics for 192.168.2.36: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > C:\Users\svradmin> > > ***From the Notebook off site with VPN connected. > > C:\Windows\system32>ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : ADMINASSIST > Primary Dns Suffix . . . . . . . : company.local > Node Type . . . . . . . . . . . . : Broadcast > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : company.local > > PPP adapter Company VPN Connection: > > Connection-specific DNS Suffix . : company.local > Description . . . . . . . . . . . : Company VPN Connection > Physical Address. . . . . . . . . : > DHCP Enabled. . . . . . . . . . . : No > Autoconfiguration Enabled . . . . : Yes > IPv4 Address. . . . . . . . . . . : 192.168.2.15(Preferred) > Subnet Mask . . . . . . . . . . . : 255.255.255.255 > Default Gateway . . . . . . . . . : 0.0.0.0 > DNS Servers . . . . . . . . . . . : 192.168.2.5 > Primary WINS Server . . . . . . . : 192.168.2.5 > NetBIOS over Tcpip. . . . . . . . : Enabled > > Wireless LAN adapter Wireless Network Connection: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN > Physical Address. . . . . . . . . : 00-1A-73-82-49-26 > DHCP Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > Link-local IPv6 Address . . . . . : > fe80::c5d:18d5:4104:1b19%10(Preferred) > IPv4 Address. . . . . . . . . . . : 192.168.0.113(Preferred) > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 6:39:42 > PM > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 6:39:42 > PM > Default Gateway . . . . . . . . . : 192.168.0.1 > DHCP Server . . . . . . . . . . . : 192.168.0.1 > DHCPv6 IAID . . . . . . . . . . . : 218110579 > DHCPv6 Client DUID. . . . . . . . : > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B > > DNS Servers . . . . . . . . . . . : 192.168.0.1 > NetBIOS over Tcpip. . . . . . . . : Enabled > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller > Physical Address. . . . . . . . . : 00-1B-24-81-B1-B7 > DHCP Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > Link-local IPv6 Address . . . . . : > fe80::c464:32ad:ed1:9e1d%9(Preferred) > IPv4 Address. . . . . . . . . . . : 192.168.0.125(Preferred) > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 6:39:45 > PM > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 6:39:45 > PM > Default Gateway . . . . . . . . . : 192.168.0.1 > DHCP Server . . . . . . . . . . . : 192.168.0.1 > DHCPv6 IAID . . . . . . . . . . . : 234887972 > DHCPv6 Client DUID. . . . . . . . : > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B > > DNS Servers . . . . . . . . . . . : 192.168.0.1 > NetBIOS over Tcpip. . . . . . . . : Enabled > > Tunnel adapter Local Area Connection*: > > Media State . . . . . . . . . . . : Media disconnected > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Microsoft ISATAP Adapter > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > DHCP Enabled. . . . . . . . . . . : No > Autoconfiguration Enabled . . . . : Yes > > Tunnel adapter Local Area Connection* 2: > > Media State . . . . . . . . . . . : Media disconnected > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter > Physical Address. . . . . . . . . : 02-00-54-55-4E-01 > DHCP Enabled. . . . . . . . . . . : No > Autoconfiguration Enabled . . . . : Yes > > Tunnel adapter Local Area Connection* 9: > > Media State . . . . . . . . . . . : Media disconnected > Connection-specific DNS Suffix . : company.local > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > DHCP Enabled. . . . . . . . . . . : No > Autoconfiguration Enabled . . . . : Yes > > Tunnel adapter Local Area Connection* 12: > > Media State . . . . . . . . . . . : Media disconnected > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > DHCP Enabled. . . . . . . . . . . : No > Autoconfiguration Enabled . . . . : Yes > > C:\Windows\system32> > > > Microsoft Windows [Version 6.0.6002] > Copyright (c) 2006 Microsoft Corporation. All rights reserved. > > C:\Users\stuart>net use s: \server12\data > s: has a remembered connection to \\server12\data. Do you > want to overwrite the remembered connection? (Y/N) [Y]: > System error 67 has occurred. > > The network name cannot be found. > > > C:\Users\stuart.>ping server12 > > Pinging server12.company.local [192.168.2.5] with 32 bytes of data: > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=22ms TTL=127 > > Ping statistics for 192.168.2.5: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 22ms, Maximum = 23ms, Average = 22ms > > C:\Users\stuart>ping 192.168.2.5 > > Pinging 192.168.2.5 with 32 bytes of data: > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Ping statistics for 192.168.2.5: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 23ms, Maximum = 23ms, Average = 23ms > > C:\Users\stuart>net view server12 > Shared resources at server12 > > > Share name Type Used as Comment > > ------------------------------------------------------------------------------- > RedirectedFolders Disk [Offline Share] > The command completed successfully. > > C:\Users\stuart> > > "Bob Lin (MS-MVP)" wrote: > >> Sounds like name resolution issue. Can you ping -a 192.168.2.36? Also >> post >> back the result of VPN client ipconfig /all may help. >> >> -- >> Bob Lin, Microsoft-MVP, MCSE & CNE >> Networking, Internet, Routing, VPN Troubleshooting on >> http://www.ChicagoTech.net >> How to Setup Windows, Network, VPN & Remote Access on >> http://www.HowToNetworking.com >> >> >> "Donny" <> wrote in message >> news:FF5F602D-A4C5-4EAE-AACC-... >> >I am logging in with the Domain username, not the local one. I think >> >that >> > this is a DNS issue but I don't know what I need to do to fix it. Here >> > is >> > some more information: >> > I have some more information on this. After I connect with VPN and i go >> > to >> > Network and Sharing center it says that my network is unathenticated. >> > My >> > VPN >> > IP address is 192.168.2.22 >> > Going on the server 192.168.2.5 I found the following: >> > >> > C:\Users\svradmin>ping adminassist >> > >> > Pinging adminassist.epic.local [192.168.2.36] with 32 bytes of data: >> > Reply from 192.168.2.5: Destination host unreachable. >> > >> > Ping statistics for 192.168.2.36: >> > Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), >> > >> > C:\Users\svradmin>ping 192.168.2.22 >> > >> > Pinging 192.168.2.22 with 32 bytes of data: >> > Reply from 192.168.2.22: bytes=32 time=23ms TTL=128 >> > >> > Ping statistics for 192.168.2.22: >> > Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), >> > Approximate round trip times in milli-seconds: >> > Minimum = 23ms, Maximum = 24ms, Average = 23ms >> > >> > C:\Users\svradmin>tracert 192.168.2.22 >> > >> > Tracing route to ADMINASSIST [192.168.2.22] >> > over a maximum of 30 hops: >> > >> > 1 23 ms 24 ms 24 ms ADMINASSIST [192.168.2.22] >> > >> > Trace complete. >> > >> > C:\Users\svradmin>nslookup adminassist >> > Server: UnKnown >> > Address: fe20::9661:b7f6:e3da:559f >> > >> > Name: adminassist.company.local >> > Address: 192.168.2.36 >> > >> > >> > "Bob Lin (MS-MVP)" wrote: >> > >> >> Do you logon local user or domain user? It could be credentials issue. >> >> try >> >> net use domainname\username to map the drive. or this search result >> >> may >> >> help. >> >> Can access remote computer via VPN occasionally >> >> However, when the same user access the VPN, he uses cached >> >> credentials >> >> to access the remote computer. The VPN user may lose the cached >> >> credentials >> >> and may ... >> >> www.chicagotech.net/casestudy/vpnaccess1.htm >> >> >> >> >> >> -- >> >> Bob Lin, Microsoft-MVP, MCSE & CNE >> >> Networking, Internet, Routing, VPN Troubleshooting on >> >> http://www.ChicagoTech.net >> >> How to Setup Windows, Network, VPN & Remote Access on >> >> http://www.HowToNetworking.com >> >> >> >> >> >> "Donny" <> wrote in message >> >> news:A91805D6-6462-4D13-92FB-... >> >> >I am having problems connecting to Network Shares over VPN >> >> > I am suspecting that this is a network security issue and I am very >> >> > weak >> >> > in >> >> > this area. >> >> > >> >> > My server is SBS 2008 and it is fully patched. All of the laptops >> >> > are >> >> > Vista >> >> > Business 32 bit. >> >> > If I connect to the VPN by using the Vista Network Login I can >> >> > connect >> >> > and >> >> > everything works well, if on only if I connect through a wired >> >> > connection. >> >> > I have made sure that my first NIC to load is my wireless NIC. I >> >> > cannot >> >> > connect to VPN through a Network logon using wireless. It appears >> >> > that >> >> > my >> >> > Wireless connection doesn't start or doesn’t connect until after I >> >> > have >> >> > logged into a user account. >> >> > >> >> > If I log in normally then connect to VPN, I can ping the server by >> >> > DNS >> >> > name >> >> > and also by IP address, however, I cannot see any shares and I >> >> > cannot >> >> > connect >> >> > to them. If I try to connect I get a message that either says >> >> > “incorrect >> >> > password or unknown username for \\server\Share” and also an error >> >> > occurred >> >> > while reconnecting S: to \\server\share or else I get: “Microsoft >> >> > Windows >> >> > Network: The network path was not found” >> >> > >> >> > I don't know what to look for in order to determine if the problem >> >> > is >> >> > on >> >> > the >> >> > remote workstation, the Server or the Router. The company is small, >> >> > about >> >> > 10 >> >> > users, and we use a Linksys WRT160N router. I would change routers >> >> > if I >> >> > knew >> >> > that the router was the issue. >> >> > >> >> > The server event log doesn't show any VPN or connection/logon errors >> >> > in >> >> > it. >> >> > The router log is empty. >> >> > >> >> >> |
|
|
|
|
|||
|
Guest
Posts: n/a
|
Hello again, We have a wired and wirelesss network in the office, however, the server only has 1 NIC. How should I proceed with this? I don't think I can disable IP v6 as this is a SBS Server and Exchange puts up a major fuss is IP v6 is disabled. Ho do I compare both VPN server and client routing tables? "Bob Lin (MS-MVP)" wrote: > We have some configuration issues with this system. It seems to me the SBS > is multihomed computers with two NICs (wired and wireless). It is not > recommended. Also you may want to disable IPv6 on the server for > troubleshooting. You may compare both VPN server and client routing table to > see where the traffic will go. > > -- > Bob Lin, Microsoft-MVP, MCSE & CNE > Networking, Internet, Routing, VPN Troubleshooting on > http://www.ChicagoTech.net > How to Setup Windows, Network, VPN & Remote Access on > http://www.HowToNetworking.com > > > "Donny" <> wrote in message > news 3AD6D33-015B-4865-951B-...> > Here is the information from the server and also from the notebook. Sorry > > for > > the delay. They took it out of town for a day. > > > > ***From the server: > > > > C:\Users\svradmin>nslookup adminassist > > Server: UnKnown > > Address: fe80::9691:b7f6:e3da:589f > > > > Name: adminassist.company.local > > Address: 192.168.2.36 > > > > C:\Users\svradmin>ping -a 192.168.2.36 > > > > Pinging 192.168.2.36 with 32 bytes of data: > > Reply from 192.168.2.5: Destination host unreachable. > > Reply from 192.168.2.5: Destination host unreachable. > > Reply from 192.168.2.5: Destination host unreachable. > > Reply from 192.168.2.5: Destination host unreachable. > > > > Ping statistics for 192.168.2.36: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > > C:\Users\svradmin> > > > > ***From the Notebook off site with VPN connected. > > > > C:\Windows\system32>ipconfig /all > > > > Windows IP Configuration > > > > Host Name . . . . . . . . . . . . : ADMINASSIST > > Primary Dns Suffix . . . . . . . : company.local > > Node Type . . . . . . . . . . . . : Broadcast > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > DNS Suffix Search List. . . . . . : company.local > > > > PPP adapter Company VPN Connection: > > > > Connection-specific DNS Suffix . : company.local > > Description . . . . . . . . . . . : Company VPN Connection > > Physical Address. . . . . . . . . : > > DHCP Enabled. . . . . . . . . . . : No > > Autoconfiguration Enabled . . . . : Yes > > IPv4 Address. . . . . . . . . . . : 192.168.2.15(Preferred) > > Subnet Mask . . . . . . . . . . . : 255.255.255.255 > > Default Gateway . . . . . . . . . : 0.0.0.0 > > DNS Servers . . . . . . . . . . . : 192.168.2.5 > > Primary WINS Server . . . . . . . : 192.168.2.5 > > NetBIOS over Tcpip. . . . . . . . : Enabled > > > > Wireless LAN adapter Wireless Network Connection: > > > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN > > Physical Address. . . . . . . . . : 00-1A-73-82-49-26 > > DHCP Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > Link-local IPv6 Address . . . . . : > > fe80::c5d:18d5:4104:1b19%10(Preferred) > > IPv4 Address. . . . . . . . . . . : 192.168.0.113(Preferred) > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 6:39:42 > > PM > > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 6:39:42 > > PM > > Default Gateway . . . . . . . . . : 192.168.0.1 > > DHCP Server . . . . . . . . . . . : 192.168.0.1 > > DHCPv6 IAID . . . . . . . . . . . : 218110579 > > DHCPv6 Client DUID. . . . . . . . : > > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B > > > > DNS Servers . . . . . . . . . . . : 192.168.0.1 > > NetBIOS over Tcpip. . . . . . . . : Enabled > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller > > Physical Address. . . . . . . . . : 00-1B-24-81-B1-B7 > > DHCP Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > Link-local IPv6 Address . . . . . : > > fe80::c464:32ad:ed1:9e1d%9(Preferred) > > IPv4 Address. . . . . . . . . . . : 192.168.0.125(Preferred) > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 6:39:45 > > PM > > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 6:39:45 > > PM > > Default Gateway . . . . . . . . . : 192.168.0.1 > > DHCP Server . . . . . . . . . . . : 192.168.0.1 > > DHCPv6 IAID . . . . . . . . . . . : 234887972 > > DHCPv6 Client DUID. . . . . . . . : > > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B > > > > DNS Servers . . . . . . . . . . . : 192.168.0.1 > > NetBIOS over Tcpip. . . . . . . . : Enabled > > > > Tunnel adapter Local Area Connection*: > > > > Media State . . . . . . . . . . . : Media disconnected > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Microsoft ISATAP Adapter > > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > > DHCP Enabled. . . . . . . . . . . : No > > Autoconfiguration Enabled . . . . : Yes > > > > Tunnel adapter Local Area Connection* 2: > > > > Media State . . . . . . . . . . . : Media disconnected > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter > > Physical Address. . . . . . . . . : 02-00-54-55-4E-01 > > DHCP Enabled. . . . . . . . . . . : No > > Autoconfiguration Enabled . . . . : Yes > > > > Tunnel adapter Local Area Connection* 9: > > > > Media State . . . . . . . . . . . : Media disconnected > > Connection-specific DNS Suffix . : company.local > > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 > > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > > DHCP Enabled. . . . . . . . . . . : No > > Autoconfiguration Enabled . . . . : Yes > > > > Tunnel adapter Local Area Connection* 12: > > > > Media State . . . . . . . . . . . : Media disconnected > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 > > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 > > DHCP Enabled. . . . . . . . . . . : No > > Autoconfiguration Enabled . . . . : Yes > > > > C:\Windows\system32> > > > > > > Microsoft Windows [Version 6.0.6002] > > Copyright (c) 2006 Microsoft Corporation. All rights reserved. > > > > C:\Users\stuart>net use s: \server12\data > > s: has a remembered connection to \\server12\data. Do you > > want to overwrite the remembered connection? (Y/N) [Y]: > > System error 67 has occurred. > > > > The network name cannot be found. > > > > > > C:\Users\stuart.>ping server12 > > > > Pinging server12.company.local [192.168.2.5] with 32 bytes of data: > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=22ms TTL=127 > > > > Ping statistics for 192.168.2.5: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > Approximate round trip times in milli-seconds: > > Minimum = 22ms, Maximum = 23ms, Average = 22ms > > > > C:\Users\stuart>ping 192.168.2.5 > > > > Pinging 192.168.2.5 with 32 bytes of data: > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 > > > > Ping statistics for 192.168.2.5: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > Approximate round trip times in milli-seconds: > > Minimum = 23ms, Maximum = 23ms, Average = 23ms > > > > C:\Users\stuart>net view server12 > > Shared resources at server12 > > > > > > Share name Type Used as Comment > > > > ------------------------------------------------------------------------------- > > RedirectedFolders Disk [Offline Share] > > The command completed successfully. > > > > C:\Users\stuart> > > > > "Bob Lin (MS-MVP)" wrote: > > > >> Sounds like name resolution issue. Can you ping -a 192.168.2.36? Also > >> post > >> back the result of VPN client ipconfig /all may help. > >> > >> -- > >> Bob Lin, Microsoft-MVP, MCSE & CNE > >> Networking, Internet, Routing, VPN Troubleshooting on > >> http://www.ChicagoTech.net > >> How to Setup Windows, Network, VPN & Remote Access on > >> http://www.HowToNetworking.com > >> > >> > >> "Donny" <> wrote in message > >> news:FF5F602D-A4C5-4EAE-AACC-... > >> >I am logging in with the Domain username, not the local one. I think > >> >that > >> > this is a DNS issue but I don't know what I need to do to fix it. Here > >> > is > >> > some more information: > >> > I have some more information on this. After I connect with VPN and i go > >> > to > >> > Network and Sharing center it says that my network is unathenticated. > >> > My > >> > VPN > >> > IP address is 192.168.2.22 > >> > Going on the server 192.168.2.5 I found the following: > >> > > >> > C:\Users\svradmin>ping adminassist > >> > > >> > Pinging adminassist.epic.local [192.168.2.36] with 32 bytes of data: > >> > Reply from 192.168.2.5: Destination host unreachable. > >> > > >> > Ping statistics for 192.168.2.36: > >> > Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), > >> > > >> > C:\Users\svradmin>ping 192.168.2.22 > >> > > >> > Pinging 192.168.2.22 with 32 bytes of data: > >> > Reply from 192.168.2.22: bytes=32 time=23ms TTL=128 > >> > > >> > Ping statistics for 192.168.2.22: > >> > Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), > >> > Approximate round trip times in milli-seconds: > >> > Minimum = 23ms, Maximum = 24ms, Average = 23ms > >> > > >> > C:\Users\svradmin>tracert 192.168.2.22 > >> > > >> > Tracing route to ADMINASSIST [192.168.2.22] > >> > over a maximum of 30 hops: > >> > > >> > 1 23 ms 24 ms 24 ms ADMINASSIST [192.168.2.22] > >> > > >> > Trace complete. > >> > > >> > C:\Users\svradmin>nslookup adminassist > >> > Server: UnKnown > >> > Address: fe20::9661:b7f6:e3da:559f > >> > > >> > Name: adminassist.company.local > >> > Address: 192.168.2.36 > >> > > >> > > >> > "Bob Lin (MS-MVP)" wrote: > >> > > >> >> Do you logon local user or domain user? It could be credentials issue. > >> >> try > >> >> net use domainname\username to map the drive. or this search result > >> >> may > >> >> help. > >> >> Can access remote computer via VPN occasionally > >> >> However, when the same user access the VPN, he uses cached > >> >> credentials > >> >> to access the remote computer. The VPN user may lose the cached > >> >> credentials > >> >> and may ... > >> >> www.chicagotech.net/casestudy/vpnaccess1.htm > >> >> > >> >> > >> >> -- > >> >> Bob Lin, Microsoft-MVP, MCSE & CNE > >> >> Networking, Internet, Routing, VPN Troubleshooting on > >> >> http://www.ChicagoTech.net > >> >> How to Setup Windows, Network, VPN & Remote Access on > >> >> http://www.HowToNetworking.com > >> >> > >> >> > >> >> "Donny" <> wrote in message > >> >> news:A91805D6-6462-4D13-92FB-... > >> >> >I am having problems connecting to Network Shares over VPN > >> >> > I am suspecting that this is a network security issue and I am very > >> >> > weak > >> >> > in > >> >> > this area. |
|
|
|
|
|||
|
Guest
Posts: n/a
|
"Donny" <> wrote in message
news:97F6991A-046E-4A62-B7A5-... > Hello again, > We have a wired and wirelesss network in the office, however, the server > only has 1 NIC. How should I proceed with this? > I don't think I can disable IP v6 as this is a SBS Server and Exchange > puts > up a major fuss is IP v6 is disabled. > > Ho do I compare both VPN server and client routing tables? Hello Donny, Actually, since this is SBS, it should have been posted to the SBS newsgroup, where those folks could have given you specific help. I cross-posted it for you. You can simply check back here for responses, if any. And yes, disabling IPv6 is one of the best things you can do. After all, are you using it? Do you have some sort of large infrasturcture using a BGP routing scheme (such as the backbone of a university) that is based on IPv6? If so, then you would need to keep IPv6. Otherwise, it's additional overhead that is checked during communication, and of course not used because there may be other machines that do not have it installed. Disabling it eliminates additional processing overhead and the additional IPv6 IP. Also, disabling the RSS/TCP Chimney feature is helpfule with network transfer issues associated with it. Read the following on how to disable IPv6. And no, it will NOT cause any problems with Exchange. It will help with communication between Exchange and the DC (even if on the same server). ================================================== ================ ================================================== ================ How to Disable IPv6 There are known issues regarding IPv6 affecting communications in certain scenarios, such as with errors when using Outlook Anywhere such as to fix an Exchange/DC NSPI port 6004 communication issue, among many others. Therefore to eliminiate communications issues regarding whether this is a factor or not, it is recommended to disable IPv6 in registry on the Exchange server, as well as on the domain controllers, or any server for that matter, especially if there are no plans in using IPv6. To disable IPv6 on 2008 or Vista: Uncheck IPv6 in NIC properties Uncheck the two LinkLayer Topology Discovery components Then follow the registry changes procedure below to completely disable IPv6. 1. Navigate to: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters] 2. In the details pane, click New, and then click DWORD (32-bit) Value. 3. Type in DisabledComponents , and then press ENTER. 4. Double-click DisabledComponents, 5. Type ff in Hexadecimal. 6. So it should like this when completed: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters] "DisabledComponents"=dword:000000ff ==== More info: The installation of the Exchange Server 2007 Hub Transport role is unsuccessful on a Windows Server 2008-based computer http://support.microsoft.com/?id=952842 Disabling IPv6 on Windows 2008 or Vista http://blogs.dirteam.com/blogs/paulb...dows-2008.aspx --- Interesting view point by "Anteaus" publicly posted to a newsgroup post in thread: Subject: Re: Should we disable IPv6 ? Date: Sat, 27 Jun 2009 00:42:01 -0700 Newsgroups: microsoft.public.windows.server.networking The issue, as I understand it, is that IPv4 addresses will eventually run out, and when they do, any new webhosts will have to use IPv6 addresses ONLY. Thus if your client-kit sticks with IPv4 after that date there will be a gradually-increasing number of websites which will be inaccessible to you. Whether this actually matters will of course depend on what you need to access. As for IPv6 being a logical step forward, I dispute that. On the contrary, IPv6 is a total departure from a well-proven scheme which works, to one which is not only unproven but which already has a number of identified compatibility bugs, for example IPv6 addresses are incompatible with UNC paths. Extending the existing scheme to five or six octets would be the simple, sensible choice, unfortunately the "Let's make things complicated" crew got-in on the act, as they so often do. --- ================================================== ================ ================================================== ================ -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution. Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging Microsoft Certified Trainer For urgent issues, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. ================================================== ================ ================================================== ================ ================================================== ================ > > "Bob Lin (MS-MVP)" wrote: > >> We have some configuration issues with this system. It seems to me the >> SBS >> is multihomed computers with two NICs (wired and wireless). It is not >> recommended. Also you may want to disable IPv6 on the server for >> troubleshooting. You may compare both VPN server and client routing table >> to >> see where the traffic will go. >> >> -- >> Bob Lin, Microsoft-MVP, MCSE & CNE >> Networking, Internet, Routing, VPN Troubleshooting on >> http://www.ChicagoTech.net >> How to Setup Windows, Network, VPN & Remote Access on >> http://www.HowToNetworking.com >> >> >> "Donny" <> wrote in message >> news 3AD6D33-015B-4865-951B-...>> > Here is the information from the server and also from the notebook. >> > Sorry >> > for >> > the delay. They took it out of town for a day. >> > >> > ***From the server: >> > >> > C:\Users\svradmin>nslookup adminassist >> > Server: UnKnown >> > Address: fe80::9691:b7f6:e3da:589f >> > >> > Name: adminassist.company.local >> > Address: 192.168.2.36 >> > >> > C:\Users\svradmin>ping -a 192.168.2.36 >> > >> > Pinging 192.168.2.36 with 32 bytes of data: >> > Reply from 192.168.2.5: Destination host unreachable. >> > Reply from 192.168.2.5: Destination host unreachable. >> > Reply from 192.168.2.5: Destination host unreachable. >> > Reply from 192.168.2.5: Destination host unreachable. >> > >> > Ping statistics for 192.168.2.36: >> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> > >> > C:\Users\svradmin> >> > >> > ***From the Notebook off site with VPN connected. >> > >> > C:\Windows\system32>ipconfig /all >> > >> > Windows IP Configuration >> > >> > Host Name . . . . . . . . . . . . : ADMINASSIST >> > Primary Dns Suffix . . . . . . . : company.local >> > Node Type . . . . . . . . . . . . : Broadcast >> > IP Routing Enabled. . . . . . . . : No >> > WINS Proxy Enabled. . . . . . . . : No >> > DNS Suffix Search List. . . . . . : company.local >> > >> > PPP adapter Company VPN Connection: >> > >> > Connection-specific DNS Suffix . : company.local >> > Description . . . . . . . . . . . : Company VPN Connection >> > Physical Address. . . . . . . . . : >> > DHCP Enabled. . . . . . . . . . . : No >> > Autoconfiguration Enabled . . . . : Yes >> > IPv4 Address. . . . . . . . . . . : 192.168.2.15(Preferred) >> > Subnet Mask . . . . . . . . . . . : 255.255.255.255 >> > Default Gateway . . . . . . . . . : 0.0.0.0 >> > DNS Servers . . . . . . . . . . . : 192.168.2.5 >> > Primary WINS Server . . . . . . . : 192.168.2.5 >> > NetBIOS over Tcpip. . . . . . . . : Enabled >> > >> > Wireless LAN adapter Wireless Network Connection: >> > >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN >> > Physical Address. . . . . . . . . : 00-1A-73-82-49-26 >> > DHCP Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > Link-local IPv6 Address . . . . . : >> > fe80::c5d:18d5:4104:1b19%10(Preferred) >> > IPv4 Address. . . . . . . . . . . : 192.168.0.113(Preferred) >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 >> > 6:39:42 >> > PM >> > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 >> > 6:39:42 >> > PM >> > Default Gateway . . . . . . . . . : 192.168.0.1 >> > DHCP Server . . . . . . . . . . . : 192.168.0.1 >> > DHCPv6 IAID . . . . . . . . . . . : 218110579 >> > DHCPv6 Client DUID. . . . . . . . : >> > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B >> > >> > DNS Servers . . . . . . . . . . . : 192.168.0.1 >> > NetBIOS over Tcpip. . . . . . . . : Enabled >> > >> > Ethernet adapter Local Area Connection: >> > >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : NVIDIA nForce Networking >> > Controller >> > Physical Address. . . . . . . . . : 00-1B-24-81-B1-B7 >> > DHCP Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > Link-local IPv6 Address . . . . . : >> > fe80::c464:32ad:ed1:9e1d%9(Preferred) >> > IPv4 Address. . . . . . . . . . . : 192.168.0.125(Preferred) >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 >> > 6:39:45 >> > PM >> > Lease Expires . . . . . . . . . . : Friday, September 04, 2009 >> > 6:39:45 >> > PM >> > Default Gateway . . . . . . . . . : 192.168.0.1 >> > DHCP Server . . . . . . . . . . . : 192.168.0.1 >> > DHCPv6 IAID . . . . . . . . . . . : 234887972 >> > DHCPv6 Client DUID. . . . . . . . : >> > 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B >> > >> > DNS Servers . . . . . . . . . . . : 192.168.0.1 >> > NetBIOS over Tcpip. . . . . . . . : Enabled >> > >> > Tunnel adapter Local Area Connection*: >> > >> > Media State . . . . . . . . . . . : Media disconnected >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : Microsoft ISATAP Adapter >> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >> > DHCP Enabled. . . . . . . . . . . : No >> > Autoconfiguration Enabled . . . . : Yes >> > >> > Tunnel adapter Local Area Connection* 2: >> > >> > Media State . . . . . . . . . . . : Media disconnected >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter >> > Physical Address. . . . . . . . . : 02-00-54-55-4E-01 >> > DHCP Enabled. . . . . . . . . . . : No >> > Autoconfiguration Enabled . . . . : Yes >> > >> > Tunnel adapter Local Area Connection* 9: >> > >> > Media State . . . . . . . . . . . : Media disconnected >> > Connection-specific DNS Suffix . : company.local >> > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 >> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >> > DHCP Enabled. . . . . . . . . . . : No >> > Autoconfiguration Enabled . . . . : Yes >> > >> > Tunnel adapter Local Area Connection* 12: >> > >> > Media State . . . . . . . . . . . : Media disconnected >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 >> > Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >> > DHCP Enabled. . . . . . . . . . . : No >> > Autoconfiguration Enabled . . . . : Yes >> > >> > C:\Windows\system32> >> > >> > >> > Microsoft Windows [Version 6.0.6002] >> > Copyright (c) 2006 Microsoft Corporation. All rights reserved. >> > >> > C:\Users\stuart>net use s: \server12\data >> > s: has a remembered connection to \\server12\data. Do you >> > want to overwrite the remembered connection? (Y/N) [Y]: >> > System error 67 has occurred. >> > >> > The network name cannot be found. >> > >> > >> > C:\Users\stuart.>ping server12 >> > >> > Pinging server12.company.local [192.168.2.5] with 32 bytes of data: >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=22ms TTL=127 >> > >> > Ping statistics for 192.168.2.5: >> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> > Approximate round trip times in milli-seconds: >> > Minimum = 22ms, Maximum = 23ms, Average = 22ms >> > >> > C:\Users\stuart>ping 192.168.2.5 >> > >> > Pinging 192.168.2.5 with 32 bytes of data: >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >> > >> > Ping statistics for 192.168.2.5: >> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> > Approximate round trip times in milli-seconds: >> > Minimum = 23ms, Maximum = 23ms, Average = 23ms >> > >> > C:\Users\stuart>net view server12 >> > Shared resources at server12 >> > >> > >> > Share name Type Used as Comment >> > >> > ------------------------------------------------------------------------------- >> > RedirectedFolders Disk [Offline Share] >> > The command completed successfully. >> > >> > C:\Users\stuart> >> > >> > "Bob Lin (MS-MVP)" wrote: >> > >> >> Sounds like name resolution issue. Can you ping -a 192.168.2.36? Also >> >> post >> >> back the result of VPN client ipconfig /all may help. >> >> >> >> -- >> >> Bob Lin, Microsoft-MVP, MCSE & CNE >> >> Networking, Internet, Routing, VPN Troubleshooting on >> >> http://www.ChicagoTech.net >> >> How to Setup Windows, Network, VPN & Remote Access on >> >> http://www.HowToNetworking.com >> >> >> >> >> >> "Donny" <> wrote in message >> >> news:FF5F602D-A4C5-4EAE-AACC-... >> >> >I am logging in with the Domain username, not the local one. I think >> >> >that >> >> > this is a DNS issue but I don't know what I need to do to fix it. >> >> > Here >> >> > is >> >> > some more information: >> >> > I have some more information on this. After I connect with VPN and i >> >> > go >> >> > to >> >> > Network and Sharing center it says that my network is >> >> > unathenticated. >> >> > My >> >> > VPN >> >> > IP address is 192.168.2.22 >> >> > Going on the server 192.168.2.5 I found the following: >> >> > >> >> > C:\Users\svradmin>ping adminassist >> >> > >> >> > Pinging adminassist.epic.local [192.168.2.36] with 32 bytes of data: >> >> > Reply from 192.168.2.5: Destination host unreachable. >> >> > >> >> > Ping statistics for 192.168.2.36: >> >> > Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), >> >> > >> >> > C:\Users\svradmin>ping 192.168.2.22 >> >> > >> >> > Pinging 192.168.2.22 with 32 bytes of data: >> >> > Reply from 192.168.2.22: bytes=32 time=23ms TTL=128 >> >> > >> >> > Ping statistics for 192.168.2.22: >> >> > Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), >> >> > Approximate round trip times in milli-seconds: >> >> > Minimum = 23ms, Maximum = 24ms, Average = 23ms >> >> > >> >> > C:\Users\svradmin>tracert 192.168.2.22 >> >> > >> >> > Tracing route to ADMINASSIST [192.168.2.22] >> >> > over a maximum of 30 hops: >> >> > >> >> > 1 23 ms 24 ms 24 ms ADMINASSIST [192.168.2.22] >> >> > >> >> > Trace complete. >> >> > >> >> > C:\Users\svradmin>nslookup adminassist >> >> > Server: UnKnown >> >> > Address: fe20::9661:b7f6:e3da:559f >> >> > >> >> > Name: adminassist.company.local >> >> > Address: 192.168.2.36 >> >> > >> >> > >> >> > "Bob Lin (MS-MVP)" wrote: >> >> > >> >> >> Do you logon local user or domain user? It could be credentials >> >> >> issue. >> >> >> try >> >> >> net use domainname\username to map the drive. or this search result >> >> >> may >> >> >> help. >> >> >> Can access remote computer via VPN occasionally >> >> >> However, when the same user access the VPN, he uses cached >> >> >> credentials >> >> >> to access the remote computer. The VPN user may lose the cached >> >> >> credentials >> >> >> and may ... >> >> >> www.chicagotech.net/casestudy/vpnaccess1.htm >> >> >> >> >> >> >> >> >> -- >> >> >> Bob Lin, Microsoft-MVP, MCSE & CNE >> >> >> Networking, Internet, Routing, VPN Troubleshooting on >> >> >> http://www.ChicagoTech.net >> >> >> How to Setup Windows, Network, VPN & Remote Access on >> >> >> http://www.HowToNetworking.com >> >> >> >> >> >> >> >> >> "Donny" <> wrote in message >> >> >> news:A91805D6-6462-4D13-92FB-... >> >> >> >I am having problems connecting to Network Shares over VPN >> >> >> > I am suspecting that this is a network security issue and I am >> >> >> > very >> >> >> > weak >> >> >> > in >> >> >> > this area. |
|
|
|
|
|||
|
Guest
Posts: n/a
|
This is from the MS SBS2008 blog regarding disabling ipv6, slightly
different than Ace's instructions: http://blogs.technet.com/sbs/archive...6/default.aspx -- Allan Williams Ace Fekay [MCT] wrote: > "Donny" <> wrote in message > news:97F6991A-046E-4A62-B7A5-... >> Hello again, >> We have a wired and wirelesss network in the office, however, the >> server only has 1 NIC. How should I proceed with this? >> I don't think I can disable IP v6 as this is a SBS Server and >> Exchange puts >> up a major fuss is IP v6 is disabled. >> >> Ho do I compare both VPN server and client routing tables? > > Hello Donny, > > Actually, since this is SBS, it should have been posted to the SBS > newsgroup, where those folks could have given you specific help. I > cross-posted it for you. You can simply check back here for > responses, if any. > > And yes, disabling IPv6 is one of the best things you can do. After > all, are you using it? Do you have some sort of large infrasturcture > using a BGP routing scheme (such as the backbone of a university) > that is based on IPv6? If so, then you would need to keep IPv6. > Otherwise, it's additional overhead that is checked during > communication, and of course not used because there may be other > machines that do not have it installed. Disabling it eliminates > additional processing overhead and the additional IPv6 IP. > Also, disabling the RSS/TCP Chimney feature is helpfule with network > transfer issues associated with it. > > Read the following on how to disable IPv6. And no, it will NOT cause > any problems with Exchange. It will help with communication between > Exchange and the DC (even if on the same server). > > ================================================== ================ > ================================================== ================ > How to Disable IPv6 > > There are known issues regarding IPv6 affecting communications in > certain scenarios, such as with errors when using Outlook Anywhere > such as to fix an Exchange/DC NSPI port 6004 communication issue, > among many others. Therefore to eliminiate communications issues > regarding whether this is a factor or not, it is recommended to > disable IPv6 in registry on the Exchange server, as well as on the > domain controllers, or any server for that matter, especially if > there are no plans in using IPv6. > To disable IPv6 on 2008 or Vista: > > Uncheck IPv6 in NIC properties > Uncheck the two LinkLayer Topology Discovery components > Then follow the registry changes procedure below to completely > disable IPv6. > 1. Navigate to: > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters] > 2. In the details pane, click New, and then click DWORD (32-bit) > Value. 3. Type in DisabledComponents , and then press ENTER. > 4. Double-click DisabledComponents, > 5. Type ff in Hexadecimal. > 6. So it should like this when completed: > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters] > "DisabledComponents"=dword:000000ff > > ==== > More info: > > The installation of the Exchange Server 2007 Hub Transport role is > unsuccessful on a Windows Server 2008-based computer > http://support.microsoft.com/?id=952842 > > Disabling IPv6 on Windows 2008 or Vista > http://blogs.dirteam.com/blogs/paulb...dows-2008.aspx > > --- > > Interesting view point by "Anteaus" publicly posted to a newsgroup > post in thread: > Subject: Re: Should we disable IPv6 ? > Date: Sat, 27 Jun 2009 00:42:01 -0700 > Newsgroups: microsoft.public.windows.server.networking > > The issue, as I understand it, is that IPv4 addresses will eventually > run out, and when they do, any new webhosts will have to use IPv6 > addresses ONLY. > Thus if your client-kit sticks with IPv4 after that date there will > be a gradually-increasing number of websites which will be > inaccessible to you. Whether this actually matters will of course > depend on what you need to access. > > As for IPv6 being a logical step forward, I dispute that. On the > contrary, IPv6 is a total departure from a well-proven scheme which > works, to one which > is not only unproven but which already has a number of identified > compatibility bugs, for example IPv6 addresses are incompatible with > UNC paths. Extending the existing scheme to five or six octets would > be the simple, sensible choice, unfortunately the "Let's make things > complicated" crew got-in on the act, as they so often do. > --- > ================================================== ================ > ================================================== ================ > > > For urgent issues, please contact Microsoft PSS directly. Please check > http://support.microsoft.com for regional support phone numbers. > ================================================== ================ > ================================================== ================ > ================================================== ================ >> >> "Bob Lin (MS-MVP)" wrote: >> >>> We have some configuration issues with this system. It seems to me >>> the SBS >>> is multihomed computers with two NICs (wired and wireless). It is >>> not recommended. Also you may want to disable IPv6 on the server for >>> troubleshooting. You may compare both VPN server and client routing >>> table to >>> see where the traffic will go. >>> >>> -- >>> Bob Lin, Microsoft-MVP, MCSE & CNE >>> Networking, Internet, Routing, VPN Troubleshooting on >>> http://www.ChicagoTech.net >>> How to Setup Windows, Network, VPN & Remote Access on >>> http://www.HowToNetworking.com >>> >>> >>> "Donny" <> wrote in message >>> news 3AD6D33-015B-4865-951B-...>>>> Here is the information from the server and also from the notebook. >>>> Sorry >>>> for >>>> the delay. They took it out of town for a day. >>>> >>>> ***From the server: >>>> >>>> C:\Users\svradmin>nslookup adminassist >>>> Server: UnKnown >>>> Address: fe80::9691:b7f6:e3da:589f >>>> >>>> Name: adminassist.company.local >>>> Address: 192.168.2.36 >>>> >>>> C:\Users\svradmin>ping -a 192.168.2.36 >>>> >>>> Pinging 192.168.2.36 with 32 bytes of data: >>>> Reply from 192.168.2.5: Destination host unreachable. >>>> Reply from 192.168.2.5: Destination host unreachable. >>>> Reply from 192.168.2.5: Destination host unreachable. >>>> Reply from 192.168.2.5: Destination host unreachable. >>>> >>>> Ping statistics for 192.168.2.36: >>>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >>>> >>>> C:\Users\svradmin> >>>> >>>> ***From the Notebook off site with VPN connected. >>>> >>>> C:\Windows\system32>ipconfig /all >>>> >>>> Windows IP Configuration >>>> >>>> Host Name . . . . . . . . . . . . : ADMINASSIST >>>> Primary Dns Suffix . . . . . . . : company.local >>>> Node Type . . . . . . . . . . . . : Broadcast >>>> IP Routing Enabled. . . . . . . . : No >>>> WINS Proxy Enabled. . . . . . . . : No >>>> DNS Suffix Search List. . . . . . : company.local >>>> >>>> PPP adapter Company VPN Connection: >>>> >>>> Connection-specific DNS Suffix . : company.local >>>> Description . . . . . . . . . . . : Company VPN Connection >>>> Physical Address. . . . . . . . . : >>>> DHCP Enabled. . . . . . . . . . . : No >>>> Autoconfiguration Enabled . . . . : Yes >>>> IPv4 Address. . . . . . . . . . . : 192.168.2.15(Preferred) >>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255 >>>> Default Gateway . . . . . . . . . : 0.0.0.0 >>>> DNS Servers . . . . . . . . . . . : 192.168.2.5 >>>> Primary WINS Server . . . . . . . : 192.168.2.5 >>>> NetBIOS over Tcpip. . . . . . . . : Enabled >>>> >>>> Wireless LAN adapter Wireless Network Connection: >>>> >>>> Connection-specific DNS Suffix . : >>>> Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN >>>> Physical Address. . . . . . . . . : 00-1A-73-82-49-26 >>>> DHCP Enabled. . . . . . . . . . . : Yes >>>> Autoconfiguration Enabled . . . . : Yes >>>> Link-local IPv6 Address . . . . . : >>>> fe80::c5d:18d5:4104:1b19%10(Preferred) >>>> IPv4 Address. . . . . . . . . . . : 192.168.0.113(Preferred) >>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0 >>>> Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 >>>> 6:39:42 >>>> PM >>>> Lease Expires . . . . . . . . . . : Friday, September 04, 2009 >>>> 6:39:42 >>>> PM >>>> Default Gateway . . . . . . . . . : 192.168.0.1 >>>> DHCP Server . . . . . . . . . . . : 192.168.0.1 >>>> DHCPv6 IAID . . . . . . . . . . . : 218110579 >>>> DHCPv6 Client DUID. . . . . . . . : >>>> 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B >>>> >>>> DNS Servers . . . . . . . . . . . : 192.168.0.1 >>>> NetBIOS over Tcpip. . . . . . . . : Enabled >>>> >>>> Ethernet adapter Local Area Connection: >>>> >>>> Connection-specific DNS Suffix . : >>>> Description . . . . . . . . . . . : NVIDIA nForce Networking >>>> Controller >>>> Physical Address. . . . . . . . . : 00-1B-24-81-B1-B7 >>>> DHCP Enabled. . . . . . . . . . . : Yes >>>> Autoconfiguration Enabled . . . . : Yes >>>> Link-local IPv6 Address . . . . . : >>>> fe80::c464:32ad:ed1:9e1d%9(Preferred) >>>> IPv4 Address. . . . . . . . . . . : 192.168.0.125(Preferred) >>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0 >>>> Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 >>>> 6:39:45 >>>> PM >>>> Lease Expires . . . . . . . . . . : Friday, September 04, 2009 >>>> 6:39:45 >>>> PM >>>> Default Gateway . . . . . . . . . : 192.168.0.1 >>>> DHCP Server . . . . . . . . . . . : 192.168.0.1 >>>> DHCPv6 IAID . . . . . . . . . . . : 234887972 >>>> DHCPv6 Client DUID. . . . . . . . : >>>> 00-01-00-01-11-C0-B3-57-00-1B-24-81-B1-B >>>> >>>> DNS Servers . . . . . . . . . . . : 192.168.0.1 >>>> NetBIOS over Tcpip. . . . . . . . : Enabled >>>> >>>> Tunnel adapter Local Area Connection*: >>>> >>>> Media State . . . . . . . . . . . : Media disconnected >>>> Connection-specific DNS Suffix . : >>>> Description . . . . . . . . . . . : Microsoft ISATAP Adapter >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >>>> DHCP Enabled. . . . . . . . . . . : No >>>> Autoconfiguration Enabled . . . . : Yes >>>> >>>> Tunnel adapter Local Area Connection* 2: >>>> >>>> Media State . . . . . . . . . . . : Media disconnected >>>> Connection-specific DNS Suffix . : >>>> Description . . . . . . . . . . . : Microsoft Tun Miniport >>>> Adapter Physical Address. . . . . . . . . : 02-00-54-55-4E-01 >>>> DHCP Enabled. . . . . . . . . . . : No >>>> Autoconfiguration Enabled . . . . : Yes >>>> >>>> Tunnel adapter Local Area Connection* 9: >>>> >>>> Media State . . . . . . . . . . . : Media disconnected >>>> Connection-specific DNS Suffix . : company.local >>>> Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >>>> DHCP Enabled. . . . . . . . . . . : No >>>> Autoconfiguration Enabled . . . . : Yes >>>> >>>> Tunnel adapter Local Area Connection* 12: >>>> >>>> Media State . . . . . . . . . . . : Media disconnected >>>> Connection-specific DNS Suffix . : >>>> Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 >>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 >>>> DHCP Enabled. . . . . . . . . . . : No >>>> Autoconfiguration Enabled . . . . : Yes >>>> >>>> C:\Windows\system32> >>>> >>>> >>>> Microsoft Windows [Version 6.0.6002] >>>> Copyright (c) 2006 Microsoft Corporation. All rights reserved. >>>> >>>> C:\Users\stuart>net use s: \server12\data >>>> s: has a remembered connection to \\server12\data. Do you >>>> want to overwrite the remembered connection? (Y/N) [Y]: >>>> System error 67 has occurred. >>>> >>>> The network name cannot be found. >>>> >>>> >>>> C:\Users\stuart.>ping server12 >>>> >>>> Pinging server12.company.local [192.168.2.5] with 32 bytes of data: >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=22ms TTL=127 >>>> >>>> Ping statistics for 192.168.2.5: >>>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >>>> Approximate round trip times in milli-seconds: >>>> Minimum = 22ms, Maximum = 23ms, Average = 22ms >>>> >>>> C:\Users\stuart>ping 192.168.2.5 >>>> >>>> Pinging 192.168.2.5 with 32 bytes of data: >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> Reply from 192.168.2.5: bytes=32 time=23ms TTL=127 >>>> >>>> Ping statistics for 192.168.2.5: >>>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >>>> Approximate round trip times in milli-seconds: >>>> Minimum = 23ms, Maximum = 23ms, Average = 23ms >>>> >>>> C:\Users\stuart>net view server12 >>>> Shared resources at server12 >>>> >>>> >>>> Share name Type Used as Comment >>>> >>>> ------------------------------------------------------------------------------- >>>> RedirectedFolders Disk [Offline Share] >>>> The command completed successfully. >>>> >>>> C:\Users\stuart> >>>> >>>> "Bob Lin (MS-MVP)" wrote: >>>> >>>>> Sounds like name resolution issue. Can you ping -a 192.168.2.36? >>>>> Also post >>>>> back the result of VPN client ipconfig /all may help. >>>>> >>>>> -- >>>>> Bob Lin, Microsoft-MVP, MCSE & CNE >>>>> Networking, Internet, Routing, VPN Troubleshooting on >>>>> http://www.ChicagoTech.net >>>>> How to Setup Windows, Network, VPN & Remote Access on >>>>> http://www.HowToNetworking.com >>>>> >>>>> >>>>> "Donny" <> wrote in message >>>>> news:FF5F602D-A4C5-4EAE-AACC-... >>>>>> I am logging in with the Domain username, not the local one. I >>>>>> think that >>>>>> this is a DNS issue but I don't know what I need to do to fix it. >>>>>> Here >>>>>> is >>>>>> some more information: >>>>>> I have some more information on this. After I connect with VPN >>>>>> and i go >>>>>> to >>>>>> Network and Sharing center it says that my network is >>>>>> unathenticated. >>>>>> My >>>>>> VPN >>>>>> IP address is 192.168.2.22 >>>>>> Going on the server 192.168.2.5 I found the following: >>>>>> >>>>>> C:\Users\svradmin>ping adminassist >>>>>> >>>>>> Pinging adminassist.epic.local [192.168.2.36] with 32 bytes of >>>>>> data: Reply from 192.168.2.5: Destination host unreachable. >>>>>> >>>>>> Ping statistics for 192.168.2.36: >>>>>> Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), >>>>>> >>>>>> C:\Users\svradmin>ping 192.168.2.22 >>>>>> >>>>>> Pinging 192.168.2.22 with 32 bytes of data: >>>>>> Reply from 192.168.2.22: bytes=32 time=23ms TTL=128 >>>>>> >>>>>> Ping statistics for 192.168.2.22: >>>>>> Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), >>>>>> Approximate round trip times in milli-seconds: >>>>>> Minimum = 23ms, Maximum = 24ms, Average = 23ms >>>>>> >>>>>> C:\Users\svradmin>tracert 192.168.2.22 >>>>>> >>>>>> Tracing route to ADMINASSIST [192.168.2.22] >>>>>> over a maximum of 30 hops: >>>>>> >>>>>> 1 23 ms 24 ms 24 ms ADMINASSIST [192.168.2.22] >>>>>> >>>>>> Trace complete. >>>>>> >>>>>> C:\Users\svradmin>nslookup adminassist >>>>>> Server: UnKnown >>>>>> Address: fe20::9661:b7f6:e3da:559f >>>>>> >>>>>> Name: adminassist.company.local >>>>>> Address: 192.168.2.36 >>>>>> >>>>>> >>>>>> "Bob Lin (MS-MVP)" wrote: >>>>>> >>>>>>> Do you logon local user or domain user? It could be credentials >>>>>>> issue. >>>>>>> try >>>>>>> net use domainname\username to map the drive. or this search >>>>>>> result may >>>>>>> help. >>>>>>> Can access remote computer via VPN occasionally >>>>>>> However, when the same user access the VPN, he uses cached >>>>>>> credentials >>>>>>> to access the remote computer. The VPN user may lose the cached >>>>>>> credentials >>>>>>> and may ... >>>>>>> www.chicagotech.net/casestudy/vpnaccess1.htm >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Bob Lin, Microsoft-MVP, MCSE & CNE >>>>>>> Networking, Internet, Routing, VPN Troubleshooting on >>>>>>> http://www.ChicagoTech.net >>>>>>> How to Setup Windows, Network, VPN & Remote Access on >>>>>>> http://www.HowToNetworking.com >>>>>>> >>>>>>> >>>>>>> "Donny" <> wrote in message >>>>>>> news:A91805D6-6462-4D13-92FB-... >>>>>>>> I am having problems connecting to Network Shares over VPN >>>>>>>> I am suspecting that this is a network security issue and I am >>>>>>>> very >>>>>>>> weak >>>>>>>> in >>>>>>>> this area. |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Re: problems connecting to Network Shares over VPN | Ace Fekay [MCT] | Windows Small Business Server | 18 | 09-10-2009 04:05 AM |
| Connecting Network Shares Remotely | tkutil | Server Networking | 3 | 05-31-2008 01:41 AM |
| Credentials not remember when connecting to network shares | Deb | Windows Server | 9 | 11-27-2007 11:17 PM |
| problems with connecting my Vista laptop to my network wirelessly | Vesta | Windows Vista Networking | 2 | 06-18-2007 04:07 PM |
| Anyone got problems with x64 connecting to samba shares? | Mark Gillespie | Windows 64 Bit | 1 | 09-03-2006 06:33 AM |
Linear Mode
