Access denied after connecting elsewhere

[Guest]

Hi

I have a friend who recently took his notebook on a business trip and hooked into a corporate network in order to check his email. When he came back and hooked back into his three machine, workgroup-based network, he was unable to see the computer that holds a share where he keeps his working files, nor could he print to the shared printer installed on that same machine. He has his notebook sync'd to the share using Offline Files and the sync failed every time and indicated he was offline and could not reconnect to the share

I checked it out for him and found that although he was able to surf the Web and do email, he could not see either of the other two computers in his workgroup. His IP was an APIPA address (169...) even though his Linksys router is running DHCP. To test for a failing cable, I hooked his machine up to a drop where another machine was working flawlessly. I got him an IP but still no access to the machine he needed. I checked all his settings, all the settings on the second machine, verified the WinXP firewall is off for both machines and did a virus check with up-to-date definitions. I did a repair on the connection and nothing... I can consistently get an IP from the router now (even at the original drop -- not a cabling or NIC issue) and I get instant access to the share using the host machine's IP. I have also set up the shared printer using the host machine's IP and run a test print with no problem.

This seems to be a name resolution problem and NetBIOS is set to the 'Default' setting. There is no hosts file so I've pretty much run out of diagnostics. Any suggestions short of setting Alternate fixed IPs for all three machines on the workgroup? I'd like to leave DHCP active so he can connect more easily when he goes elsewhere

Thanks for your help!

 

[Roger Abell]

It sounds like you have checked most things one might expect
to be at issue.
From your post it seems all is fine except for being able to
browse in network neighborhood, or map by name.

However, since you did not mention it, even though you most
likely did check this, the machines are using the same workgroup
name ?

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

Hi,

I have a friend who recently took his notebook on a business trip and

hooked into a corporate network in order to check his email. When he came
back and hooked back into his three machine, workgroup-based network, he was
unable to see the computer that holds a share where he keeps his working
files, nor could he print to the shared printer installed on that same
machine. He has his notebook sync'd to the share using Offline Files and the
sync failed every time and indicated he was offline and could not reconnect
to the share.

I checked it out for him and found that although he was able to surf the

Web and do email, he could not see either of the other two computers in his
workgroup. His IP was an APIPA address (169...) even though his Linksys
router is running DHCP. To test for a failing cable, I hooked his machine up
to a drop where another machine was working flawlessly. I got him an IP but
still no access to the machine he needed. I checked all his settings, all
the settings on the second machine, verified the WinXP firewall is off for
both machines and did a virus check with up-to-date definitions. I did a
repair on the connection and nothing... I can consistently get an IP from
the router now (even at the original drop -- not a cabling or NIC issue) and
I get instant access to the share using the host machine's IP. I have also
set up the shared printer using the host machine's IP and run a test print
with no problem.

This seems to be a name resolution problem and NetBIOS is set to the

'Default' setting. There is no hosts file so I've pretty much run out of
diagnostics. Any suggestions short of setting Alternate fixed IPs for all
three machines on the workgroup? I'd like to leave DHCP active so he can
connect more easily when he goes elsewhere.

 

[Simon Woolley]

Might also want to try nbtstat -R
Should flush the NETBIOS name resolution cache
Set Netbios over TCP\IP to enabled.

Regards
Simon