That might be the only real way to do it sounds like something went wrong during the upgrade process from XP to 7.
Jon On Tue, Jan 31, 2012 at 7:43 PM, Kurt Buff <[email protected]> wrote: > On Tue, Jan 31, 2012 at 16:33, Ben Scott <[email protected]> wrote: > > > > On Tue, Jan 31, 2012 at 6:11 PM, Kurt Buff <[email protected]> wrote: > > > It's one subnet for everything in that office, with the firewall as > > > the gateway, no managed switch (I've been trying for years to get one > > > there). > > > > Okay, so, basically, one big collision domain, one dumb switch. A > > wireless access point plugged into the switch. Firewall/router > > plugged into that same switch. Yah? > > Broadcast domain, but yes, you are correct. I believe they've strung > together a couple of switches, but not more than that. > > > > The machine that are unreachable are in a remote subnet - along with > > > some machines that *are* reachable in that same subnet - and no other > > > machine. > > > > Hmmm, that's interesting. Rules out most routing problems, unless > > they're individual host routes. Rules out firewall misconfigurations > > the same way. Rules out most data dependent problems. > > Which is why I was curios to pint out the routing table on the laptop. > There were no anomalies on that. > > > > happening ... when he's wireless-only as well as wired-only > > > > That rules out the network transceiver, or even the medium (cable). > > > > Curiouser and curiouser. > > > > I'd still check the MAC addresses with your sniffer, make sure the > > frame's it's sending are indeed addressed to the firewall/gateway. > > Although I can't imagine what would cause that, at this stage. (I was > > thinking a static ARP entry, but that would (again) break other things > > on the same destination network.) > > > > Can you walk someone through getting a sniffer going on another > > machine, and plugging that in between the problem laptop and the > > switch? At this point I'm wondering if maybe what the sniffer on the > > laptop is seeing isn't accurate (i.e., things are getting screwed up > > further down in the network stack). > > If he wants to work on this further, I'll suggest that. He's made > noises about wiping it and starting over, and that might be simplest. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
