I have a question regarding Windows XP incoming connections. I have a PC in the office connected to Internet via...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
DSL. The setup is a typical LAN setup of five computers. It is the main gateway hence 192.168.0.1. The other PCs connect to it, which means to say the Internet connection is shared. It has two NICs one connected to DSL modem and the other to the hub in which the other PCs on the LAN connects also the hub.
I created an Incoming Connection icon in Network Connections folder so that I will be able to connect to that PC via dialup from my home laptop. I wonder why I could access the files in the local network but I can't access the Internet. I heard it is possible to share the Internet via remote access as if my PC will act as a mini private ISP dialup server but how come I can access the network and shared files but I can't get out of the LAN going outside the Internet. Is there something missing?
There are a few points we need to check in order to resolve your problem. Logically, your setup is correct and therefore should work, however I am not aware if all Windows XP editions will support what you are trying to achieve.
For example, I am not certain if Windows XP Home edition will allow you to use the PC as a gateway to the Internet in this way. This is something you need to check, before proceeding with the suggestions that follow.
- On your Windows XP workstation (Dialup server) go to your 'Network Connections' area. You should be able to see your incoming dialup connection you have created. Double click on it and go to the 'Networking' tab. From there, double click on the 'Internet Protocol' component and make sure the 'Network Access' section is enabled, allowing callers to access your local area network.
- Enable IP routing. If you are not familiar with the term "IP routing", in plain English it is the ability to 'move' packets from one network to another. For example, consider the following setup:
PC1 belongs to Network1 and PC3 to Network2. PC2 in this case is part of both networks. In order for PC1 to send information to PC3, PC2 must be able to receive the data and forward it to PC3, this can be described with one word – 'route'. Hence IP Routing.
So, coming back to our problem, you need to ensure IP routing is enabled. You can do this by hitting your 'Start' button, go to 'Run' and type 'regedit'. Once the registry editor loads, find your way to the following entry:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip \Parameters
Click on the 'Parameters' folder and check the subkey named "IPEnableRouter". If the 'Data' value is set to zero (0) (this is also the default value), double click on the subkey and change that into a one (1).
Reboot the machine at this point. You have now successfully enabled IP Routing.
- Ensure that your Internet Sharing Connection is enabled by viewing the properties of your network card that connects to your broadband router.
At this point, you can try your dialup connection again, hoping that you will be able to access the Internet.
If the problem persists, then you should point your Web browser to support.microsoft.com and search their database for any known problems related to Remote Access.
Dig Deeper on LANs (Local Area Networks)
Related Q&A from Chris Partsenidis
Learn how to understand the difference between bit rate and baud rate in this expert answer.continue reading
Expert Chris Partsenidis offers guidelines for a smooth and successful PSTN to VoIP migration.continue reading
What SIP trunking basics should you know before you deploy? SIP trunking guru Chris Partsenidis explains what you need to know about SIP trunking ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.