[markwalk]

So, I'm trying to set up a LAN to share my wi-fi internet from my laptop (OS: Vista Home Basic) to my desktop (OS: XP Pro SP2). Everything seems alright, I'm using a hub to link the two computers via ethernet, I activated ICS in laptop's Wireless Connection, its Local Connection automatically fixed its own ip as 192.168.0.1 to act as gateway, and then I configured the desktop's Local Connection to match that gateway ("Use the following IP:" IP Address: 192.168.0.112 / Mask: 255.255.255.0 / Gateway: 192.168.0.1 | "Use the following DNS:" Primary DNS Server: 192.168.0.1). The desktop even shows an "Internet Gateway" under Network Connections when it's all done, saying "Wireless connection in LAPTOP - Connected".

The only downer is that, when all these things are set up and everything seems to be fine, both computers have zero connectivity. I can't ping, can't browse.. Sometimes in the laptop's Network Connections, both the wireless and the local connection Connectivity show as "Local access only", but other times the wireless even says "Local and Internet Access" (while the local says nothing, and its status is just "Active" instead of [un]identified), but still, the effective connectivity keeps being unexistent.

The only way to make laptop's connection work again after that is disabling local connection and/or disabling ICS.

Any ideas on what might be causing this?

Thanks in advance.

[jmwills]

Save yourself a lot of grief and but a wireless card for the XP desktop.

[dlsayremn]

ICS is for sharing a a connection by directly connecting (no hub) the computers using a crossover cable. Crossover and standard ethernet cables are wired differently, so standard ethernet cables will not work for ICS.
Exception: Some newer ethenet cards have an Autosensing function that will actually switch the pin wiring on the card so that a standard cable can be used.


You may want ot check post #2 by JohnWill in this thread. Directs you t tutorial for setting up ICS.

http://forums.techguy.org/networking...onnection.html

[markwalk]

I've read the whole thing about setting up ICS, besides the fact that it's written about XP (I'm trying to set it up on a Vista's platform). The weird thing is: back when my newtork was a wired one, everything worked okay, I shared the XP Desktop's connection via hub with no problem (hub having the XP's ethernet, laptop's ethernet and the dsl modem's ethernet plugged in). I could even (despite the fact that this seems odd) 'dial' the dsl connection on both computers simultaneously.

Is it regular for older ethernet cards (without this Autosensing feature) to estabilish a LAN via direct connecting using a non-crossover cable? 'Cause that was always the case here.

Well then, I guess anyway I'm gonna buy a crossover cable to give it a shot. Any other news I'll post here. If anything else doesn't work, I'm gonna take jmwills advice.

Best regards for all of you.

[TerryNet]

Either a cross-over cable between two computers (unless one has auto-sensing port) or else connect them each by regular cable to hub or switch. I doubt your cabling is the issue here, but it's hard to tell until you get some (any) communication between the computers.

It's better to just use dynamic addressing on the client (desktop), but assigning the IP configuration manually usually works.

Your inability to ping is probably one or more firewalls, probably non-Windows firewall(s).

[markwalk]

I don't know if I expressed this correctly, but just to clarify: the computers do have perfect communication among themselves; I have file sharing activated in both of them, and one can ping the other and I can access the desktop easily through LAN. I just can't ping websites.

Originally Posted by TerryNet

or else connect them each by regular cable to hub or switch.

That's exactly what I've done.

I'll try disabling every firewall I can find, and the antivirus, and see if there are any changes.

[TerryNet]

Disabling a firewall often doesn't give the desired result. Some non-Windows firewalls have a specific setting to allow or not allow internet access through them (in other words, they need to know that ICS is OK).

So, if I now understand correctly on your client machine

ping 192.168.0.1 works fine, but

ping 206.190.60.37 fails (this is yahoo.com). Right? And pinging your router from the client also fails?

[markwalk]

That's exactly that. I can ping one another, but I can't ping any internet site nor browse (this happening both in the cliend AND in the server).
If you mean the wireless router, I'm not sure of its IP, since it's not really mine, it's installed in this building. So I haven't tried pinging it from the client, as of yet.

>> Trying to look up the router's IP, in the IPCONFIG the Wireless Network Connection names its Standard Gateway as 192.168.0.1. I then tried accessing that IP via Internet Explorer and a popup emerges saying ""The server 192.168.0.1 at DI-624 requires a username and a password." and asking for it. Is that the router's IP? If so, could there be a conflict between my server lan ip and the router's wlan one, from the client "POV" thus causing the network to not work properly?

[TerryNet]

Yep. Since (I assume) you can do nothing about the router (i.e., change the subnet to something other than 192.168.0.x) you cannot use ICS. Disable it.

Then make sure the ethernet connections in server and client are set for dynamic addressing. Then in the server in Network Connections bridge your wireless and ethernet. With luck you'll be able to mark this "Solved."

If not successful tell us any error indication and please show the following for when you have the bridge connected and for the same PC w/o the bridge ...

Start, Run, CMD, OK to open a command prompt:
(For Vista type CMD in the Search box after Start)

Type the following command:

IPCONFIG /ALL

[Note that there is no space between the slash and ALL.]

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

If necessary use a text file and removable media to copy the results to a computer with internet access.

[markwalk]

First of all, I'd like to thank you very much TerryNet, for it did really work after activating the bridge. Now everything is functional, from the LAN/filesharing to the internet browsing in both server and client.

Just to comply with your last request, I'll be posting the IPCONFIG /all of the server prior to and post bridging. Took me awhile to translate it, since my OS system language is not english (perhaps it'd been easier to change the language before ipconfiging.. oh well), but here you go:

Laptop/Server IPCONFIG Non-bridged

Windows IP Configuration

Host Name. . . . . . . . . . . . . : Walker
Primary DNS Suffix . . . . . . . . :
Node Type. . . . . . . . . . . . . : Hybrid
IP Routing Enabled . . . . . . . . : No
WINS Proxy Enabled . . . . . . . . : No

Wireless adapter Wireless Connection:

Connection-specific DNS Suffix. . . . :
Description . . . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . . . : 00-1C-BF-90-41-2A
DHCP Enabled. . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . . : Yes
Local-link IPv6 Address . . . . . . . : fe80::4d0a:24eb:9793:8d5f%10(Preferential)
IPv4 Address . . . . . . . . . . . . : 192.168.0.111(Preferential)
Subnet Mask . . . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . . . : terça-feira, 10 de março de 2009 03:04:38
Lease Expires . . . . . . . . . . . . : terça-feira, 17 de março de 2009 12:50:40
Default Gateway . . . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . . . : 167779519
DNS Servers . . . . . . . . . . . . . : 192.168.0.1
Tcpip NetBIOS . . . . . . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix. . . . :
Description . . . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
Physical Address. . . . . . . . . . . : 00-1C-23-FF-06-CA
DHCP Enabled. . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . . : Yes
Local-link IPv6 Address . . . . . . . : fe80::499f:387d:ed1a:736b%9(Preferential)
Autoconfiguration IPv4 Address . . . : 169.254.115.107(Preferential)
Subnet Mask . . . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . . . : 201333795
DHCPv6 Client DUID. . . . . . . . . . : 00-01-00-01-0F-48-A7-DE-00-1C-23-FF-06-CA
DNS Servers . . . . . . . . . . . . . : fe80::499f:387d:ed1a:736b%9
Tcpip NetBIOS . . . . . . . . . . . . : Enabled


Tunnel adapter Local Area Connection*:

Media State. . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address . . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Media State. . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : 6TO4 Adapter
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes
Local-link IPv6 Address. . . . . . : fe80::5efe:192.168.0.111%18(Preferential)
Default Gateway. . . . . . . . . . :
DNS Servers. . . . . . . . . . . . : 192.168.0.1
Tcpip NetBIOS. . . . . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Media State. . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : isatap.{C6769F8B-CC14-4FF5-93C6-F50F7F764633}
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes
Local-link IPv6 Address. . . . . . : fe80::5efe:169.254.115.107%20(Preferential)
Default Gateway. . . . . . . . . . :
DNS Servers. . . . . . . . . . . . : fe80::499f:387d:ed1a:736b%9
Tcpip NetBIOS. . . . . . . . . . . : Disabled

--//--


Laptop/Server IPCONFIG Bridged

Windows IP Configuration

Host Name. . . . . . . . . . . . . : Walker
Primary DNS Suffix . . . . . . . . :
Node Type. . . . . . . . . . . . . : Hybrid
IP Routing Enabled . . . . . . . . : No
WINS Proxy Enabled . . . . . . . . : No

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix. . . . :
Description . . . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . . . : 02-1C-BF-90-41-2A
Physical Address. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . . : Yes
Local-link IPv6 Address . . . . . . . : fe80::b159:d66c:678f:81ca%21(Preferential)
IPv4 Address . . . . . . . . . . . . : 192.168.0.101(Preferential)
Subnet Mask . . . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . . . : terça-feira, 10 de março de 2009 17:24:48
Lease Expires . . . . . . . . . . . . : terça-feira, 17 de março de 2009 17:24:48
Default Gateway . . . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . . . : 352459967
DNS Servers . . . . . . . . . . . . . : 192.168.0.1
Tcpip NetBIOS . . . . . . . . . . . . : Habilitado

Tunnel adapter Local Area Connection*:

Media State. . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address . . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes
Local-link IPv6 Address. . . . . . : fe80::5efe:192.168.0.101%13(Preferential)
Default Gateway. . . . . . . . . . :
DNS Servers. . . . . . . . . . . . : 192.168.0.1
Tcpip NetBIOS. . . . . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Media State. . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description. . . . . . . . . . . . : isatap.{C6769F8B-CC14-4FF5-93C6-F50F7F764633}
Physical Address . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . : No
Autoconfiguration Enabled. . . . . : Yes

Thanks again for everyone that helped, and my best regards to all of you.

[JohnWill]

You can mark your own threads solved using the button at the top of the first page of the thread in the upper left corner.©

[TerryNet]

Good! I'm glad that's working. For future reference, we can usually read ipconfigs pretty well in any language. The numbers are the same, and most of the words we can guess from the placement. Sometimes we have to ask for certain words or phrases though.