No Access One-way Shared Files Workgroup

[AnnieMS]

I have a Dell 380 [WinXP Pro SP2] & a Thinkpad X41 tablet [WinXP tab ed SP3] workgrouped using a 2Wiregateway wireless/ethernet router. Both connect wirelessly. I am currently using simple file sharing on both computers. I can access the shared files on the Dell from the Thinkpad but I can't access the shared files on the Thinkpad from the Dell. I get the message "logon failure: the user has not been granted the requested logon type at this computer".

I can successfully ping the Thinkpad from the Dell using its IP address and using the -a option the thinkpad's computer name is displayed.

I have run the network wizard from CP on one and saved the netsetup.exe to disk and then run that on the other [done this several times both ways]. I am using Windows firewall on both computers and both have file sharing as an exception. Both computers have the same workgroup name & SSID. The accounts I'm logged into have the same UN & PW and group type on both computers. The Shared Documents folder on both computers has 'Share this folder on the network' checked.

The adapters on both computers have Client for MS, File&Print Sharing and TCP/IP installed. The Thinkpad also has QoS Packet Scheduler and AEGIS protocol v3.2.0.3 installed.

I have been troubleshooting this off and on for months and have checked registry values for restrictanonymous, hidden & RestrictNullSessAccess per various articles on the thinkpad. I have checked local security policy network access entries on both computers per different articles and am now thoroughly confused.

I have never been able to get from the Dell to the Thinkpad thru My Network Places but at one time I could get from the Dell to the Thinkpad using Run > \\computername\ShareName. However, if I opened a file the connection crashed. I once got the message "not enough server space is available" when trying to connect thru Run. I increased the IPRStackSize in the registry, but shortly after that I had to reformat/reinstall the thinkpad and I don't know if it made any difference. After reformat/reinstall the IPRStackSize DWORD wasn't present in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters so I added it w/ a value of 15 - no change. [Thinkpad RAM =1.49GB; Dell RAM=256MB]

Can anyone spot what I've overlooked or have any suggestions what I can try next?

Also, does anyone know why the Run command opened the share on the thinkpad at one point while going thru My Network Places I consistently got the 'logon failure' message?

[Fish]

Sorry i can't help you.

Im having a similar problem. One machine on the network, laptop, can see and connect and share files with all others, but none of them can even connect to the laptop. Neither can they ping the IP of the laptop, but laptop can ping all others. Same result whether Ethernet or wireless, Static or dynamic IP.

I noted 2 differences in the setting from ipconfig /all, IP routing and WINS Proxy are both enabled, only on the laptop. I tried have checked / changed registry settings, but they have had no effect. I have searched through my programs and removed any i don't use, don't recognize.

I wonder what these settings are for you?

[Sp0iLedBrAt]

Have you tried turning off simple file sharing and using logon with user name and password? Also, are the IP addresses automatically assigned through DHCP or you set them manually? Are they from the same class?

[AnnieMS]

Hey Fish

Have you tried pinging the Loopback address - 127.0.0.1 - from the laptop? You also can "ping localhost". ping the laptop's IP address that you get from ipconfig /all and ping the laptop's NetBIOS name "ping computername" - all done from the command prompt on the laptop. All those ping commands tell you if the laptop's tcp/ip installation is OK or corrupted. Pinging per the NetBIOS name isn't part of tcp/ip protocols and may tell us something that pinging xxx.xxx.xxx.xxx doesn't - but I don't know what.

I also don't know if the tcp/ip stack can be corrupted one way - you can ping out but no pings in. The fact that you can ping the other computers might tell an expert your tcp/ip stack is not the problem. But since there are no experts around at the moment you might as well see if you can ping to the laptop from the laptop. Maybe the problem is w/ one of those "WAN miniports" I can't find any info about.

WINS is a program run by a server to convert a computer's NetBIOS name to an IP address. Windows computers that are not in a domain network using their NetBIOS broadcasts/requests and NetBIOS can't communicate across a router. If I understand what I've read, the client computers have to be "WINS-enabled" to utilize the WINS server, which is reached by its IP address rather than a NetBIOS name [and thus can communicate w/ computers on the other side of a router]. So a WINS client [somehow] uses an IP address when its seeking name/address resolution or name/address resolution under some circumstances.

A WINS proxy is a computer used on a network whose clients are NOT "WINS-enabled"and they seek name/address resolution thru their NetBIOS broadcasts & requests. The WINS proxy listens to the NetBIOS broadcasts and communicates to a WINS server on behalf on the non-WINS enabled computers.

So my understanding is that a computer w/ WINS proxy enabled would continue to network via basic NetBIOS broadcasting and I would think your other computers would find it - your laptop is finding them. Pinging your laptop w/ its IP address bypasses NetBIOS name resolution and that failed in your network. Do you have a software firewall on your laptop configured differently than on the other computers? I found a check box to block incoming pings on some tab on some software firewall on one of my computers at some point in time.

There's a place in Windows firewall, if you're using that, to check to allow an incoming echo request [ping]. When you open windows firewall in Control Panel it's on the advanced tab > ICMP area > settings button - first one on the list. I think that check enables incoming pings for all adapters/connections - there's also an ICMP tab for each connection in the network connections settings of the advanced tab. You highlight the adapter/connection and click the settings button. Pinging works whether its checked or unchecked if ts checked in the other place.

Does your laptop go into a work environment and connect to a network there where there are computers running server OS's and server programs like WINS Proxy? If it does that may be where the Wins proxy enabled came from and maybe there's some other configuration setting that's causing a problem.

I don't know what "IP routing" is in the context of the ipconfig command. As far as I know your router does the IP routing . Did you ever use the laptop to connect another computer to the internet and enable ICS [internet connections sharing]? I've never used ICS, but maybe there are some settings that get left over when you discontinue using ICS.

That's all I think I know about that. Please post if you figure something out and good luck.

[AnnieMS]

Hey Sp0iLeDBrAt,

Edit: Your suggestion WORKED!!! Thanks.

I turned off SFS and added the same authenticated user to Share Permissions and NTFS Permissions on both computers and rebooted. After reboot I couldn't connect either way [altho F&PS was still excepted in Windows Firewall on both computers and the proper protocols were bound to the adapters, etc] but once I ran the Networking Wizard on both computers I had access both ways.

Sorry for the delay in replying. When I checked my posts my name was the last listed [because I was checking posts thinking I was checking threads] so I didn't check for a reply .

I just wish I knew why SFS wouldn't work - what setting changed where when I turned it off and re-ran the wizard. I had CTL+ALT+DEL logon enabled on both computers and I logged into accounts w/ the same UN & PW on both computers. I had "obtain IP address automatically" checked on both computers and IP Settings [advanced button] showed DHCP enabled [from the router]. I pinged successfully both ways using the IP addresses from ipconfig /all and using ping -a from the desktop to the problem thinkpad displayed the thinkpad's netbios name. [i don't know how the -a parameter works w/ the TCP/IP ping command, but at some level the thinkpad's IP address was associated w/ its netbios name.]

I was using Simple File Sharing in order to use Windows' synch program between the desktop & my external HD, but fortunately I'm not using Windows synching anymore so I can keep SFS turned off. I expected that if access was denied under SFS, it was going to be denied w/ advanced file sharing since one reason I prefer AFS is so security can be tighter - well supposedly or theoretically anyway - but I guess "Simple" file sharing isn't as simple as I thought.

Edited December 1, 2009 by AnnieMS