Sponsored Content
Operating Systems Solaris Copy via samba on vmware workstation with Solaris taking much longer than usual Post 302771732 by hicksd8 on Thursday 21st of February 2013 10:48:17 AM
Old 02-21-2013
I'll just add a few more points from my experience that might help.

1. It doesn't matter what Windoze version it is, old or new, they all seem to suffer from this.
2. Using gigabit interfaces makes it worse.
3. Transfering very large files makes it much worse. Starts off good and then gets sloooooower and slooooooooooooooower. Thousands of smaller files is less of a problem but still slow.

Hope that helps. As you'll see in the link I posted above, people say "Why doesn't Microsoft do something to help us poor buggers out!". But they don't!
 

6 More Discussions You Might Find Interesting

1. Solaris

How to install Sun Solaris 10 inside VMware Workstation 5.5

Some members asked about this way, click Here u will find what u want (1 Reply)
Discussion started by: Sound Of Wisdom
1 Replies

2. Solaris

Error opening PAM libraries : solaris 10 on vmware workstation

Hi Admins, I am facing an issue with Solaris 10 sitting on vmware workstation... When I start it, it gives me an error : "Error opening PAM libraries, contact system administrator" Also I can reach it via putty, but none of the id/passwd working. I did revert pam.conf. But still no... (2 Replies)
Discussion started by: snchaudhari2
2 Replies

3. Solaris

Solaris 10x86 on VMware Workstation

Is it possible to create metadevices and soft partitions using Solaris Volume Manager on Solaris 10 x86 that is running on VMware Workstation. It would a low cost method to practice extending soft partitions and metadevices. If anyone has an experience with this please share. Regards (1 Reply)
Discussion started by: Tirmazi
1 Replies

4. Linux

vmware workstation

i have following :- fedora 16 x 64bit kernel 3.2.7-1 vmware workstation 8.0.2. Steps to install vmware workstation to access ESX machine 1- sh vmware name.bundle 2- setup started and completed with out any warning. 3- when i type "vmware " then "VMware Module Updater Started" and the... (2 Replies)
Discussion started by: engrtahir2007
2 Replies

5. Solaris

Solaris x86 on vmware workstation panic and almost crashing

Hello Admins, Howz it going? Coming to our forum after long time. Well, a solaris x86 system on my vmware workstation is facing a big trouble. I did a file system check on root file system. And after reboot, I am getting an error for both normal mode and fail safe mode. I have... (4 Replies)
Discussion started by: snchaudhari2
4 Replies

6. Solaris

Solaris x86 guest in vmware workstation

I swear I have no other devices on the vmnet 192.168.142.2, but after I configured one of the solaris x86 os, I kept getting warning ..node xx xxxxx have our ip addresss 192.168.142.2, and it scrolled thru it forever .. I tried to boot it into single user mode , still having the same issue.. ... (1 Reply)
Discussion started by: ppchu99
1 Replies
PCAP_INJECT(3PCAP)														PCAP_INJECT(3PCAP)

NAME
pcap_inject, pcap_sendpacket - transmit a packet SYNOPSIS
#include <pcap/pcap.h> int pcap_inject(pcap_t *p, const void *buf, size_t size); int pcap_sendpacket(pcap_t *p, const u_char *buf, int size); DESCRIPTION
pcap_inject() sends a raw packet through the network interface; buf points to the data of the packet, including the link-layer header, and size is the number of bytes in the packet. Note that, even if you successfully open the network interface, you might not have permission to send packets on it, or it might not sup- port sending packets; as pcap_open_live() doesn't have a flag to indicate whether to open for capturing, sending, or capturing and sending, you cannot request an open that supports sending and be notified at open time whether sending will be possible. Note also that some devices might not support sending packets. Note that, on some platforms, the link-layer header of the packet that's sent might not be the same as the link-layer header of the packet supplied to pcap_inject(), as the source link-layer address, if the header contains such an address, might be changed to be the address assigned to the interface on which the packet it sent, if the platform doesn't support sending completely raw and unchanged packets. Even worse, some drivers on some platforms might change the link-layer type field to whatever value libpcap used when attaching to the device, even on platforms that do nominally support sending completely raw and unchanged packets. pcap_sendpacket() is like pcap_inject(), but it returns 0 on success, rather than returning the number of bytes written. (pcap_inject() comes from OpenBSD; pcap_sendpacket() comes from WinPcap. Both are provided for compatibility.) RETURN VALUE
pcap_inject() returns the number of bytes written on success and -1 on failure. pcap_sendpacket() returns 0 on success and -1 on failure. If -1 is returned, pcap_geterr() or pcap_perror() may be called with p as an argument to fetch or display the error text. SEE ALSO
pcap(3PCAP), pcap_geterr(3PCAP) 5 April 2008 PCAP_INJECT(3PCAP)
All times are GMT -4. The time now is 05:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy