Search results for query: *

www.tzo.com dynamic dns. set the script up to run every minute, and you don't need to worry about it anymore...

dawned on me you may not know how to make one. basically get a cable you don't need. cut off one end. connect white-orange and blue-white, and orange-white and white-blue. of course, if you wanna see on an oscope, you'll have to somehow put it in the middle of those :/ on your own there :P

either go buy, or "hack" together a loopback device. simply hardwire your xmit pair to your receive pair, and voila'!

the only way *i* know is to telnet to the thing, and look at the port config. if you could figure out a way to pull up stats for that interface, and look at the collisions stat, if it was zero, that would strongly indicate full duplex. maybe somebody else can chime in ...

jinxx, FYI. i used to manage third party connectivity for compaq, and i got to see a TON of frame from a TON of different vendors. your experience with sprint really is quite different from literally %100 of the sites i saw with it. cpq's latency - cross country - from our vendors would be, say...

oops. got swamped at work. sorry. sending an email to my work addy now so i won't forget again :/

okey doke. i'll have a syntax example here a little later today. (0530 local - need a bit to "get up to speed :-)

TimRegester - for REAL!? i didn't know gbics kbew anything other than gig. you're sure????

well, if your version of IOS supports generic traffic shaping, you could just shape it to the lower bandwidth. in effect "spoofing" the router into thinking that pipe is much smaller than it really is. need help with syntax for GTS?

did you do a bug scrub on that IOS version before you upgraded??? sounds like your snazzy new IOS version has a serious ISDN bug.

gig is gig. period. you need to come up with a 10/100 port somewhere.

ok, make sure i have this correct. sending FROM the windows box TO the unix box, yes? if that is the case, i hate to say this, but "welcome to windows". windows has a nasty habit of ratcheting down tcp window size and then never ratcheting it back UP when appropriate. i assume unix to...

those rate limits should indeed work, however, anything "going over" that interface is likely to see random "issues". when it drops, it provides no nontification to the end station - it just drops it in the bit bucket.

ok, 2 things. "in the business", sprint frame relay is jokingly referred to as "same day frame relay service" - their latencies are HUGE compared to their competitors. 2nd, traffic shaping may indeed save your butt here. also, if you're seeing BECNs and FECNs, you have...

8724374 input errors, 5315962 CRC, 3319903 frame, 0 overrun, 0 ignored, 439 1 abort there's your problem. you have a borked cable, transceiver or some other physical problem, apparently. i'm not overly familiar with the smaller cisco devices, but if you've checked all the obvious stuff (loose...

tried swapping out the nic?

i'm pretty sure if there's any setting for tweeking this, they're going to be buried in the registry.we did some lab testing on this os, and it's network performance was notably poor, doing pretty much ANYTHING. for instance, a quad ppro 200mhz with 192MB of RAM running unix was EASILY twice as...