I have no problem with a cat-5 connection. The wireless connection
is a different story. Sometimes it works, sometimes it doesn't.
Personally, I think the wLan Monitor widget requires something that
I don't have set correctly.
My network is mostly static ip. I've set the TP up as static.
I've also set the wLan monitor to deactivate radio on startup and I
start it manually. This is because one time I had the cat 5
attached and turned on wireless (enabled radio) and it locked the
system. So I've been careful to not have a connection active while
another one is active.
With wireless I can ping my internal network but not outside. I do
have the gateway defined in the wLan setup. My resolv2 file has 3
dns addresses, the first one I use is 1.1.1.1 and the other 2 or my
isp dns. Of course, this resolv2 file is the same one used by the
wired nic and works fine.
Yesterday I had no problem with wireless internet access. The only
thing that changed is that I powered down last night. This morning
I had to power off 3x on bootup before the boot would finish (it's
been like this ever since I activated psd /smp).
Today I made a change to the wLan DNS setup, toggling it on and
setting it to 1.1.1.1. After that I was able to connect perfectly
fine. This is odd because it is the first entry into my original
resolv2 file. Unfortunately, this setting overwrites resolv2 even
though the help says it sets Hosts in %etc%. I already have the
above in my Hosts file anyway. As far as I can tell the only thing
setting dns in wLan does is rewrite my resolve file be deleting
everything after the 2nd line in the file. Could it be that more
than one ip in the resolv2 file confuses wLan?
I'd rather maintain the resolv2 file as it originally was. I don't
even know why 1.1.1.1 works.
My problem is further compounded by lockups on bootup & by eCenter
whenever I've been toggling the wireless on/off. I may just start
over again & reinstall the whole thing.
listeye geri dön