Hi, This machine has two NICs, one has a non routable IP for example 192.168.1.1 and all the shares on this machines are accessible through the UNC \\192.168.1.1\sharename The other NIC has a public IP, for example 193.x.x.x. Shares are not accessible through \\193.x.x.x\sharename. I can ping this machine but even on the same machine I can not open any share with public IP. Path not found appears :-( We need to access a Visual Source Safe Database over the Internet through it, it will not work unless this problem is fixed. And Yes I configured VPN (RRAS Service) earlier, that I removed. But still no luck. Kindly help Regards

You really don't need the second NIC with the external IP. Just use the internal NIC and connect the PC to the router. Then set up your VPN.

Hi guapo, Thanks for the reply. What you said is ok, but VPN makes it really slow, we need direct access without VPN.

Is remote desktop any better?

No, we need to access Visual Source Safe (VSS2005) server. So should be connected to it through the VSS client not using Remote desktop.

http://msdn.microsoft.com/en-us/lib... That's the MS site with the setup ^^^ instructions. Here's a quote from the site: "Visual SourceSafe (Internet) plug-in can be configured to access a Visual SourceSafe database either on the same computer where the Visual SourceSafe Web service is running or on another computer. In the latter case, both the Web service computer and the computer that is hosting the database must reside inside the same Windows domain." In other words the remote VSS client and host have to be on the same domain.

rajoo_sh,"we need direct access without VPN." means you are raw on the internet. You are begging to be hacked. Within days you will find your public ip blacklisted due to being a spam relay server. "UNC \\192.168.1.1\sharename" There are two problems here. Unc is \\server name\sharename. It is never \\server name\ip address\sharename \\ipaddress\sharename indicates you do not have the MS DNS server properly configured. You should only be using \\server name\sharename if MS server is setup correctly. For security reasons you should never run web facing software on servers containing internal network information. In other words, the web facing server should be in a DMZ separate from your DC's. It should be a member server. Especially if you are considering direct web based access to this software. I am not familiar with Visual SourceSafe but I suspect, like Exchange, you can have a web facing component that then creates a secure comm link to the database/software on a secure server. Example of Oxymoron: Person who is pro choice and anti sex education. Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.