Turning the firewall off on both machines makes no difference to
anything. Trying to map drives elicits exactly the same similar but
different responses. Trying to ping from one to the other also has
exactly the same results.
*I asked this yesterday I think. Is there perhaps a big clue in the
failure of the laptop to ping the desktop? Is this not LAN adapter to
LAN adapter via the router with no or at least minimal involvement of
the OS?*
Chuck Norcutt
On 7/31/2011 9:16 AM, Jez Cunningham wrote:
> IANAexpert but it kinda sounds like the ship's IT folks turned on the
> laptop firewall too tightly... I'm afraid I would definitely suspect
> something they did...
> Jez
>
> On 31/07/2011, Chuck Norcutt<chucknorcutt@xxxxxxxxxxxxxxxx> wrote:
>> I've reset the router, swapped router cable sockets between the two
>> machines, swapped cables into previously unused sockets... no change.
>> The desktop can ping the laptop but the laptop can't ping the desktop.
>> :-(
>>
>> Chuck Norcutt
>>
>> On 7/30/2011 9:31 PM, Chuck Norcutt wrote:
>>> Well, it's been a totally frustrating day.
>>>
>>> The desktop can ping the laptop by name which gets translated to the
>>> correct address and all 3 trials are successful.
>>> The laptop can ping the desktop by name, which gets translated to the
>>> correct address but the ping is not successful. It times out on all 3
>>> trials. Yet we know that both machines have internet connectivity
>>> through the router since the internet is working fine.
>>>
>>> running "netstat -n" on each machine returns only information about
>>> itself. Likewise, "route print" run on the laptop returns only
>>> information about itself and the router, nothing about the desktop where
>>> the printers are installed. I uninstalled several old print drivers
>>> from the laptop and then tried printing to the HP inkjet that's on the
>>> desktop and has always worked previously... no go. The document failed
>>> to print and ended up stuck in the laptop's HP printer queue.
>>>
>>> Running "arp -a" from each machine properly resolves the router's MAC
>>> address. Running "ipconfig /all" is similar to "route print". Each
>>> machine returns only the info for itself and the router, nothing about
>>> it's network partner.
>>>
>>> If I then attempt something like mapping a drive from each machine I get
>>> failures on both but subtly different messages. The laptop says: "The
>>> drive could not be mapped because no network was found." The desktop
>>> says: "The network path xxxxxxxxxxxx could not be found." Remembering
>>> that the desktop could ping the laptop but not vice-versa putting these
>>> data points together is perhaps a clue to what's happening or not
>>> happening.
>>>
>>> There have been no password changes on either machine for many months,
>>> long before they were disconnected and rejoined. I checked the local
>>> net security policy or tried to. The desktop supports viewing and
>>> changing such policies through the control panel's administrative tools
>>> or via the command line "gpedit.msc". These are set for guest access as
>>> they have always been. But the laptop has no such tools in the
>>> administrative tool set and also doesn't support "gpedit.msc". Both
>>> machines are on Service Pack 3 but the desktop runs "Media Center
>>> Edition" and the laptop runs "Home Edition". I assume MS didn't want
>>> home users messing with network security policy. Presumably the
>>> settings there are as they have always been since there's no ready way
>>> to change them. But I do suppose that the QM2's IT personnel could have
>>> done so. But I don't know why they would.
>>>
>>> Given that things can pass in and out of the router to the internet but
>>> apparently not between the local machines is it reasonable to suspect a
>>> partial failure of the router? I did repower and reboot it after I came
>>> home. Maybe I should to that again as well as swapping cables between
>>> its ports?
>>>
>>> Chuck Norcutt
>>>
>>>
>>>
>>>
>>> On 7/30/2011 9:58 AM, Chuck Norcutt wrote:
>>>> Thanks again. I'll be sure to check all of this stuff and add it to
>>>> your prior list.
>>>>
>>>> Chuck Norcutt
>>>>
>>>>
>>>> On 7/30/2011 9:50 AM, WayneS wrote:
>>>>> I mentioned the login/authentification issue as being the most likely
>>>>> issue, as the network seems to be up and running. So the question as
>>>>> to whether the login has changed or was the laptop was used to
>>>>> connect during travel? Most of my issues have been security issues
>>>>> that deny access, either by firewall, login passwords or other
>>>>> authentication problems. The Name resolution conflict from running
>>>>> diagnostics is also curious (hence suggested arp -a command check).
>>>>>
>>>>> Suggest you check the passwords and shut off firewall temporarily to
>>>>> try to isolate the problem. Check the network access policies with
>>>>> gpedit.msc on both machines. And sometimes, even though you change
>>>>> settings, like file and print setting, they don't take affect until a
>>>>> reboot, (unless you know what service to stop and restart).
>>>>>
>>>>> Wayne
>>>>>
>> --
>> _________________________________________________________________
>> Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
>> Archives: http://lists.thomasclausen.net/mailman/private/olympus/
>> Themed Olympus Photo Exhibition: http://www.tope.nl/
>>
>>
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|