Recent content by mfoc

Just spoke with the Qwest tech again. It sounds like their local equipment MTU was set to 1500 instead of 1546?? He wasn't really clear. In any case, they're moving everything to 9216 to support jumbo - the equipment I was using just hadn't been changed yet. He's seeing a few dropped packets...

Qwest called me back and said that the local engineer recognized a configuration error in the local equipment. Switched from my wireless back to the QMOE last night - all seems well today. AD sluggishness is gone, encrypted traffic seems solid. An informal 200 second speed test this morning...

ip cef is enabled Update from Qwest - the national tech I have on the case took a deeper look and suspects that packet size may be the issue with the local Qwest equipment. He tried to send some larger ping packets through the local switches and they didn't make it. He'll be following up with...

Qwest claims they are layer-2 all the way through on this circuit. The next step is to put traffic through it again and see if we can increment errors on any of the interfaces. I have a wireless point-to-point using the same router - no vlan tagging though - works fine. The only difference...

The QMOE circuit is 100Mbps, however, this VLAN on the circuit is 70Mbps. The other 30Mbps will be an Internet VLAN. As far as Qwest encryption, I'm not sure what they're doing.

I'm having some strange issues on my newly tagged intra-office QMOE VLAN connection. The first noticeable issue was Active Directory functions slowed down to a crawl. AD lookups became extremely sluggish (I have a DC at both locations on the same domain). The other issue happened with remote...

OK, how about this: - It uses the core switch as the gateway - It splits the QMOE VLAN's at the edge router - Old firewall with DMZ'd app servers is segregated - Web browsing traffic uses Barracuda and new firewall Bonus - it frees up one of my 2811's.

Currently, I have a 100Mbps MOE circuit connecting two offices and I'm taking a 30Mbps chunk to bring in new Internet service to our Main Office. My issue question is.... What's the best way to split the Internet portion off and send it in through the firewall - or even a different firewall...

Found the answer here: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=39

Maybe this is better described in simpler terms: My external address to the sharepoint server no longer connects to sharepoint. Internally, http://machinename/sites/sitename works fine. Externally, http://domainname/sites/sitename doesn't work fine. I get the authentication window - then a...

I just upgraded to 3.0 from 2003 and I can't get to any pages from outside of my network. Everything inside works fine, but only if you use the machine name http://sharepoint )or if the external domain name resolves to sharepoint). Since the upgrade, nobody outside of the network can get in...

I found a solution, if you have the resources. I stripped off Office 2007, installed Office XP Pro, and then installed Office 2007 over the top of Office XP Pro. The Excel Integration module works after doing this.

Same problem here. Some interesting info though - I have another user who has the Office 2007 suite and it works fine on his..?? The only difference I can see is that the Office 2007 installation on the working machine didn't seem to get rid of all of the previous Office XP files. Office XP...

I clinched my teeth and used the SDM QoS Wizard. Here's what it gave me (some items obviously removed for secutiy purposes): Current configuration : 9512 bytes ! version 12.4 service tcp-keepalives-in service tcp-keepalives-out service timestamps debug datetime msec localtime show-timezone...

Thanks for the response. Does it matter that the interface at Site A is functioning as that office's entire Internet connection? If I apply your aformentioned mechanisms, won't it affect more than just the Site A to Site B traffic?