Re: ICS, wireless, Access point problems...big time

Try:

1. Disconnect the NetGear and/or new Linksys device and manually configure
TCP/IP on the problem machine:

Right click on the Local Area Connection (you may have several of these -
make sure you choose the LAC for the present adapter) and select Properties,
highlight TCP/IP and click the Properties button. Enter these settings:

IP address 192.168.0.250 (or some other non-conflicting
192.168.0.x address)
Subnet mask 255.255.255.0
Default Gateway 192.168.0.1
Preferred DNS 192.168.0.1

Reboot and run ipconfig /all to see if these settings are retained.

2. Possibly the problem machine has suffered a coincidental corruption of
TCP/IP. You could try Start/Run cmd ENTER and run 'netsh winsock reset
catalog' or try one of the winsock fixes:

http://www.cexx.org/lspfix.htm
http://www.tacktech.com/display.cfm?ttid=257
http://www.spychecker.com/program/winsockxpfix.html

Doug Sherman
MCSE, MCSA, MCP+I, MVP

<HLAMUTHNOSPAM@xxxxxxxxxxxxx> wrote in message
news:1balm1dasmm6mmnfpa2ub628cel0j5fet9@xxxxxxxxxx
> Well, it gets worse and worse. I replaced the wireless Netgear router
> with a wireless linksys router with more horsepower...taking your
> advice to go back to go.. However, the PC I was trying to use to set
> up the original netgear has gotten screwed up. Before putting in the
> new Linksys wireless router, I put the old non-wireless router back in
> to make sure everything was working OK. It wasn't...one pc cannot talk
> to the network or get on-ling. I swapped cables, slots, and NICs with
> the same result...it cannot connect to get an IP address...this is
> going back to my orginal and very well functioning non-wireless
> Linksys router used as a hub. When I try to go into the router setup
> from that PC, I get the old Netgear setup and cannot access the
> original Linksys. I am baffelled. This is the only dinged computer and
> it was not the only one I was trying to set up the netgear from. I
> have uninstalled and re-installed stuff and it just keeps getting hung
> up and not being able to get an IP address.
>
> Until I get back to ground zero, I cannot go forward. To top that off,
> it is not clear that the new wireless router can be configured as a
> hub. On-line help isn't very clear on that...since dial up is obsolete
> for all practical purposes.
>
> Any help would be appreciated.
>
> Henry
>
> On Wed, 2 Nov 2005 19:49:57 -0500, "Doug Sherman [MVP]"
> <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Try:
> >
> >1. If the NetGear device is a router, why not simply configure it the
same
> >as the Linksys and get rid of the Linksys altogether?
> >
> >2. If you are going to use both devices plus ICS, then DHCP must be
> >disabled on both devices.
> >
> >3. If you are going to use both devices, then you should connect a
Linksys
> >LAN port to a NetGear LAN (or uplink) port. Do not connect anything to
the
> >NetGear WAN/Internet port. Assign a 192.168.0.x address to the NetGear
> >device.
> >
> >4. Bluetooth adapters frequently have elaborate configuration options -
> >double check your documentation.
> >
> >Doug Sherman
> >MCSE, MCSA, MCP+I, MVP
> >
> ><HLAMUTHNOSPAM@xxxxxxxxxxxxx> wrote in message
> >news:45jim1t44ce8g7q7diu9jocg14ags00b4r@xxxxxxxxxx
> >> Hard problem to describe. Added a new laptop to a home three PC
> >> network using a Linksys router and ICS for my dial up...no real
> >> wireless or cable high speed available. All four use XP Home SP2 OS.
> >> After much coaching from this forum, tweaked settings and all
> >> PCs/Laptop visible to all others. In other words, the network worked
> >> like a charm. Enter wireless.
> >>
> >> Rumor has it that there may be wireless wideband access in the near
> >> future at my location....but, in the meantime, I plan to drink a lot
> >> of coffee at the local WiFi spot. To set the system up, I implemented
> >> a wireless access for the laptop (which has Bluetooth wireless built
> >> in) on my hardwired LAN....or I tried to set it up.
> >>
> >> The wireless link works but the network link has zero signal. Swap out
> >> hard wire, perfect. Go to wireless, link shows with execellent signal,
> >> no thru-put. Ergo, I didn't set the wireless system up. And this is
> >> where I get into problems...I don't know what to set up.
> >>
> >> The ICS NIC uses 192.168.0.1 address and the router was configured as
> >> a hub with address 192.168.0.254 and no DHCP. Each PC/Laptop get IP
> >> address and DNS server addresses automatically and DHCP is enabled. OK
> >> so far. Then I added a wireless router to be configured as a wireless
> >> access point. I have hit a wall, here.
> >>
> >> The Netgear instructions are so barebones as to be useless. I need to
> >> configure this device with its own IP address and wth its DHCP shut
> >> off....but the instructions say to enable the DHCP in my primary
> >> router, which has been shut off. When I enable the DHCP in the primary
> >> router, what do I populate the tables with? Unpopulated, nothing seems
> >> to be affected....but I really don't want to mess with success.
> >>
> >> But, and this is the real problem...I cannot get the access point to
> >> let me connect the laptop to the internet either with the wireless or
> >> hard wired connections. When I stumble onto anything that seems to
> >> work...I get a connections....the thru put is zero. Usually, I cannot
> >> even access the damned router to configure it. I remember the thruput
> >> problem from the past when my corporate IT folks said it was likely a
> >> conflict with the wireless and NIC based connections. I have tried to
> >> eliminate this conflict, but I am not sure how to shut either service
> >> off or on at the laptop.
> >>
> >> What I really want is some step by step steps, such as those available
> >> for setting up the ICS. The equipment sellers want you to buy
> >> expensive integrated all in one systems, but the dial up and ICS
> >> confuse thise whole selection process...and I don't want to invest in
> >> a bunch of equipment that does not work as I need it to.
> >>
> >> Just point me in the right direction. I am bitching to the Netgear
> >> folks, but they have no real support.
> >>
> >> Thanks for the help.
> >>
> >> Henry
> >>
> >>
> >
>


.