Sharing EVDO with ICS on XP Pro

Walter · EVDO Junkie Joined: 14 Sep 2005 Posts: 307

No, it shouldn't be this hard, but unfortunately sometimes it is. Mad

For now, ignore the 98 machine. If you can't get the XP client to get access, you have almost no chance of getting the 98 machine to.

1st thing to try is to go back to the Network Connections window on the XP client. right click on the LAN connection icon (probably is named Local Area Connection), and click on Repair on the context menu that pops up. This will reset a few things and then put out a DHCP request again to try to get an IP address from your server. If it gets an IP address, Repair will finish relatively quickly. If it can't get one, it'll take a bit longer because it will wait a fair bit before timing out.

If this doesn't work, the next thing I'd try is to manually set the IP address on your XP client. Right click on the LAN connection icon again and select Properties this time. This will open a window that includes an area marked "This connection uses the following items:" From this list, highlight Internet Protocol (TCP/IP) and click the Properties button just below the list. This brings up another window where you can manually set the computer's IP address. Click the "Use the following IP address" button and set as follows:

IP Adderss 192.168.0.100
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1

Preferred DNS Server 192.168.0.1
Don't worry about the Secondary DNS server setting. Just leave it blank.

Then click OK on the window and any remaining windows left in the chain. Highlight the LAN icon in the Network Connections again and verify that the settings listed under Details match what you filled in.

If this doesn't work, the first thing to test is whether you can ping your server. Run a command window (DOS window) and type:

ping 192.168.0.1

If things are working OK, you should get something like the following in response:

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128
Reply from 192.168.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

If things are NOT working OK, you should get something like the following in response (after a fair bit of time):

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Let me know how you make out. If this doesn't work, I have a couple of other things for you to try. Good luck.
_________________
Reach, Connect, Celebrate, Grow, Serve.

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

Hi Walter,

Thank you for all the information. I got in late tonght and won'yt have time to do battle. I will try and get back a bit earlier tomorrow and have a good go at this network. I should have some more information then

Here is a little extra info from my first attempt that I didn't post yesterday.

The two xp machines saw the file sharing network and the files with each other but no 98 machine. The 98 machine saw a network but it was the only machine on the network.

The xp client machine did have the LAN repair option and I did try that but it came back with a failed message. So as you say I should try a manual setup tomorrow.

Thanks for all your help. I will give your suggestions a try tomorrow

Mark

bcbradford · Posted: Tue Sep 27, 2005 8:51 pm Post subject:

I had to smile when I saw the initial post in this thread because I spent the better part of the weekend on a similar problem. I, too, have a functioning LAN with three XP machines. On is in the router by Ethernet while the other two are on a wi-fi connection and the router is the gateway.
The reason I said I smiled is because I also tried putting a 2 on the end of the current network name and had the same result. I am running XP Home.
I don't know the reason, but I agree with Walter that running two networks
on the same machines may not work. My problem now is fuguring how to get the old network off the machines.
But, based on Walter's excellent suggestion about what is setting the IP address, I am going to try that when I get back home.
This is a great thread...I am learning a ton.
Bill

brendanhoar · EVDO Heavy User Joined: 09 Jun 2005 Posts: 140

I had a similar problem. I ended up using the network setup wizard under XP and it sorted itself out. Who knows why?

-brendan

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

Hi Bill,

Before I found this forum I posted some of my questions on a general xp bulletin board and I had a similar problem with the Workgroup_02 that I had created. The answer to my question about removing workgroups was that you couldn't remove it but that it would eventually disappear. In fact it did go away of it's own accord in the end. Here is my posting.

http://discussions.virtualdr.com/showthread.php?t=194432

Brendan - I am holding the wizard in reserve. I like to do things manually. That way I can undo what was done but I may end up using the wizard. Walter has given me quite a few things to try.

I am interested in learning a lot more about networking so this is good experience.

Mark

ralphie · EVDO Newbie Joined: 06 Sep 2005 Posts: 4

There are alternative proxies for the windows environment that will not interfere with local workgroups. One that many use is freeproxy . Freeproxy has its own downside in that the ports required for client programs (media player, quicktime, ftp, etc.) have to be specified in the freeproxy setup, but 80% of browser use can be supported simply by specifying the standard http port of 8080.

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

Hi Walter,

I set up the client as you said. I did it manually and it seems to like the connection but still no internet. I tried to ping the host and it timed out with the error message that you describe.

I looked at the LAN connection on the host computer and it says limited connection. I tried to do the repair on it but it failed. Do I have to set this one up manually too. What would be the setting for the host computer? It gets more complicated because it has the EVDO modem and the LAN. I am sharing the EVDO connection.

thanks Mark

Walter · EVDO Junkie Joined: 14 Sep 2005 Posts: 307

What are the IP settings reading on the host computer (the one with the EVDO modem)? It should be:

IP Address 192.168.0.1
Subnet Mask 255.255.255.0
Manually Configured

but the limited connection indicator and the ping timeout implies something is messed up on it. I would suggest rerunning the network setup wizard on your host machine again and see if this corrects it. If this does not correct it, I would suggest the following (I posted this on another similar thread, so I'm going to just cut and paste it):

<start paste from other thread>
I've got one suggestion to try. Since I've set up my V620 and shared via ICS, I have encountered a couple of times when the connection sharing just flat stopped working: with absolutely no changes made. The 2 or 3 times this has happened, all the setup information still looked correct. ICS is on, the clients are set to connect via another computer or gateway, each client has a good DHCP assigned IP address, all other network stuff (file and printer sharing) still works, etc. Just no Internet Connection sharing. Even if I log onto my server and manually connect to the internet, the clients still don't see it.

The only way I've been able to clear this situation is to delete the Ethernet adapter from Device Manager on the server (the one with the V620), reboot, let Windows auto-detect and re-install the Ethernet card driver, and then re-run the Network Setup Wizard on the server to share the connection. So far this has worked each time the connection sharing has been lost.
<end paste from other thread>
_________________
Reach, Connect, Celebrate, Grow, Serve.

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

I will give the wizard a try. I think that when I set it all up initially I just configured everything manually - I was trying to share files and it all worked so I never went any further. I will give your suggestions a go and let you know what happens. Thanks for your help.

I am hoping that the Kyocera EVDO router will be here soon. Not sure if it would make this setup any easier.

Mark

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

Something that confuses me is why the file sharing is working but I cannot ping. Do they work differently. I though that the file sharing was working via TCIP.

Mark

Walter · EVDO Junkie Joined: 14 Sep 2005 Posts: 307

Yes, file sharing works (usually) independently of ICS and ping. ICS and ping (plus a slew of other things) need TCP/IP to be working. Usually file sharing only needs Netbios to be working (although IIRC, there is a way to get Netbios to work over TCP, hence the "usually" comment). If your host and client computer do not have their IP addresses set correctly, ICS and even ping will not work; even while file sharing does. HTH
_________________
Reach, Connect, Celebrate, Grow, Serve.

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

OK when I trried to set the host LAN connection with

IP Address 192.168.0.1
Subnet Mask 255.255.255.0
Manually Configured

and nothing in the DNS - should that be manually configured, auto or left empty?

I got the error message saying that the ip address 192.168.0.1 was assigned to the Broadcom 54G MaxPerformance 802.11g on this computer.

That is the Kyocera card I believe. This is where I get really confused. Who is talking on the LAN, the LAN card or the EVDO card and what should I put on the LAN idf the EVDO card has it's ip address. Shou;d the EVDO card have a different address or any address come to that?

thanks Mark

Walter · EVDO Junkie Joined: 14 Sep 2005 Posts: 307

OK, the settings look OK on your host. You shouldn't need to worry about the DNS settings, your Host computer *is* the DNS server for your client machine and your host will get the IP address of its DNS server whenever it connects via the EVDO modem.

Now the error message is very interesting and is probably the cause of your problems. It's telling you that something else on your network already has that address (or at least Windows *thinks* there is). This is *not* the EVDO card. As far as Windows is concerned, your EVDO card is just another modem Might as well be an old analog modem as far as it cares. It does not have an IP address associated with it (not directly at least).

Much more likely is that the Linksys router you used to have connected uses a Broadcom chipset. I think Windows still thinks it's connected. I assume it is disconnected and unpowered right now, correct?. If it is not, do so.

This sounds similar to the problem I had getting everything working the first time. My server used to get its IP address from my wired router. Then when I disconnected it and switched to using ICS, my server sometimes would still try to obtain an IP address from a DHCP server: even with ICS on so that it should be the DHCP server.

At this point I would go through the steps I outlined before about deleting the Ethernet card driver from Windows, re-booting, letting it re-install the driver, then re-running the Network Setup Wizard. This *should* remove any lingering traces of your previous Linksys router setup. I think this may be your best bet right now. Good luck.

Walter
_________________
Reach, Connect, Celebrate, Grow, Serve.

boater805 · Posted: Thu Sep 29, 2005 5:35 pm Post subject:

Markgc · EVDO Heavy User Joined: 14 Sep 2005 Posts: 107

I do have wifi built in to this laptop although I am not using it. Also for that experiment I was still running gthrough the Linksys router because it enable me to still file sharing with the 98 machine. I will remove the Linksys router from the room and unpower it. The Linksys router also has a built in wireless connection. As far as I know none of the wirless systems are active. To turn on the Linksy wirelss you have to access the Linksys router with a browser and as I said that function has never worked. I wonder if the built in wireless in the laptop is causing problems. I will try again with just the switch on and in the room and then we will know

Mark