Steven
Fri May 19 16:37:58 CDT 2006
OK. Thanks for the update. A couple more things came to mind. Check the
properties of the wireless network adapter when it is enabled to make sure
that Client for Microsoft Networks is enabled on it and verify with the
command net config workstation. Also run the support tool netdiag on that
computer when it is using the wireless network adapter and compare the
results to what is found when the wired adapter is used. Support tools are
on the install disk in the support/tools folder. If you can ping the servers
with the shares from the wireless adapter then try using telnet on it to see
if it shows the computer has access to TCP ports 139/445 [used for file and
print sharing] on the computer with the share as in telnet xxx.xxx.xxx.xxx
139 using the real IP or name of the computer. If the port is open you will
see a blank command window with a blinking cursor and if not you will get
some sort of error message. If you have never tried telent for that use the
command telent localhost 445 on your computer to see what happens. ---
Steve
"Brad Pears" <donotreply@notreal.com> wrote in message
news:OboOmb4eGHA.4900@TK2MSFTNGP02.phx.gbl...
> Steve, yes this is a wierd one for sure...
>
> I tried accessing the shares using the IP address instead as you suggested
> and I get the same error each time. Basically I get an "unable to find"
> error message. I don;t have his machine here in front of me right now so I
> forget the exact message I am getting bit it's something along those
> lines. When you go to browse the Windows network and then below that - our
> domain (which it does show as it must be cached locally on his machine) ,
> it will not show any machines at all under the domain name. However, plug
> in the ethernet cable, disable the wireless card and presto... everything
> shows up!!! I also tried turning off his firewall - no change. We are not
> using TCP filtering on any of our servers at all. Maybe I should try aa
> static IP addess on his wireless card too. I haven't done that one yet...
>
> I still have to try pinging the machines he is attempting to acccess
> shares on but I know for sure he can talk to the terminal servers because
> that he can do (suing RDP) with his wireless card!! Is that not bizarre??
> It's almost like there is some kind of filtering going on there for sure
> because he communicating on port 3389 no problem but maybe not other ports
> that are required to browse and access a network!!!
>
> I'll keep you posted on further findings!!
>
> Brad
>
> "Steven L Umbach" <n9rou@n0-spam-for-me-comcast.net> wrote in message
> news:55mdnZ4jFImJJPHZ4p2dnA@comcast.com...
>> Can he ping the computers that have the shares he is trying to access by
>> name and IP?? What happens when he tries to access a share - any
>> particular error message such as access denied or not found? It does seem
>> strange in that it works for a wired adapter but not a wireless adapter
>> but verify that the wireless connection is using the same DNS servers and
>> only the same DNS servers [never and ISP DNS server!] as the wired
>> connection which you can do with the command ipconfig /all and have him
>> try accessing a share via IP address instead of name as in
>> \\xxx.xxx.xxx.xxx\share. Is there any IP filtering on the servers with
>> the shares such as Windows Firewall or ipsec policy that only allows
>> access from specific IP addresses that does not include the IP address
>> that his wireless adapter gets? --- Steve
>>
>>
>> "Brad Pears" <donotreply@notreal.com> wrote in message
>> news:enxmn5peGHA.3792@TK2MSFTNGP03.phx.gbl...
>>> Yes, I closely scrutinized his wireless config and it is fine. Signal
>>> strength is great and is connected at 54mbs. He is being assigned an IP
>>> vbia DHCP etc.. no probs. We are using WEP (his NIC does not support
>>> WPA) and he has the correct key entered. The funny thing is he can
>>> access our terminal server via his wireless connection using the Remote
>>> Desktop Protocol and that works just fine!!! It's browsing anything
>>> else on the network or mapping netowrk drives with domain credentials he
>>> is unable to do. I just don't get it. I think I will try a different
>>> wireless card in his machine to see if the issue is somehow related to
>>> his built-in card.
>>>
>>> Any other suggestions?
>>>
>>> Thanks, Brad
>>>
>>> "Steven L Umbach" <n9rou@n0-spam-for-me-comcast.net> wrote in message
>>> news:l7qdnYb1QoM-KfbZnZ2dnUVZ_tednZ2d@comcast.com...
>>>> Is he showing that he is connected to your wireless network and
>>>> receiving it with good signal strength? Use ipconfig /all to see what
>>>> IP address he is getting to make sure it is on your network and not a
>>>> self assigned 169.xxx.xxx.xxx IP address. If it is an IP on your
>>>> network can he ping local host, his own IP, any other IP on the network
>>>> such as the default gateway to establish basic network connectivity or
>>>> not?? I assume you are using WEP or hopefully WPA and if so make sure
>>>> he is using the correct pass key for the wireless network and channel.
>>>> Though the article is a bit outdated for references to SP2 check to see
>>>> if that computer is using Wireless Auto Configuration and that it is
>>>> configured correctly. If it is not using it you may want to try it.
>>>> There is also a Microsoft wireless newsgroup. --- Steve
>>>>
>>>>
http://www.microsoft.com/technet/community/columns/cableguy/cg1102.mspx
>>>>
>>>> "Brad Pears" <donotreply@notreal.com> wrote in message
>>>> news:ej9mS5feGHA.3888@TK2MSFTNGP02.phx.gbl...
>>>>>I have a user with an XP Home sp2 machine of his own he uses here at
>>>>>work. We have a domain here so this user needs to access domain
>>>>>resources. He has a built in wireless card in his Dell laptop. Using
>>>>>the wireless he gets no domain access at all - cannot even map a
>>>>>network drive even when supplying domain credentials. If he disables
>>>>>his wireless card and plugs in using an ethernet cable, everything
>>>>>works just fine. I have tried playing with some of the settings in his
>>>>>wireless card - I do not see anything different in there as compared to
>>>>>other wireless users. There is also a "1394 Connection" when you look
>>>>>at all his network connections - that is enabled. Could it be something
>>>>>to do with this and.. what is this anyway????
>>>>> I tried turning off the firewall, nothing, turned on netbios etc...
>>>>> nothing... I am not sure if maybe this is just an issue with the
>>>>> builkt in wireless period and there is nothing I can do. I have not
>>>>> yet tried another wireless card - but that is next on teh list of
>>>>> to-do's!!!
>>>>>
>>>>> Has anyone ever seen this issue before and if so did you ever find a
>>>>> resolution?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Brad
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>