I have a question about Share an Internet Connection:

Hi, I've been trying to Share my ADSL with my brothers computer. This is my Hardware : - Windows XP Pro in both. - ADSL - 2 Network Cards (1 x 10mb & 1 x 10/100mb) - 8 port 10mb Hub - Asus External Router etc i connect the router to the hub's uplink, and then connect the two other computers to the hub. My computer works fine and can access the net etc, but his computer cannot. We can play Lan games, sharefiles no problem, but he can't get on the net. Any ideas? Thanks alot !~

[Reply or follow-up to this message]

why are you using a hub AND a router.....?
(just curious)

does the router not have enough ports to connect
two computers to.....??
Or is the hub a print server as well.....??

You should only need to connect your ADSL to the
routers WAN port , and then connect the computers
to it as well......

[Reply or follow-up to this message]

Hi, I am not very good with this networking stuff so yeh, Umm my Modem is a ASUS AAM6000EV ADSL Router. here is modems link if it helps :/ http://www.asus.com/communication/adsl/performance_6000ev.htm anywayz I donno only see 1 place to stick in a network cable. So thats why i fort i had to use hub. there is a USB thing there but it is covered or somthing. thanks


On Saturday, August 24, 2002 at 8:48 pm, GM wrote:

>
>why are you using a hub AND a router.....?
>(just curious)
>
>does the router not have enough ports to connect
>two computers to.....??
>Or is the hub a print server as well.....??
>
>You should only need to connect your ADSL to the
>routers WAN port , and then connect the computers
>to it as well......
>

[Reply or follow-up to this message]

go to configuration panel - network - and there someone should be a wizard for setting 
up the network and it makes internet sharable too and puts in a firewall etc.

u can also find it in startmenu - programs - accesoires - communication- wizard set 
network or something like that






On Saturday, August 24, 2002 at 10:00 pm, Kyo wrote:
>Hi, I am not very good with this networking stuff so yeh, Umm my Modem is a  ASUS 
>AAM6000EV ADSL Router. here is modems link if it helps :/
>http://www.asus.com/communication/adsl/performance_6000ev.htm
>anywayz I donno only see 1 place to stick in a network cable. So thats why i fort 
>i had to use hub.
>there is a USB thing there but it is covered or somthing.
>
>thanks
>
>

[Reply or follow-up to this message]

hi, yup i've tried that already, but the other computer still cannot access the internet. Like in my computer it says Adress type : Assigned by DHCP but in the other computer Adress type : Automatic Private Address Does that have anything to do with it?. Thanks once again


On Monday, August 26, 2002 at 2:15 am, PIT wrote:

>go to configuration panel - network - and there someone should be a wizard for setting 
>up the network and it makes internet sharable too and puts in a firewall etc.
>
>u can also find it in startmenu - programs - accesoires - communication- wizard 
set 
>network or something like that
>
>

[Reply or follow-up to this message]

I'm having the exact same problem. My network was working absolutely fine up until a few weeks ago, when I began to be unable to access shared files on the secondary computer from the primary. The internet still worked.

About a week ago, the users of the second computer complained their internet wasn't working either. They received the "Automatic Private Address" in their LAN settings, where I was still getting "Assigned by DHCP".

So now, the home network doesn't work on either computer, and the cable connection doesn't work on the second computer. I've tried just about every trick I could pull out my ass. I'm starting to wonder if my Switch went bad; it's 3 years old, so that's a possibility. But why would it still have no trouble sending data to my computer? This is driving me nuts.

I should note that my configuration is this: Each computer has a 10/100 NIC, the computers run CAT 5 cable to a 10/100 5-port switch, and the switch runs a 10/100 crossover cable to the cable modem. I'm paying for 2 IPs through my Cable provider.

Anybody have any clues out there?


On Monday, August 26, 2002 at 2:21 am, Kyo wrote:
>hi,
>yup i've tried that already, but the other computer still cannot access the internet.
>Like in my computer it says
>Adress type : Assigned by DHCP
>but in the other computer
>Adress type : Automatic Private Address
>
>Does that have anything to do with it?.
>Thanks once again

[Reply or follow-up to this message]

I had the same problem and found the follwing answer: Automatic Private Address Configuration Automatic Private IP Addressing (APIPA) is used to allocate addresses within subnetworks that either do not have a local DHCP server or do not have a routed path to a DHCP server on another subnetwork. By default, a computer running Windows 2000 first tries to contact a DHCP server to obtain an IP address and related configuration information for each installed network connection:
If a DHCP server is reached and the leased configuration is successful, TCP/IP configuration is completed.
If a DHCP server is not reached, the computer instead uses APIPA to automatically configure TCP/IP. When you use APIPA, Windows 2000 determines an address in the reserved IP address range from 169.254.1.1 through 169.254.254.254. This address is used as a temporary IP address configuration until a DHCP server is located. The subnet mask is set to 255.255.0.0. The APIPA range of IP addresses (169.254.0.0/16) has been set aside for use in IP address autoconfiguration by the Internet Assigned Numbers Authority (IANA; www.iana.org/). Any IP addresses within this range are not usable on the Internet. APIPA eliminates IP address configuration for single-network small office or home office networks that are not connected to the Internet. End of quote. So, in a nutshell, all computers must have DHCP enabled (thru TCP\IP protocol) and the one sharing the internet connection must be connected to the internet BEFORE you boot up the other computer(s). To check to see if you have DHCP assignment or APIPA, right click on your local network connection icon in systray, select STATUS, then SUPPORT tab. It will state your address type, either "Automatic Private Address" or "Assigned By DHCP". Two places to go for XP: http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp http://www.microsoft.com/windowsxp/pro/techinfo/administration/homenetbridge/default.asp

[Reply or follow-up to this message]

I installed a Q-Tec Firewire Card, and it changed my settings in Win XP so I couldnt get on the internet. Intranet was still working. (Automatic private address -instead of DHCP) Finally I found all the places in Regedit where there was a Ipautoconfig and I erased the value 162.xxx.xxx.xxx) also the subnetmasks. After a reset all was well again.


On Monday, November 4, 2002 at 4:42 pm, Donny wrote:
>I had the same problem and found the follwing answer:
>
>Automatic Private Address Configuration
>
>Automatic Private IP Addressing (APIPA) is used to allocate addresses within subnetworks
>that either do not have a local DHCP server or do not have a
>routed path to a DHCP server on another subnetwork.
>By default, a computer running Windows 2000 first tries to contact a DHCP server
>to obtain an IP address and related configuration information for each installed
>network connection:
>
>
If a DHCP server is reached and the leased configuration is successful, TCP/IP
>configuration is completed.
>
If a DHCP server is not reached, the computer instead uses APIPA to automatically
>configure TCP/IP.
>
>When you use APIPA, Windows 2000 determines an address in the reserved IP address
>range from
>169.254.1.1 through 169.254.254.254. This address is used as a temporary IP address
>configuration until a DHCP server is located. The subnet mask is set to 255.255.0.0.
>The APIPA range of IP addresses (169.254.0.0/16) has been set aside for use in IP
>address autoconfiguration by the Internet Assigned Numbers Authority (IANA; www.iana.org/).
>Any IP addresses within this range are not usable on the Internet. APIPA eliminates
>IP address configuration for single-network small office or home office networks
>that are not connected to the Internet.
>
>End of quote. So, in a nutshell, all computers must have DHCP enabled (thru TCP\IP
>protocol) and the one sharing the internet connection must be connected to the internet
>BEFORE you boot up the other computer(s). To check to see if you have DHCP assignment
>or APIPA, right click on your local network connection icon in systray, select STATUS,
>then SUPPORT tab. It will state your address type, either "Automatic Private Address"
>or "Assigned By DHCP".
>
>Two places to go for XP:
>
>http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp
>
>http://www.microsoft.com/windowsxp/pro/techinfo/administration/homenetbridge/default.asp

[Reply or follow-up to this message]

I am getting "Automatic Private Address" and not "Assigned By DHCP" as should be the case. Mine is a completely new installation of XP Pro. I've checked and the DHCP is seen as enabled. I followed your way by editing the registry entries and everytime i restarted, the connection if still Automatic Private Address. Anyone can help me please?


On Thursday, November 27, 2003 at 10:36 am, Jan Schønemann wrote:
>I installed a Q-Tec Firewire Card, and it changed my settings in Win XP so I couldnt
>get on the internet. Intranet was still working.
>(Automatic private address -instead of DHCP)
>Finally I found all the places in Regedit where there was a Ipautoconfig and I erased
>the value 162.xxx.xxx.xxx) also the subnetmasks. After a reset all was well again.
>
>

[Reply or follow-up to this message]

I spent days/hours with similar problems.

My router was setup as a default gateway on 10.0.0.2

My two XP Pro machines could handle this address and were assigned DHCP addresses 
between 10.0.0.3 and 10.0.0.14 .

When connecting XP home machines to the network they would get an automatic private 
address assigned with the usualy 168.XXX.XXX.XXX address and no connectivity.

I changed the Router IP/Default gateway to 192.168.0.1 and in seconds everything 
was up.

Make sure your Default Gateway is setup as 192.168.0.1.

[Reply or follow-up to this message]

I had this problem for some time. It fixed when I assigned static IP addresses to all client computers and 192.168.0.1 to my gateway. My network doesn't use DHCP anymore - and now it works.

[Reply or follow-up to this message]

I've been trying to share 2 PCs with 1 cable modem and an 8-port hub for half the day. The primary PC access the Net fine but nothing from the other. IPCONFIG/RENEW doesn't work; manual configs don't work; HOW did you solve yours..please tell me. Thx!


On Saturday, March 27, 2004 at 1:01 pm, randomahhahahah wrote:
>I had this problem for some time. It fixed when I assigned static IP addresses to
>all client computers and 192.168.0.1 to my gateway. My network doesn't use DHCP anymore
>- and now it works.

[Reply or follow-up to this message]

The best advice I found (worked like a charm for the same originally posted problem) is found at the site www.dslreports.com/forum/remark,10779865~mode=flat It says that the winsock sockets are likely corrupt. To diagnose that and to fix that, there is a Microsoft article with some fairly simple steps listed. I did the steps exactly as in the Microsoft document (Method 1 to diagnose, then edited the two registry sections as the fix, restarted, reloaded TCP/IP and restarted again) and suddenly my home network was working again and my step-daughter's Dell laptop was connecting to the internet. The microsoft info is KnowledgeBase article 811259 (go to support.microsoft.com and search). Check it out and good luck!


On Monday, November 4, 2002 at 4:42 pm, Donny wrote:
>I had the same problem and found the follwing answer:
>
>Automatic Private Address Configuration
>
>Automatic Private IP Addressing (APIPA) is used to allocate addresses within subnetworks
>that either do not have a local DHCP server or do not have a
>routed path to a DHCP server on another subnetwork.
>By default, a computer running Windows 2000 first tries to contact a DHCP server
>to obtain an IP address and related configuration information for each installed
>network connection:
>
>
If a DHCP server is reached and the leased configuration is successful, TCP/IP
>configuration is completed.
>
If a DHCP server is not reached, the computer instead uses APIPA to automatically
>configure TCP/IP.
>
>When you use APIPA, Windows 2000 determines an address in the reserved IP address
>range from
>169.254.1.1 through 169.254.254.254. This address is used as a temporary IP address
>configuration until a DHCP server is located. The subnet mask is set to 255.255.0.0.
>The APIPA range of IP addresses (169.254.0.0/16) has been set aside for use in IP
>address autoconfiguration by the Internet Assigned Numbers Authority (IANA; www.iana.org/).
>Any IP addresses within this range are not usable on the Internet. APIPA eliminates
>IP address configuration for single-network small office or home office networks
>that are not connected to the Internet.
>
>End of quote. So, in a nutshell, all computers must have DHCP enabled (thru TCP\IP
>protocol) and the one sharing the internet connection must be connected to the internet
>BEFORE you boot up the other computer(s). To check to see if you have DHCP assignment
>or APIPA, right click on your local network connection icon in systray, select STATUS,
>then SUPPORT tab. It will state your address type, either "Automatic Private Address"
>or "Assigned By DHCP".
>
>Two places to go for XP:
>
>http://www.microsoft.com/windowsxp/expertzone/columns/crawford/02april22.asp
>
>http://www.microsoft.com/windowsxp/pro/techinfo/administration/homenetbridge/default.asp

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum