In the grand tradition of Hatrack, here're some REAL technical questions:
1) I have a Win2003/IIS6 box running Frontpage 2002 extensions. When I browse to one of its webs from my own machine (via a web browser), or open that web in Frontpage, it pops right up. When I browse from a machine on a different VLAN, the connection is made -- eventually -- but only trickles out data and finally peters out, closing the connection. Possibilities?
2) I have a Win2003 file server. I am currently sharing one folder, and permissions (for the purposes of testing) are wide open. When I browse to that machine from my box, again, there's little difficulty -- but some unusual slowness. When I hit the share from a machine on another VLAN, Windows Explorer eventually times out; the data, again, trickles and stops.
Before I drop netmon on these boxes and start wading through packets, does anyone have some obvious suggestions that I might be missing? It LOOKS like our routing's okay, but everything about this smells like a routing problem.
Posted by John L (Member # 6005) on :
Tom, keep this thread up in the queue. I'm not home and don't have my laptop open right now, but I have some resources that may be useful. I'll get back to you in about an hour.
Posted by John L (Member # 6005) on :
Okay, first off, what is handling the name resolution? If the servers aren't handling name resolutions outside of their own domain, then that could explain the slowness (but not the timeouts). Other than that, it definitely sounds like a routing issue, where you may not have to sift through packets, but you may have to double-check the topology. For example: what is the current routing layout with regard to the VLANs? Try some ping, tracert, and pathping checks. Find out what is hopping where before sniffing the network.
Posted by TomDavidson (Member # 124) on :
John, it MAY be a bad blade, as both boxes are on the same new blade on our CS6509; I swapped the file server to another (known good) blade, and the problems completely vanished. Once I can swap the web box, I'll be able to confirm the issue -- but that would certainly explain the problems we're seeing.
Posted by John L (Member # 6005) on :
Yeah, I know of a few examples where it was actually a bad network adapter that caused similar problems. Not bad enough to not work, but bad enough to cause serious issues with network traffic. If you can get hold of it, CommView is really good at tracking such problems down (if it's spurious packets). There are others, but those are out of my price range, both in licensing and training.
Posted by Zevlag (Member # 1405) on :
Tom, let us know if that fixes the prob for you. If not, give us some more detail on the routing/VLAN config.