Ram disk... reminds me of Windows 98 boot disk.
H
Posts made by Harry Lui
-
RE: AMD Radeon RamDisk Utility for Windowsposted in News
-
RE: How Do Such Big Gaps Get Missed in IT Educationposted in IT Careers
Hm... Let's see how I learn format.
I broke the 512MB hardddrive by dropping it accidentally. I bought a replacement 1GB harddrive and plug it, expect it to work when I turned on the computer, except that it didn't. I had a MS DOS 6.2 3.5 inch floppy disk so I booted of that and start typing in HELP and read thru all the commands. Found FDISK and FORMAT. Ran both and then I can use the harddrive. I was 13 and this was the time without internet, smartphone, nor instruction from anything or anyone. I just figure Operation System must have the things I need to make the harddrive work.
First time I had virtualization experience was watching someone using Windows inside a Mac at school, I think I was 15.
-
RE: So I bought an abandoned Storage unit in Paradise, CA - Tons of vinage computer stuff was inside.posted in Self Promotion
I wonder how much $$$$ the guy paid for storage...
$60 a month x 12 x 20 =$14400
-
RE: ODBC passwordposted in IT Discussion
Are you installing SQL because of another program? If so, look thru the program's instruction, you may find what you need.
-
RE: Why are local drives betterposted in IT Discussion
Less COST makes local drives better.
Less network traffic makes local drives better.
Less switch/jack/cable needed makes local drives better.
Less IP address/setup/maintenance/update/firmware makes local drives better. -
RE: Was It the Last IT Guys Faultposted in IT Discussion
Was it the last IT guy's fault? You can be the judge.
When I first started with my current company, I was suppose to meet the last IT guy so he can show me things, it never happened, he never showed up! After a day and a half of waiting, my boss gave me the last IT guy's credential and I logged into the IT computer, I found he had his google account logged in, I can see his "google hangouts" buddies, I can see his gmails, I can see he was chatting real time with his buddies and when he was going to start playing games with them. I reported the finding to my boss and let it be. When I looked for documents, they were 7 months behind, just so happen the last IT guy was here 7 months.
During the first week, three physical servers froze, two were DC servers. During the second week, virtual email server ran out of disk space, I had to come in on a Saturday to fix it. Even though the email server is a virtual server, I found the email data volume is spanned across three drives. I think my heart skipped a beat or 10. I had to add another drives to the spanned volume just to get the email server working. I fixed the spanned volume the week after, by enlarging the main drive, defragging the volume and removing the additional drives.
VMware vSphere Essentials Plus Kit, (over $5,000) was purchased, yet, the company servers are only setup to use VMware vSphere Essentials Kits (slightly over $500) worth of functions (backup API and vCenter). Company could have chosen HyperV and saved over $5,000 and will not make a difference in daily operations! Only two ESXi virtual server were setup. vCenter was also installed on a physical server running windows server, I replace it with a vCenter appliance running on one of the the ESXi host and saved a server license.
In the third week, I proposed and got approval to buy a few used HP DL380G6 and use them as virtual server host, buy more RAM, and new 2TB harddrives to refresh the current virtual host servers as well as converting all physical servers to virtual. DL380G6 was $50 each, RAM and harddrives were the main expense, total was maybe $5,000. A week or two after I have got three HP DL380G6 servers with new harddrives and RAM hosting the virtual servers and running happily and couple spare HP DL380G6 shells/RAM/harddrives for DR.
At one point of time, the physical windows file server was running out of space, but instead of buying more harddrives for the server, a decision was made to buy QNAP NAS, set to RAID 5, established an iSCSI connection to the server, then the server shared out the files. Result was a unstable file server that would forget permission of files when the server is restarted. There was an old HP server on the IT desk, the document left behind by two IT guy ago said this would make a good file server, but he didn't think he has time to setup up the server. During the first week there, I plug the kvm and power to that server, server will not even boot!!
Two months in, the physical windows file server finally crashed. File system was in a read only mode and would not allow any write until the CHKDSK was done. I saw this as an opportunity to get rid of the physical server and QNAP at the same time. I gave my boss two options: I can attempt to repair the current physical file server or I can spend time and energy to build a new virtual file server and then copy everything over. Boss chose the latter and I had the new virtual server up and sharing its files by the next morning. I set it up so quickly, I wondered why the two IT guy ago even bother to write the document stating he didn't have the time.
So, by the start of the third month, I had all virtual servers on fresh harddrives running RAID10, I have three virtual hosts and no other physical servers, I had cold server shells with RAM and harddrives for DR, no more QNAP running RAID5, plenty of disk space for all the virtual servers, all virtual servers were backed up, no more frozen servers since the virtual conversion and I can sleep better.
-
RE: Help With Resumeposted in IT Discussion
@scottalanmiller said in Help With Resume:
@Harry-Lui said in Help With Resume:
HIPPA compliant? Put it in if you are.
How is a person HIPAA compliant?
Excuse me, English is my third language.
I meant to say whatever status he would be after taking HIPAA test, assuming OP took a HIPAA test at Rose Radiology. -
RE: What do you think of these ping response time from these switches?posted in IT Discussion
@momurda said in What do you think of these ping response time from these switches?:
@JaredBusch said in What do you think of these ping response time from these switches?:
Regarding that last screenshot.
Connect to the serial port and verify boot completed and all that. then start your pings.
It is entirely possible it was still booting.
Yes that might be true; the ping times incrementally get larger until they go back to 1, at least in the screenshot, but not the posted wall of text.
In the first wall of text ping times start high and go down slowly.
In the last screenshot they start low and get higher til they all go back to 1.
To me this is either something booting up, or a bottleneck somewhere.
I might check the wireless stuff as a starting point.All pings/logs are from different switches. Please read the notes.
-
RE: What do you think of these ping response time from these switches?posted in IT Discussion
@DustinB3403
We are having issue with multiple switches. Same make, different model of switches.@JaredBusch
I am not on site. Can't do any complicated test other than the ping test batch file I am having the technician run.
We took out the rack mount 26 port switch (picture of the laptop with the white cat5 connected to a switch) and put in a 24 port NetGear switch and these are the response. This test was with a full load on the NetGear switch while the picture above is just with one laptop plugged into it.Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64...
Ping statistics for 192.168.1.1:
Packets: Sent = 75002, Received = 75002, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0msI think the switches in questions are just badly design/manufactured/programmed/whatever. Switch maker doesn't think so and told us their switch is working as design.
-
What do you think of these ping response time from these switches?posted in IT Discussion
Pinging from a server that connects to a 24 port rack mount switch, then to a pair of wireless bridge, then to a 8 port rack mount switch.
Switch maker said the ping delay from switch is not a issue with the switch, as long as the switch can pass traffic fine. I tend to disagree.
Pinging 192.168.1.33 with 32 bytes of data: Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Request timed out. Request timed out. Reply from 192.168.1.33: bytes=32 time=245ms TTL=128 Reply from 192.168.1.33: bytes=32 time=230ms TTL=128 Reply from 192.168.1.33: bytes=32 time=223ms TTL=128 Reply from 192.168.1.33: bytes=32 time=214ms TTL=128 Reply from 192.168.1.33: bytes=32 time=201ms TTL=128 Reply from 192.168.1.33: bytes=32 time=191ms TTL=128 Reply from 192.168.1.33: bytes=32 time=187ms TTL=128 Reply from 192.168.1.33: bytes=32 time=176ms TTL=128 Reply from 192.168.1.33: bytes=32 time=164ms TTL=128 Reply from 192.168.1.33: bytes=32 time=147ms TTL=128 Reply from 192.168.1.33: bytes=32 time=150ms TTL=128 Reply from 192.168.1.33: bytes=32 time=139ms TTL=128 Reply from 192.168.1.33: bytes=32 time=126ms TTL=128 Reply from 192.168.1.33: bytes=32 time=128ms TTL=128 Reply from 192.168.1.33: bytes=32 time=121ms TTL=128 Reply from 192.168.1.33: bytes=32 time=120ms TTL=128 Reply from 192.168.1.33: bytes=32 time=109ms TTL=128 Reply from 192.168.1.33: bytes=32 time=98ms TTL=128 Reply from 192.168.1.33: bytes=32 time=100ms TTL=128 Reply from 192.168.1.33: bytes=32 time=100ms TTL=128 Reply from 192.168.1.33: bytes=32 time=90ms TTL=128 Reply from 192.168.1.33: bytes=32 time=80ms TTL=128 Reply from 192.168.1.33: bytes=32 time=67ms TTL=128 Reply from 192.168.1.33: bytes=32 time=57ms TTL=128 Reply from 192.168.1.33: bytes=32 time=48ms TTL=128 Reply from 192.168.1.33: bytes=32 time=38ms TTL=128 Reply from 192.168.1.33: bytes=32 time=25ms TTL=128 Reply from 192.168.1.33: bytes=32 time=15ms TTL=128 Reply from 192.168.1.33: bytes=32 time=19ms TTL=128 Reply from 192.168.1.33: bytes=32 time=23ms TTL=128 Reply from 192.168.1.33: bytes=32 time=11ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=8ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=11ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=12ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=421ms TTL=128 Reply from 192.168.1.33: bytes=32 time=410ms TTL=128 Reply from 192.168.1.33: bytes=32 time=398ms TTL=128 Reply from 192.168.1.33: bytes=32 time=400ms TTL=128 Reply from 192.168.1.33: bytes=32 time=391ms TTL=128 Reply from 192.168.1.33: bytes=32 time=380ms TTL=128 Reply from 192.168.1.33: bytes=32 time=381ms TTL=128 Reply from 192.168.1.33: bytes=32 time=372ms TTL=128 Reply from 192.168.1.33: bytes=32 time=373ms TTL=128 Reply from 192.168.1.33: bytes=32 time=372ms TTL=128 Reply from 192.168.1.33: bytes=32 time=361ms TTL=128 Reply from 192.168.1.33: bytes=32 time=364ms TTL=128 Reply from 192.168.1.33: bytes=32 time=354ms TTL=128 Reply from 192.168.1.33: bytes=32 time=343ms TTL=128 Reply from 192.168.1.33: bytes=32 time=334ms TTL=128 Reply from 192.168.1.33: bytes=32 time=324ms TTL=128 Reply from 192.168.1.33: bytes=32 time=312ms TTL=128 Reply from 192.168.1.33: bytes=32 time=305ms TTL=128 Reply from 192.168.1.33: bytes=32 time=302ms TTL=128 Reply from 192.168.1.33: bytes=32 time=304ms TTL=128 Reply from 192.168.1.33: bytes=32 time=294ms TTL=128 Reply from 192.168.1.33: bytes=32 time=285ms TTL=128 Reply from 192.168.1.33: bytes=32 time=274ms TTL=128 Reply from 192.168.1.33: bytes=32 time=276ms TTL=128 Reply from 192.168.1.33: bytes=32 time=271ms TTL=128 Reply from 192.168.1.33: bytes=32 time=266ms TTL=128 Reply from 192.168.1.33: bytes=32 time=255ms TTL=128 Reply from 192.168.1.33: bytes=32 time=242ms TTL=128 Reply from 192.168.1.33: bytes=32 time=231ms TTL=128 Reply from 192.168.1.33: bytes=32 time=232ms TTL=128 Reply from 192.168.1.33: bytes=32 time=220ms TTL=128 Reply from 192.168.1.33: bytes=32 time=203ms TTL=128 Reply from 192.168.1.33: bytes=32 time=204ms TTL=128 Reply from 192.168.1.33: bytes=32 time=206ms TTL=128 Reply from 192.168.1.33: bytes=32 time=208ms TTL=128 Reply from 192.168.1.33: bytes=32 time=205ms TTL=128 Reply from 192.168.1.33: bytes=32 time=212ms TTL=128 Reply from 192.168.1.33: bytes=32 time=198ms TTL=128 Reply from 192.168.1.33: bytes=32 time=192ms TTL=128 Reply from 192.168.1.33: bytes=32 time=181ms TTL=128 Reply from 192.168.1.33: bytes=32 time=182ms TTL=128 Reply from 192.168.1.33: bytes=32 time=173ms TTL=128 Reply from 192.168.1.33: bytes=32 time=159ms TTL=128 Reply from 192.168.1.33: bytes=32 time=162ms TTL=128 Reply from 192.168.1.33: bytes=32 time=156ms TTL=128 Reply from 192.168.1.33: bytes=32 time=156ms TTL=128 Reply from 192.168.1.33: bytes=32 time=158ms TTL=128 Reply from 192.168.1.33: bytes=32 time=158ms TTL=128 Reply from 192.168.1.33: bytes=32 time=160ms TTL=128 Reply from 192.168.1.33: bytes=32 time=157ms TTL=128 Reply from 192.168.1.33: bytes=32 time=149ms TTL=128 Reply from 192.168.1.33: bytes=32 time=150ms TTL=128 Reply from 192.168.1.33: bytes=32 time=152ms TTL=128 Reply from 192.168.1.33: bytes=32 time=154ms TTL=128 Reply from 192.168.1.33: bytes=32 time=150ms TTL=128 Reply from 192.168.1.33: bytes=32 time=139ms TTL=128 Reply from 192.168.1.33: bytes=32 time=128ms TTL=128 Reply from 192.168.1.33: bytes=32 time=130ms TTL=128 Reply from 192.168.1.33: bytes=32 time=126ms TTL=128 Reply from 192.168.1.33: bytes=32 time=127ms TTL=128 Reply from 192.168.1.33: bytes=32 time=122ms TTL=128 Reply from 192.168.1.33: bytes=32 time=110ms TTL=128 Reply from 192.168.1.33: bytes=32 time=97ms TTL=128 Reply from 192.168.1.33: bytes=32 time=98ms TTL=128 Reply from 192.168.1.33: bytes=32 time=107ms TTL=128 Reply from 192.168.1.33: bytes=32 time=100ms TTL=128 Reply from 192.168.1.33: bytes=32 time=104ms TTL=128 Reply from 192.168.1.33: bytes=32 time=92ms TTL=128 Reply from 192.168.1.33: bytes=32 time=93ms TTL=128 Reply from 192.168.1.33: bytes=32 time=81ms TTL=128 Reply from 192.168.1.33: bytes=32 time=69ms TTL=128 Reply from 192.168.1.33: bytes=32 time=66ms TTL=128 Reply from 192.168.1.33: bytes=32 time=64ms TTL=128 Reply from 192.168.1.33: bytes=32 time=60ms TTL=128 Reply from 192.168.1.33: bytes=32 time=67ms TTL=128 Reply from 192.168.1.33: bytes=32 time=52ms TTL=128 Reply from 192.168.1.33: bytes=32 time=47ms TTL=128 Reply from 192.168.1.33: bytes=32 time=48ms TTL=128 Reply from 192.168.1.33: bytes=32 time=52ms TTL=128 Reply from 192.168.1.33: bytes=32 time=44ms TTL=128 Reply from 192.168.1.33: bytes=32 time=32ms TTL=128 Reply from 192.168.1.33: bytes=32 time=21ms TTL=128 Reply from 192.168.1.33: bytes=32 time=14ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=10ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=7ms TTL=128 Reply from 192.168.1.33: bytes=32 time=11ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=6ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=5ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=2ms TTL=128 Reply from 192.168.1.33: bytes=32 time=4ms TTL=128 Reply from 192.168.1.33: bytes=32 time=3ms TTL=128 Reply from 192.168.1.33: bytes=32 time=434ms TTL=128 Reply from 192.168.1.33: bytes=32 time=433ms TTL=128 Reply from 192.168.1.33: bytes=32 time=423ms TTL=128 Reply from 192.168.1.33: bytes=32 time=421ms TTL=128 Reply from 192.168.1.33: bytes=32 time=415ms TTL=128 Reply from 192.168.1.33: bytes=32 time=402ms TTL=128 Reply from 192.168.1.33: bytes=32 time=402ms TTL=128 Reply from 192.168.1.33: bytes=32 time=391ms TTL=128 Reply from 192.168.1.33: bytes=32 time=389ms TTL=128 Reply from 192.168.1.33: bytes=32 time=373ms TTL=128 Reply from 192.168.1.33: bytes=32 time=374ms TTL=128 Reply from 192.168.1.33: bytes=32 time=377ms TTL=128 Reply from 192.168.1.33: bytes=32 time=367ms TTL=128 Reply from 192.168.1.33: bytes=32 time=358ms TTL=128 Reply from 192.168.1.33: bytes=32 time=348ms TTL=128 Reply from 192.168.1.33: bytes=32 time=348ms TTL=128 Reply from 192.168.1.33: bytes=32 time=355ms TTL=128 Reply from 192.168.1.33: bytes=32 time=353ms TTL=128 Reply from 192.168.1.33: bytes=32 time=357ms TTL=128 Reply from 192.168.1.33: bytes=32 time=352ms TTL=128 Reply from 192.168.1.33: bytes=32 time=352ms TTL=128 Reply from 192.168.1.33: bytes=32 time=353ms TTL=128 Reply from 192.168.1.33: bytes=32 time=351ms TTL=128 Reply from 192.168.1.33: bytes=32 time=341ms TTL=128 Reply from 192.168.1.33: bytes=32 time=343ms TTL=128 Reply from 192.168.1.33: bytes=32 time=333ms TTL=128 Reply from 192.168.1.33: bytes=32 time=325ms TTL=128 Reply from 192.168.1.33: bytes=32 time=329ms TTL=128 Reply from 192.168.1.33: bytes=32 time=319ms TTL=128 Reply from 192.168.1.33: bytes=32 time=322ms TTL=128 Reply from 192.168.1.33: bytes=32 time=313ms TTL=128 Reply from 192.168.1.33: bytes=32 time=298ms TTL=128 Reply from 192.168.1.33: bytes=32 time=302ms TTL=128 Reply from 192.168.1.33: bytes=32 time=297ms TTL=128 Reply from 192.168.1.33: bytes=32 time=284ms TTL=128 Reply from 192.168.1.33: bytes=32 time=273ms TTL=128 Reply from 192.168.1.33: bytes=32 time=267ms TTL=128 Reply from 192.168.1.33: bytes=32 time=260ms TTL=128 Reply from 192.168.1.33: bytes=32 time=249ms TTL=128 Reply from 192.168.1.33: bytes=32 time=239ms TTL=128 Reply from 192.168.1.33: bytes=32 time=231ms TTL=128 Reply from 192.168.1.33: bytes=32 time=230ms TTL=128 Reply from 192.168.1.33: bytes=32 time=217ms TTL=128 Reply from 192.168.1.33: bytes=32 time=222ms TTL=128 Reply from 192.168.1.33: bytes=32 time=212ms TTL=128 Reply from 192.168.1.33: bytes=32 time=216ms TTL=128 Reply from 192.168.1.33: bytes=32 time=205ms TTL=128 Reply from 192.168.1.33: bytes=32 time=194ms TTL=128 Reply from 192.168.1.33: bytes=32 time=193ms TTL=128 Reply from 192.168.1.33: bytes=32 time=192ms TTL=128 Reply from 192.168.1.33: bytes=32 time=186ms TTL=128Ping statistics for 192.168.1.33:
Packets: Sent = 89683, Received = 89608, Lost = 75 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2280ms, Average = 94msIn this separate test, I had a laptop plug directly to a 26 port rack mount switch, ping gets drop but switch maker said the switch is working in their environment.
Tried 3 different cables, 3 different port on switch same result.
In this separate test, nothing else is plug into the 8 port rack mount switch other than the laptop, switch was even reset to factory default, and I got this response. It goes to a cycle of 1ms then back up to ~400ms than back to 1ms and repeat.
