Just re-install the TCP/IP protocol on the affected PC. ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com http://lists.wispnotes.com/mai
We're using 4.45 on over 600 AP's,RG's,KN-100's,KN-200's... everything is working well. ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.co
Why are you replying to my message? I mentioned nothing about polling or non-polling. ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com
Anyone know if or where the temperature is listed in the MIB tree? _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com http://lists.wispnotes.com/mailman/listin
Configurator 5.00-xxxx is retaining the Public IP Address & Public IP Mask settings when the IP Host is set to "Obtain an IP address from DHCP Server". The easiest way to demonstrate this problem is
What? This has nothing to do with a "Windows ARP cache issue" dude. ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com http://lists.wispn
Ed, Thanks for at least providing confirmation that your engineers acknowledge the problem. Do they have any idea of how to fix the problem? My line of thinking is that if you read a KN's configurati
Is anyone going to take this seriously? Is anyone going to fix this? ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com http://lists.wisp
Hi Ed, The problem that we are having is a real world problem. We first noticed this problem after upgrading our network to v4.45 firmware. Some of our customers turn off their KN-100's when they are
The workaround (outlined on the web site) is to delete the "Public IP Address" and "Public Netmask" fields before saving the configuration. Note: the work-around causes an additional problem (see web
I guess no one reads my posts... On May 20th, I mentioned that v3.20 hardware was the problem with v4.45 firmware. ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailin
Ha - I heard that story back in February 2003 when I visited their office in Milipitas. Makes you wonder... _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com
About 2 months ago (when we first upgraded our customer base to firmware v4.44-02) we had a problem at one of our base stations (KN-200) where we lost the ability to communicate with any of our custo
** REPLY SEPARATOR ** I don't know if other 2.4GHz devices could cause this behaviour or not. I've just made a note that in both cases, there were other 2.4GHz devices present. It doesn't take rocket
The 2 clients that were transmitting garbage could not be reached through the wireless interface (oddly enough). From the base station, we could not see the client in Configurator's "Turbocell Statio
Of course you're going to have nulls! All over the place too, not just the center. That's a whacky setup you've got there... What are you trying to accomplish? ** REPLY SEPARATOR ** _________________
The simple soloution is to use 1 radio per antenna. You can't expect to split a TX signal to 2 antennas and not get nulls everywhere. Think about throwing 2 stones into a pond, the waves created by e
I know exactly what you're talking about, I've experienced this problem several times in the past. I haven't noticed it since our upgrade from 4.31 to 4.44 - we're using 4.45 right now. I'm not sayin
Who is still experiencing this "feature" with v4.45 firmware? ** REPLY SEPARATOR ** _______________________________________________ Karlnet mailing list Karlnet@WISPNotes.com http://lists.wispnotes.c