ryank85
asked on
VPN Connection successful, but no LAN access
Hi,
We have a couple of cloud servers which we use to VPN in to and share files/folders.
Both are hosted with the same company, both are setup using routing and remote access using PPTP. One server is working, the other is connecting but we have no LAN access.
The IP addresses used on both servers are public WAN IPs, and they are connected directly to the internet rather than being on a private network using a gateway. So for the working server we configured a range of IPs to be given out under RRAS - Right click Server name - Properties - IPV4 - Static Address Pool. When we connect the VPN, it assigns an IP from the range we set here, and we can then access the server shares using \\IPADDRESS.
We have done exactly the same on the second server. When we connect this VPN it assigns an IP from the set range, we can ping the server IP no problem however when trying to access the shares it cannot see the server. I have tried the \\IPADDRESS and also \\SERVERNAME.
I have tried disabling the firewall to make sure nothing on here is blocking the connection, and it had the same issue.
Both servers are running Windows 2012 R2 Standard, but for some reason I have an extra tab in RRAS on the non working server under IPV4 called IGMP? I am not sure what this is used for but it isnt visible on the working server.
Any suggestions?
We have a couple of cloud servers which we use to VPN in to and share files/folders.
Both are hosted with the same company, both are setup using routing and remote access using PPTP. One server is working, the other is connecting but we have no LAN access.
The IP addresses used on both servers are public WAN IPs, and they are connected directly to the internet rather than being on a private network using a gateway. So for the working server we configured a range of IPs to be given out under RRAS - Right click Server name - Properties - IPV4 - Static Address Pool. When we connect the VPN, it assigns an IP from the range we set here, and we can then access the server shares using \\IPADDRESS.
We have done exactly the same on the second server. When we connect this VPN it assigns an IP from the set range, we can ping the server IP no problem however when trying to access the shares it cannot see the server. I have tried the \\IPADDRESS and also \\SERVERNAME.
I have tried disabling the firewall to make sure nothing on here is blocking the connection, and it had the same issue.
Both servers are running Windows 2012 R2 Standard, but for some reason I have an extra tab in RRAS on the non working server under IPV4 called IGMP? I am not sure what this is used for but it isnt visible on the working server.
Any suggestions?
ASKER
IGMP has not been configured previously, we installed RRAS fresh yesterday. None of our other servers currently use this feature.
Checked the sharing options, NetBios over IP, Computer Browser Service running, and all permissions.
I changed the range on RRAS to give out 192.168.5.10-192.168.5.15. When I connect it gives me the ip address ending in .11 and I can see that it gives the server 192.168.5.10. I can ping this, and even RDP in to the server on this IP address but if I try to browse to \\SERVERNAME or \\192.168.5.10 it tells me it cannot connect.
Checked the sharing options, NetBios over IP, Computer Browser Service running, and all permissions.
I changed the range on RRAS to give out 192.168.5.10-192.168.5.15.
Can you see the shares using \\ipaddress directly on the box itself... What about if you temporarily turn off Windows firewall or any other firewalls?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Could be firewall blocking LAN access
ASKER
Assistance no longer needed.
It maybe time to upgrading your network core to a switch that is Multicast aware.
If not needed just delete it.
What is IGMP Querying and IGMP Snooping and why would I need it on my network?
Explained at Wiki
IGMP snooping - Wikipedia
https://en.wikipedia.org/wiki/IGMP_snooping
IGMP snooping is the process of listening to Internet Group Management Protocol (IGMP) network traffic. The feature allows a network switch to listen in on the IGMP conversation between hosts and routers. By listening to these conversations the switch maintains a map of which links need which IP multicast streams
IPV4 may need to be changed to ipv6
Try using the cmd prompt netstat
ipconfig /all
ipconfig /renew
Insure please that all the right sharing options are enabled.