Re: Win XP ICS - DHCP just quits working?
Duane Arnold
news:b21825bc.04112...@posting.google.com:
> Hello. Please allow me to ask a question. I am very puzzled. Perhaps
> some of you could shed some light on my current situation.
>
> Scenario: Windows XP Pro with Netgear WG111 USB 2.0 wireless(wifi)
> adapter. Drivers and applications installed from latest zip file from
> netgear (wg111_2_1.zip). Native netgear apps not running at all,
> instead I am using Windows XP's capabilities to manage my wifi network
> which consist of an ad hoc network with desktop as host and a laptop
> as the client. I am using Win XP's Internet Connection Sharing (and
> its DHCP capabilities).
>
> The ad hoc network runs at 11 mpbs (802.11b) and has a wep key.
>
> For 2 weeks everything works fine. Win XP assigns an IP address to the
> laptop everytime it connects to the ad hoc network, and I can use my
> broadband internet connection from my laptop. All is good. Getting
> great range and data transfer rate is great when streaming music from
> the host desktop.
>
> Then for what seems like totally out of the blue, Win XP does NOT
> assign an IP address to my laptop anymore. The laptop connects to the
> ad hoc network, but hangs on 'acquiring IP address' or something like
> that, and finally times out and gets a default IP address. If I run
> ipconfig /renew in a command window on the laptop, I get the message
> that the DHCP server cannot be reached.
>
> Any ideas? Why would Win XP DHCP suddenly stop working after 2 weeks
> or so?
>
> Please note that if I manually assign an IP address to the laptop,
> then all is good again. I can see the host and transfer files etc.
> Since I have other wifi networks at work, I would like to use Win XP's
> DHCP again at home because I do not want to have to assign and
> unassign IP addresses all the time (DHCP at work, then manually at
> home etc.).
I would simply get a wired/wireless NAT router and let it be the gateway
device and the DHCP server for the network and be done with it and forget
about AD-Hoc anything with ICS Windows anything. You'll have less gray
hairs that way. ;-)
It's just a lille advice.
http://www.homenethelp.com/web/explain/about-NAT.asp
Duane :)
Bendit
Thank you in advance. CHEERS!
Airhead
Have you had any virus, spyware or trojans?
"Duane Arnold" <no...@notme.com> wrote in message
news:Xns95B067EDBDA...@63.240.76.16...
Bendit
Thank you for your advice. I am aware of the different hardware components I
could purchase to make my situation better. I would like to stick with ICS
and my USB radio though, as it is cost effective (when it works!) and
reusable (you can just carry the usb thingy everywhere, it's really small
and light). Plus, it is now personal, I must conquer that problem or I will
lose sleep over it!
:)
Thanks again for any input!
Chuck
reverting back to the 4.59 or before version should let your ics work
again. Chuck
Bendit
New outcome: I had reinstalled all the netgear software and
reconfigured 'internet connection sharing' under windows XP pro and
all was good again. The desktop was giving an IP to the laptop, I
could access the web from the laptop, life was good.
Then again, while surfing the web from the laptop, all stopped working
again. I couldn't surf to anything anymore, URLs couldn't get resolved
anymore, I couldn't even PING the host desktop (192.168.0.1)! A
'repair' on the network adapter would once again fail on 'acquiring
network address'. The host computer was hosed again.
I am now forced to use hard coded IP addresses, and I am writing this
message through a remote desktop connection from the laptop to the
desktop (which I guess is way more secured in a way since I have to
authenticate).
(note that the wireless service on that laptop runs fine all day long
at work, without any drops at all)
So that is my story. I am mystified at the ability of my host computer
to work for a while (ICS) and then stop and stay broken for what seems
like no good reason at all.
Again, if you have any insights, I am all ears.
cheers!
Bendit
Progress: ICS worked for a couple of days again. This time it had
functionned properly without re-installing the netgear software. Beats
me. I had placed a support call at netgear just for the heck of it.
They have free 90 day support with a new product. Because both
computers can ping each other if IP addresses are manually configured,
they basically told me to go suck a lemon and call Microsoft (regarding
ICS).
Mark McIntyre
<BenLam...@yahoo.com> wrote:
>they basically told me to go suck a lemon and call Microsoft (regarding
>ICS).
Probably fair enough - its hardly someone else's problem if MS's DHCP
implementation is one lemon short of a G&T. The best solution is to buy a
router or invest in cheap proxying s/w.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>
mediadarling
it's worth a try for you, but i find that xp is usually the issue.
check your firewall settings (if you use xp firewall) as that's where
the issue has been when i'm troubleshooting the office computers.
although after the first few weeks of resetting (yes, on more than one
laptop it took me resetting that several times on each) i no longer
have the issue, but when i do - it is someone's firewall.
--
mediadarling
brought to you by http://www.wifi-forum.com/
Bendit
news:mediadarling.1hmhsa@WiFi-Forum_dot_com...
Thank you for your input. Unfortunately, it is not the firewall, at least
what I can see of the GUI.
Progress report:
I run ICS with a hard coded IP address (and gateway & DNS that points to my
host with ICS) on my client (the laptop). I have been up and running without
any problems. It seems like the DHCP feature of XP Pro with ICS enabled was
the problem for me, it totally breaks my connection.
siddskapoor
Hi
I have the same problem. My desktop has got ICS running on it. My
laptop was working just fine acquiring an IP address through DHCP.
Suddenly out of the blue it just stopped working.
I have two laptops at my home. Both same make and same wireless LAN
card (Intel PRO/Wireless 2200BG). Now one of them is working perfectly
fine acquring IP address through DHCP but in the other laptop the DHCP
client has suddenly quit working. therefore i know the problem is not
with the host.
both the laptops run WinXP SP2 whereas the host is just WinXP. also i
did not install any new software on my laptop so i know the DHCP client
did not quit due to some s/w conflict.
Please help. Also if at least anyone can tell me how to manually
configure my laptop for ICS.
thanks
- Sid
--
siddskapoor
http://forums.speedguide.net
Peter Pan
Cant recall what I did, but it was something to do with the XP SP2 Firewall.
For sure I turned it off to try it, and think I did something with
exceptions.
siddskapoor
My second laptop's DHCP also stopped working today just out of the
blue... no new software installed... nothing...
My first laptop was bought earlier and it stopped working around 10-15
days ago.. the other laptop was bought later and it stopped working
later.
Seems too wierd. Me totally confused.
You say you had something to do with firewalls.. Was it the host
machine firewall or the client firewall ?
On the host machine i have two Network cards. The first one connects me
to my ISP and its firewalled (it connects to the internet and is
shared). the second one is a wireless one and it is automatically
assigned 192.168.0.1 and it is not firewalled. My computer runs a soft
AP and the wirless lan card connects to the wireless network simulated
by the soft AP.
how is your network working right now?
Jeff Liebermann
<siddskapo...@no-mx.earth.universe.org> wrote:
>My second laptop's DHCP also stopped working today just out of the
>blue... no new software installed... nothing...
Well, the usual screwup is that your laptop(s) are associating with
the neighbors access point instead of your own. It's sometimes no
obvious which access point XP is trying to connect. Right click on
the wireless icon in the system tray and force a connection to your
own access point. If that works, set your access point (SSID) to the
"preferred" connection.
If you wanna have some fun, download and install the free DHCP query
tool from:
http://www.weird-solutions.com/download/demo.html
(bottom of list). You don't have to have a connection or IP address
to use it. It will find a suitable DHCP server and query it using
broadcasts. My guess(tm) is that you'll find you're not querying your
own DHCP server, but are connected to the neighbors or something.
>You say you had something to do with firewalls.. Was it the host
>machine firewall or the client firewall ?
Control Panel -> Firewall -> Exceptions tab
See if "File and Print Services" is checked.
--
Jeff Liebermann je...@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558
Peter Pan
>
> You say you had something to do with firewalls.. Was it the host
> machine firewall or the client firewall ?
>
> On the host machine i have two Network cards. The first one connects
> me to my ISP and its firewalled (it connects to the internet and is
> shared). the second one is a wireless one and it is automatically
> assigned 192.168.0.1 and it is not firewalled. My computer runs a soft
> AP and the wirless lan card connects to the wireless network simulated
> by the soft AP.
>
> how is your network working right now?
>
> - Sid
I thought you had said you had XP SP2, which has it's own firewall, and has
a problem with both it and a 3rd party firewall running on the same machine
at the same time (host or client doesn't matter.. does it have a firewall
AND sp2 with a firewall?)
Jeff Liebermann
<Marcs11...@HotmailNOSPAM.com> wrote:
>I thought you had said you had XP SP2, which has it's own firewall, and has
>a problem with both it and a 3rd party firewall running on the same machine
>at the same time (host or client doesn't matter.. does it have a firewall
>AND sp2 with a firewall?)
The XP SP2 firwall is fairly smart. It will detect if there's another
firewall present and automagically disable itself. If ZoneAlarm,
Kerio, Norton Firewall, or McAfee Firewall are present, the XP SP2
firewall turns off.
siddskapoor
network. And my own wireless network (SSID) is already set as
'preferred'.
Does that still mean my laptop may be querying someones else's DHCP
server?
Also a while ago one of my laptops was working perfectly fine while the
other one (same make and config) just beside it was not able to acquire
an IP address through DHCP server. So i dont think the problem is that
there is another wireless network in the vicinity.
I do not have any third party firewall. Just SP2 firewall on laptops
and regular WinXP Pro firewall on host desktop.
The tool you said - could not make it to work. What would be the device
identifier as asked in it??
--
siddskapoor
http://forums.speedguide.net
siddskapoor
I even tried to enable WEP so as to ensure that my laptop is connecting
to just my network. The laptop is still not able to acquire an IP from
the DHCP server on the host. The error message is "Limited or no
connectivity" and the wireless lan card on the laptop gets a default IP
address of 169.254.54.76 with subnet of 255.255.0.0
--
siddskapoor
http://forums.speedguide.net
Duane Arnold
news:1105259394.460e25a2fa0f4e2884514d6583be529b@teranews:
>
> I even tried to enable WEP so as to ensure that my laptop is connecting
> to just my network. The laptop is still not able to acquire an IP from
> the DHCP server on the host. The error message is "Limited or no
> connectivity" and the wireless lan card on the laptop gets a default IP
> address of 169.254.54.76 with subnet of 255.255.0.0
>
>
When the machine gets the 169 IP, it means that the O/S couldn't get an IP
from the DHCP server on the router and the machine timed out on getting an
IP. This is due to some mis-configuration of the wireless NIC or the
router, the NIC could be defective, or the router could be defective.
But I would say it's most likely a mis-configuration issue.
You can try ipconfig /release and ipconfig /renew at the command prompt to
see if the O/S will release the 169 IP and get a valid IP from the router.
If the O/S will not release the 169 IP with the commands above, then you
may have to reset the TCP IP Stack on the machine.
http://support.microsoft.com/kb/299357
You can try the Ipconfig /release and /renew after the TCP/IP reset to see
if the machine will gat an IP from the router.
Duane :)
Jeff Liebermann
<siddskapo...@no-mx.earth.universe.org> wrote:
>My laptop shows just my own wireless network in available wireless
>network. And my own wireless network (SSID) is already set as
>'preferred'.
>Does that still mean my laptop may be querying someones else's DHCP
>server?
No. You have to see the SSID of the access point before it can
deliver an IP address via DHCP. So much for that theory.
>Also a while ago one of my laptops was working perfectly fine while the
>other one (same make and config) just beside it was not able to acquire
>an IP address through DHCP server. So i dont think the problem is that
>there is another wireless network in the vicinity.
Actually, that's exactly the symptoms I would expect from a nearby
access point.
>I do not have any third party firewall. Just SP2 firewall on laptops
>and regular WinXP Pro firewall on host desktop.
Ok. You can have the Windoze firewall fairly badly configured and you
should still get a DHCP IP address from the wireless router.
>The tool you said - could not make it to work. What would be the device
>identifier as asked in it??
No identifier. What you should see is a list of parameters supplied
by your DHCP server. It will have your delivered IP address, the
gateway address, and the DHCP servers in the list, along with some
other junk. However, no easy way to identify the unit except the
magic cookie which methinks is a bit cryptic. If you have two
identically configured wireless routers and both with identical DHCP
configurations, then you would have some difficulty distinguishing
between them. Only the magic cookie will be different. However, in
this case, we have nothing, so the problem is elsewhere.
The 169.254.xxx.xxx address is what Windoze XP assigns as an IP
address when it can't find a DHCP server. This is normal, but it
means that something is broken.
I'm not sure exactly where to start, but methinks reducing the system
to its basic parts and defaults is the best approach. I'm a bit lost
because you didn't start a new message and mixed your system
description with another ICS related issue. It appears that you have
two laptops using Intel PRO/Wireless 2200BG cards. You describe your
system as:
"On the host machine i have two Network cards. The first one
connects me to my ISP and its firewalled (it connects to the
internet and is shared). the second one is a wireless one and it
is automatically assigned 192.168.0.1 and it is not firewalled.
My computer runs a soft AP and the wirless lan card connects
to the wireless network simulated by the soft AP."
Could you disclose?
1. What wireless device is connected to the ICS server?
2. Where does it get its IP address? From the ICS server?
3. Does the unspecified wireless device also have a DHCP server?
Incidentally, I would call it an "ICS server" and not a host.
My guess(tm), is that you have an access point or wireless router
running as an access point connected to the ICS server. That means
that you can just unplug the ethernet cable between the ethernet card
and the wireless device, and connect your laptop directly to the ICS
server. You may need an ethernet hub or switch to get the cable
polarity correct, but it should work without the wireless. If you get
a DHCP assigned IP address, the problem is in the wireless setup. If
you don't get a DHCP assigned IP address, the problem is in your ICS
setup and configuration. My guess(tm) would be the latter.
Editorial remark: ICS sucks. I usually don't bother answering
questions about ICS because it's a mess to troubleshoot and make work
reliably. The only justification for using ICS is when your ISP
forces you to use a USB or PCI DSL or cable modem. Since you have two
ethernet cards, this is obviously not the case. I non-humbly suggest
you invest in a wireless router, which does NAT, DHCP, security, and
all the things ICS is vainly trying to do, remove ICS, and do things
the "right" way (usually my way).
siddskapoor
I will try to explain the exact setup of my network:
My DESKTOP has two lan cards -
one is normal LAN card (UTP cable), lets call its network connection as
"ISP"
the other is wireless lan card, lets call its network connection as
"Wi-Fi"
The ISP connection connects my desktop to the ISP. My ISP provides net
connection through a city wide LAN through UTP cables. The ISP
connection LAN card has got IP and gateway as given to me by my ISP
(manually configured). This connection is firewalled (normal WinXP
firewall not SP2) and is shared for ICS.
The desktop has a Soft AP running with a certain SSID. The Wi-Fi
connection of the desktop connects to this Soft-AP (of desktop).
The Wi-Fi connection has been assigned the IP 192.168.0.1 due to the
ICS.
Now my LAPTOP:
The laptop has just one Wi-Fi Lan card, configured to obtain IP
automatically through DHCP. But its not able to acquire.
I do not have any other hardware like router or hub. I just have
wirless LAN cards and the Soft-AP. I hope the above is clear.
The reason why I am persisting to sove this problem and not buy a
router is cos
1. The current setup was working just fine and beautifully until 15
days ago.
2. I may be switching my ISP and the new ISP is going to give me a DSL
USB modem where i will be forced to use ICS.
I have even tried to reset the TCP/IP stack on the Laptops. Havent been
able to try it on the dekstop yet (cos its not SP2). As a last resort i
may re-install my WindowsXP on the desktop and get the SP2 patch done
on the desktop.
Please help.
--
siddskapoor
http://forums.speedguide.net
Duane Arnold
news:1105298994.b73701f350505f7ac39b7c8606ff1bdb@teranews:
>
> I will try to explain the exact setup of my network:
>
> My DESKTOP has two lan cards -
>
> one is normal LAN card (UTP cable), lets call its network connection as
> "ISP"
That's called the Internet/WAN or public facing network connection.
>
> the other is wireless lan card, lets call its network connection as
> "Wi-Fi"
That's called a LAN or private side facing network connection.
>
> The ISP connection connects my desktop to the ISP. My ISP provides net
> connection through a city wide LAN through UTP cables. The ISP
> connection LAN card has got IP and gateway as given to me by my ISP
> (manually configured). This connection is firewalled (normal WinXP
> firewall not SP2) and is shared for ICS.
>
> The desktop has a Soft AP running with a certain SSID. The Wi-Fi
> connection of the desktop connects to this Soft-AP (of desktop).
> The Wi-Fi connection has been assigned the IP 192.168.0.1 due to the
> ICS.
>
> Now my LAPTOP:
> The laptop has just one Wi-Fi Lan card, configured to obtain IP
> automatically through DHCP. But its not able to acquire.
It seems like some people are trying to do this and have nothing but
problems.
>
> I do not have any other hardware like router or hub. I just have
> wirless LAN cards and the Soft-AP. I hope the above is clear.
>
> The reason why I am persisting to sove this problem and not buy a
> router is cos
> 1. The current setup was working just fine and beautifully until 15
> days ago.
> 2. I may be switching my ISP and the new ISP is going to give me a DSL
> USB modem where i will be forced to use ICS.
Doesn't the ISP provide DSL RJ45 jack modems? And besides there is
nothing stopping you from buy your own DSL modem with a RJ45 connection.
If you buy one, then it should be a brand that's approved to run on the
ISP's network. But by doing this, it forces you to support your setup as
the ISP will not support it.
>
> I have even tried to reset the TCP/IP stack on the Laptops. Havent been
> able to try it on the dekstop yet (cos its not SP2). As a last resort i
> may re-install my WindowsXP on the desktop and get the SP2 patch done
> on the desktop.
>
> Please help.
Your best solution is to get a DSL modem with a RJ45 connection and use a
router if you can and let the router be the gateway device for the WAN
and provide the ICS on the LAN. I have seen a few posts made in various
NG(s) about the problems with ICS and XP even on a wire setup and losing
DHCP on the setup.
Duane :)
Bendit
It seems you have the exact same problem that I have been fighting for
a while. DHCP just quit working after 2 weeks when previously
everything was fine.
I found a "workaround" for the DHCP issue. I have found that if I
hardcode the IP addresses on the laptops, and make the gateway and DNS
addresses on those laptops the IP of the server (the computer running
ICS), all works fine. In other words, ICS works really well, it is the
DHCP part that stops working after a while (hardcoding the IP addresses
on the laptops/clients will make them not use the DHCP features of your
ICS server). Let's illustrate what I mean here:
-Win XP SP2 ICS server has internet connectivity which is shared and
firewalled. The IP address of the wireless adapter on there is
192.168.0.1 with a subnet of 255.255.255.0.
-My Win XP SP2 laptop wireless adapter has a hardcoded IP address of
192.168.0.2, a gateway of 192.168.0.1 and a primary DNS of 192.168.0.1
also. The subnet is 255.255.255.0 (same as ICS server).
The nice part about the wireless adapter is that the IP address changes
can be done on the fly without rebooting. So once you hit the close
button on the properties page, changes should kick in right away. Now
start a browser and you should be good to go.
Let me know how that goes. CHEERS!
Ben
lucaspaciolu2
which is the diference between ap and router wireless?
regards,
--
lucaspaciolu2
Daniel Bennett
> which is the diference between ap and router wireless?
>
> regards,
>
>
An access point provides wireless access to an existing wired network,
or just the hub for a wireless network. A wireless router may well also
provided wireless access, but is used to provide a connection between
two networks.
http://www.ezlan.net/APvsRoute.html
http://asia.cnet.com/reviews/hardware/networking/0,39001739,39115106,00.htm
Its far better explained in these two.
Daniel
Jeff Liebermann
<lucaspaciolu2.1j873n@WiFi-Forum_dot_com> wrote:
>which is the diference between ap and router wireless?
Ask and ye shall receive. Ask harder and thou might transmit.
- ALL of the radios (wireless) are bridges of one form or other.
- Bridges work on Layer 2, the MAC address layer. The decision as to
whether to cross the wireless bridge is based upon the destination MAC
address. If the destination MAC address is across the bridge, it will
transmit the packet. If the destination is NOT across the bridge, the
transmitter remains silent. Packets with no destination MAC address
(broadcasts, ARP requests) always are sent across the bridge.
- Bridges know nothing about IP addresses, routing, the internet, or
other Layer 3 features.
- An access point is a wireless bridge, used in infrastructure mode,
to orchestrate a wireless network of wireless bridge clients (usually
laptops). The bridging is between a wireless network and a wired
ethernet network.
- A switch is a bridge with more than 2 ports. There is a class of
wireless switches, where all the brains are in the central switch
instead of at the radios.
- 802.11 is essentially an encapsulation protocol. I gift wraps 802.3
ethernet packets, delivers them through the air to another 802.11
bridge, which removes the gift wrapping, and delivers the 802.3
ethernet frames intact.
- Client devices are single port bridges. They can bridge exactly one
MAC address (at a time).
- Workgroup bridges and some "game adapters" are ethernet connected
client bridges that can talk to an access point and bridge more than
one MAC address. These are necessary if you're connecting more than
one computah via a single wireless link, to an access point.
- Routers are Layer 3 devices and work with IP addresses. They glue
together two networks. In most cases, the routers glue together your
LAN (local area network) to a WAN (wide area network) also known as
the internet.
- Packets are transmitted on the basis of a rule set known as the
routing table. In most cases, the rules are simple. Everything on
your LAN's Class C IP block (192.168.1.xxx) stays local and does not
get routed to the internet. Everything else goes via the default
gateway to the internet.
- A wireless router is nothing more than a wireless access point with
the LAN port of an ethernet router connected to the access point.
Essentially, they are two devices, with different functions, in one
box. This is why you can turn a wireless router into an access point
by merely ignoring the WAN port (and turning off the DHCP server).
- Access points and routers also offer filtering. Access points
filter by MAC address. Routers filter by IP address. Neither filter
has anything to do with routing.
So, what did I leave out?