Using DHCP and assigning to hardware MAC-address

Hi,
Is it possible for the DHCP functionality of the Airport Extreme Base to manually assign an IP-address to the MAC-address of a computer on the network?
This is a feature that I am missing a lot.
Thanks.

mbp, Welcome to the discussion area!
Is it possible for the DHCP functionality of the Airport Extreme Base to manually assign an IP-address to the MAC-address of a computer on the network?
No, this is not a feature available from an AirPort Extreme base station (AEBS).

Similar Messages

How do I open ports on my airport extreme and assign a fixed IP Address for a device connected to my network?

I recently had a security system installed in my house. One of the features is an EPAD which enables me to have a virtual keypad on my iphone, and computer to operate the alarm system. The technician was not familiar with Mac's and Airports. How do I open port 80 to 80 in my airport and assign a fixed IP address for the EPAD? Apparently this is what is needed to make this work.

There are three ranges of "strictly local" IP addresses reserved for local Network use:
192.168.xxx.yyy
172.16.xxx.yyy
10.xxx.yyy.zzz
What your Router does for you is to act as your agent on the Internet.Your requests are packaged up and forwarded on your behalf, and only when a response is expected is the response returned to your local IP address.
Directing Network Traffic to a Specific Computer on Your
Network (Port Mapping)
AirPort Extreme uses Network Address Translation (NAT) to share a single IP address with the computers that join the AirPort Extreme network. To provide Internet access to several computers with one IP address, NAT assigns private IP addresses to each computer on the AirPort Extreme network, and then matches these addresses with port numbers. The wireless device creates a port-to-private IP address table entry when a computer on your AirPort (private) network sends a request for information to the Internet.
If you’re using a web, AppleShare, or FTP server on your AirPort Extreme network, other computers initiate communication with your server. Because the Apple wireless device has no table entries for these requests, it has no way of directing the information to the appropriate computer on your AirPort network.
To ensure that requests are properly routed to your web, AppleShare, or FTP server, you need to establish a permanent IP address for your server and provide inbound port mapping information to your Apple wireless device.
To set up inbound port mapping:
1) Open AirPort Utility, select your wireless device, and then choose Base Station > Manual Setup, or double-click the device icon to open its configuration in a separate window. Enter the password if necessary.
2) Click the Advanced button, and then click Port Mapping.
3) Click the Add button and choose a service, such as Personal File Sharing, from the Service pop-up menu.

Get Hardware (Mac) Address through Applescript

Hi All,
How can I get Hardware (Mac) Address using applescript. Please tell me how can I do it. I have searched in the dictionary but I found nothing there.
Why I need it, I have developed some tool for InDesign & Quark User. I want to add the mentioned module in my application, so that as user will run the tool it will first validate the Hardware address, and if it match then application will run otherwise it will show a piracy message.
Thanks
Rajeev

>get if addr en0 failed, (os/kern) failure
Then you don't have an active interface. You can't use ipconfig to query an interface that isn't up.
You need to decide how you want to deal with this - you won't know in advance what interfaces the user may have active. For this reason, relying on the MAC address is inherently problematic. You might be better off using the system's serial number (which is less likely to change anyway):
<pre class=command>set serialNum to do shell script "system_profiler SPHardwareDataType| awk -F: '/Serial/ {print $2}'"</pre>

I am trying to use Labview and RP1210 compliant hardware to connect to a truck J1939 bus and receive messages.

I am trying to use Labview and RP1210 compliant hardware to connect to a truck J1939 bus and receive messages.
Specifically I am attempting to read data frames using the RP1210_READMESSAGE . am able to configure the hardware and send a message to the J1939 bus. . I think I have not configured something correctly. I can use the RP1210_SENDMESSAGE and see the message I have sent on the bus using CANalyzer When I use the RP1210_READMESSAGE I get the timestamp from a message and the return from the function sends back the correct number of bytes (the number matches the number of bytes I sent out plus four bytes from the timestamp). What I am having trouble with is actually receiving the data. I have had the same type of behavior from two different hardware (Vector CANcase XL and Nexiq USB Link), so I don't think the issue is vendor specific.
Has anyone been able to make the RP1210_RECIEVEMESSAGE function work correctly?
Thanks for any help

Thanks
I have already tried that. The links are the NI RP1210 wraper. The problem I am having is using labview to interface with the RP1210 layer. The RecieveMessage char*fpchAPIMessage this is the output which is a pointer to a cahracter array. In this variable I can receive the timestamp of the message but not the message. The retun showns the correct amount of bytes are aviaable (18 for a 8 byte message) but I can only get the 4 byte timestamp I think I have to dereference this pointer to view the data. I am not sure how to fix this.

If I use pages and numbers on a Mac can I save the documents as an extension that I can use on a PC?

If I use pages and numbers on a Mac mini can I then save the documents as extensions that can be opened on a PC?

You can save Pages documents as Word documents and save a Numbers document as an Excel file. In Lion you can go to File>Export and then save as Word or Excel.
I assume that there is a way to do it in SL or Leopard as well.

DHCP IP assignment for special MAC acroos VLANs

Hi,
I have one layer 3 3750 switch running DHCP for individual VLANs. for some special MAC address i want to assign special IP in each VLAN. Suppose there are 5 VLANs with 10.10.1.0, 10.10.2.0, 10.10.3.0 , 10.10.4.0 and 10.10.5.0 each with /24 mask. The special MAC is traveling between VLANs and i want to assign special IP in each network for that MAC.

When the DHCP server and client reside on the same LAN segment or VLAN and the client is unable to obtain an IP address from a DHCP server, it is unlikely that the local router is causing a DHCP problem. The problem is most likely related to the devices that connect the DHCP server and DHCP client. However, the problem may be with the DHCP server or client itself. Following the troubleshooting modules below should determine what device is causing the issue.Following URL would give a brief idea.
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a00800f0804.shtml

Using NAR to restrict access by MAC address

Hello All,
We have a solution where home users connect via ATM onto our network. Currenty their radius requests are passed onto Cisco ACS 3.3 and they are authenticated using RSA SecurID Fobs to an ACE server.
I am trying to look at an alternative to using a SecurID fob and restrict the end user's access based on MAC address.
I found this on the online documentation for ACS 3.3
"About Non-IP-based NAR Filters
A non-IP-based NAR filter (that is, a DNIS/CLI-based NAR filter) is a list of permitted or denied "calling"/"point of access" locations that you can use in restricting a AAA client. However, by entering an IP address in place of the CLI you can use the non-IP-based filter even when the AAA client does not use a Cisco IOS release that supports CLI or DNIS. In another exception to entering a CLI, you can enter a MAC address to permit or deny; for example, when you are using a Cisco Aironet AAA client. The format of what you specify in the CLI boxCLI, IP address, or MAC addressmust match the format of what you receive from your AAA client. You can determine this format from your RADIUS Accounting Log."
If I specify a clients MAC in any of the non IP NAR options (CLI, Port, DNIS)access is refused. I am using radius IETF and the only time I can see the MAC in the radius accounting logs is when I turn on the option to log cisco-av-pair. Nothing is being logged under CLI or DNIS, so I don't think I can restrict access based on MAC using a non IP NAR. Has anyone implemented what is referred to in the documentation above? Is it just applicable to cisco Aironet? Any ideas?
Thanks.

A NAR is a definition, which you make in Cisco Secure ACS, of additional conditions that must be met before a user can access the network. Cisco Secure ACS applies these conditions using information from attributes sent by your AAA clients. So it is not device specific.

DHCP Server with the strange MAC address at the same time. This MAC address is HEX IP address!

Server version: Windows server 2008 R2 Ent.
Structure of DHCP scopes: Two DHCP server 50% to 50% all allocation for per scopes.
Question: Sometimes the DHCP server
allocate the IP address at the same time to the a strange MAC address per IP address, the type is "DHCP/BOOT", it cause DHCP scopes out of space at some time point. We need clear up them manually.
I found strange MAC address in HEX is the IP address which the server allocated.
Someone meet the issues before, any solution for this ?
Thanks !
Client IP Address
Name
Lease Expiration
Type
Unique ID
10.199.190.0
10.199.190.0
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e3000
10.199.190.46
10.199.190.46
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e343600
10.199.190.59
10.199.190.59
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e353900
10.199.190.69
10.199.190.69
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e363900
10.199.190.74
10.199.190.74
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e373400
10.199.190.90
10.199.190.90
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e393000
10.199.190.101
10.199.190.101
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31303100
10.199.190.104
10.199.190.104
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31303400
10.199.190.110
10.199.190.110
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313000
10.199.190.114
10.199.190.114
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313400
10.199.190.117
10.199.190.117
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31313700
10.199.190.121
10.199.190.121
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31323100
10.199.190.138
10.199.190.138
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31333800
10.199.190.144
10.199.190.144
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31343400
10.199.190.153
10.199.190.153
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353300
10.199.190.156
10.199.190.156
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353600
10.199.190.157
10.199.190.157
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31353700
10.199.190.163
10.199.190.163
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363300
10.199.190.165
10.199.190.165
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363500
10.199.190.168
10.199.190.168
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363800
10.199.190.169
10.199.190.169
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31363900
10.199.190.174
10.199.190.174
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31373400
10.199.190.177
10.199.190.177
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31373700
10.199.190.184
10.199.190.184
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383400
10.199.190.188
10.199.190.188
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383800
10.199.190.189
10.199.190.189
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31383900
10.199.190.192
10.199.190.192
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31393200
10.199.190.197
10.199.190.197
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e31393700
10.199.190.201
10.199.190.201
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303100
10.199.190.202
10.199.190.202
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303200
10.199.190.209
10.199.190.209
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32303900
10.199.190.210
10.199.190.210
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313000
10.199.190.211
10.199.190.211
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313100
10.199.190.212
10.199.190.212
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313200
10.199.190.213
10.199.190.213
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313300
10.199.190.216
10.199.190.216
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313600
10.199.190.219
10.199.190.219
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32313900
10.199.190.222
10.199.190.222
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323200
10.199.190.225
10.199.190.225
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323500
10.199.190.226
10.199.190.226
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323600
10.199.190.229
10.199.190.229
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32323900
10.199.190.233
10.199.190.233
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333300
10.199.190.235
10.199.190.235
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333500
10.199.190.238
10.199.190.238
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32333800
10.199.190.240
10.199.190.240
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343000
10.199.190.242
10.199.190.242
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343200
10.199.190.243
10.199.190.243
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343300
10.199.190.246
10.199.190.246
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343600
10.199.190.249
10.199.190.249
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32343900
10.199.190.251
10.199.190.251
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353100
10.199.190.252
10.199.190.252
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353200
10.199.190.255
10.199.190.255
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139302e32353500
10.199.191.1
10.199.191.1
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3100
10.199.191.2
10.199.191.2
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3200
10.199.191.5
10.199.191.5
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3500
10.199.191.6
10.199.191.6
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3600
10.199.191.8
10.199.191.8
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e3800
10.199.191.13
10.199.191.13
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313300
10.199.191.14
10.199.191.14
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313400
10.199.191.15
10.199.191.15
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313500
10.199.191.16
10.199.191.16
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313600
10.199.191.17
10.199.191.17
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313700
10.199.191.18
10.199.191.18
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313800
10.199.191.19
10.199.191.19
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e313900
10.199.191.20
10.199.191.20
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323000
10.199.191.21
10.199.191.21
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323100
10.199.191.22
10.199.191.22
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323200
10.199.191.23
10.199.191.23
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323300
10.199.191.24
10.199.191.24
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323400
10.199.191.27
10.199.191.27
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323700
10.199.191.29
10.199.191.29
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e323900
10.199.191.30
10.199.191.30
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333000
10.199.191.31
10.199.191.31
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333100
10.199.191.32
10.199.191.32
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333200
10.199.191.33
10.199.191.33
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333300
10.199.191.34
10.199.191.34
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333400
10.199.191.37
10.199.191.37
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333700
10.199.191.38
10.199.191.38
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333800
10.199.191.39
10.199.191.39
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e333900
10.199.191.42
10.199.191.42
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343200
10.199.191.44
10.199.191.44
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343400
10.199.191.49
10.199.191.49
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e343900
10.199.191.52
10.199.191.52
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353200
10.199.191.54
10.199.191.54
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353400
10.199.191.56
10.199.191.56
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e353600
10.199.191.61
10.199.191.61
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363100
10.199.191.62
10.199.191.62
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363200
10.199.191.64
10.199.191.64
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363400
10.199.191.65
10.199.191.65
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363500
10.199.191.66
10.199.191.66
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e363600
10.199.191.70
10.199.191.70
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373000
10.199.191.72
10.199.191.72
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373200
10.199.191.73
10.199.191.73
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373300
10.199.191.79
10.199.191.79
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e373900
10.199.191.80
10.199.191.80
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383000
10.199.191.81
10.199.191.81
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383100
10.199.191.82
10.199.191.82
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383200
10.199.191.83
10.199.191.83
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383300
10.199.191.84
10.199.191.84
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383400
10.199.191.86
10.199.191.86
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e383600
10.199.191.90
10.199.191.90
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393000
10.199.191.91
10.199.191.91
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393100
10.199.191.92
10.199.191.92
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393200
10.199.191.93
10.199.191.93
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393300
10.199.191.97
10.199.191.97
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393700
10.199.191.98
10.199.191.98
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393800
10.199.191.99
10.199.191.99
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e393900
10.199.191.101
10.199.191.101
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303100
10.199.191.102
10.199.191.102
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303200
10.199.191.105
10.199.191.105
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303500
10.199.191.106
10.199.191.106
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303600
10.199.191.108
10.199.191.108
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31303800
10.199.191.112
10.199.191.112
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313200
10.199.191.115
10.199.191.115
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313500
10.199.191.116
10.199.191.116
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313600
10.199.191.117
10.199.191.117
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313700
10.199.191.119
10.199.191.119
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31313900
10.199.191.120
10.199.191.120
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323000
10.199.191.121
10.199.191.121
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323100
10.199.191.125
10.199.191.125
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31323500
10.199.191.133
10.199.191.133
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31333300
10.199.191.146
10.199.191.146
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31343600
10.199.191.158
10.199.191.158
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31353800
10.199.191.162
10.199.191.162
2014/8/5 10:07
DHCP/BOOTP
31302e3139392e3139312e31363200

Hi,
According your description, this may be caused by virus or malicious client.
Please try to perform a network capture on your DHCP server. Then find the device which send these malicious discover messages.
To download Network Monitor, please click the link below,
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
To prevent this issue, you may implement NAP Enforcement for DHCP.
Here is a checklist of configuring NAP Enforcement for DHCP,
Checklist: Configure NAP Enforcement for DHCP
http://technet.microsoft.com/en-us/library/cc772356(v=WS.10).aspx
Hope this helps.
Steven Lee
TechNet Community Support

Using javafx and awt together in MAC

I have read blogs about not using SWT and AWT libraries together in MAC systems. So, are their any constraints for JAVAFX and AWT as well ?
Please refer to this link.
I am having a similar case of writing an image to disk and I am using javafx, the line doesn't seem to work on my mac.
Message was edited by: abhinay_agarwal

The link you posted on SWT/AWT integration is irrelevant to JavaFX/AWT integration.
To learn abount JavaFX/Swing integration, see the Oracle tutorial trail:
JavaFX for Swing Developers: About This Tutorial | JavaFX 2 Tutorials and Documentation
As Swing is based on AWT, the tutorial trail is equally applicable whether you are integrating JavaFX with only AWT or with the full Swing toolkit.
In my opinion, there is little reason to integrate JavaFX with just the AWT toolkit as there is little of value that AWT would provide that JavaFX does not already provide.
JavaFX integrates fine with ImageIO to write files to disk, Oracle provide a tutorial for that (see the "Creating a Snapshot" section):
Using the Image Ops API | JavaFX 2 Tutorials and Documentation
//Take snapshot of the scene
WritableImage writableImage = scene.snapshot(null);
// Write snapshot to file system as a .png image
File outFile = new File("imageops-snapshot.png");
try {
ImageIO.write(
    SwingFXUtils.fromFXImage(writableImage, null),
    "png",
    outFile
} catch (IOException ex) {
System.out.println(ex.getMessage());

How can I verify my phone number to use FaceTime and iMessage instead of email address!?

My iMessage and FaceTime are both working, but it still says "Waiting for activation.." right under both the FaceTime and iMessage settings. Under the "Receive At" setting, my email address is entered in. When I press on my email address, it takes me to a page shows my Apple ID, my email address, and in gray it says "Vertifying" with my phone number also in gray. I am currently out of the country and am using wifi for my apps, iMessage, FaceTime, and checking email. Why does it still say waiting for activation even though I can use everything fine?

I want that to be my last option if I need to. I don't want to delete everything and update everything back over. Are the finished with updating the severs? Last night I was unable to sign in using my Apple ID to use FaceTime or iMessage, but now I am logged in, but I can't verify my number. My iMessages are going through with my email instead of my number

Using iPad and LogMein app with Mac Mini Server

Hello everyone, I'm new to the community and I would like to ask your opinions on something I'm considering.
I'm currently using a MacBook Air beyond its capabilities. I'm running a dual system via Parallels since some of my work programs are Windows based.
I'm planning to pass the MacBook Air down to one of my employees but I'm stuck on what I will purchase to replace it.
I like the new MacBook Pro, but I don't like the $2200+ price tag. So what I'm considering is buying a Mac Mini Server ($900) and setting it up in my office with a HDTV as a monitor because I use construction design programs and the laptop screen is just too small for large drawings. The Mac Mini also has 1TB storage vs 256GB on the MacPro. I already have an external disk drive so that's no issue either.
Also, since I still need mobile convenience, I'm considering downloading the "LogMein Ignition" app ($130) and using this to log in remotely with my iPad for complete access to all of my files and programs.
What are some pros and cons I should consider before making this move?
Thanks in advance for the help!
Kevin

> If your server is behind NAT, there is almost certainly no need for packet filtering and you should disable it.
I disagree, Linc. PF is very useful to block known bad IPs and brute force attacks, which are an hourly occurrence, especially on ssh. I use this PF configuration for OS X, which blocks brute force attacks, updates IP blocks from emergingthreats.net, and more. My logs and pf table "bruteforce" are full of attacks and blocked sites (sudo pfctl -t bruteforce -Ts). I also run snort on OS X and can see that the snort alert triggers are greatly reduced by simply blocking all these packets at the network layer.

Masking and Forwarding domain to mac address

Hope I have the lingo correct, but I have a domain address that is on all of my print material. When I developed my site in iWeb, I needed to have only that published domain name appear. I went to my host and had them turn on forwarding and masking, but I can't seem to get it all together to make it happen. Can anyone help and/or guide me?
Question #2: is there some magic to perform in order for my iWeb site to appear correctly in Windows/Internet Explorer and other venues. It seems to have some glitches in other internet software re appearance.
Thanks

I went to my host and had them turn on forwarding and masking, but I can't seem to get it all together to make it happen.
Could you provide your personal and .Mac urls so we can see what is going on?

Using fusion and sharing files with mac

I am getting a Mac Airbook and am going to be running Fusion from VMWare. I have an external Western Digital drive that I want to use to transfer my files to the Mac. Two questions:
1. Will the Passport software or at least the files - be recongnized by the Mac?
2. Does the Mac share the files with Fusion or do I need separate folders?

Welcome to the Apple Support Communities
1. Your Mac will recognize the external drive without any problem if it's formatted with FAT, NTFS or exFAT. Note that OS X can't write into NTFS drives.
2. Your Mac can share files with a virtual machine if you install VMware Tools onto the virtual machine

Using Parallels and Blackberry on a Mac

Hello all,
I am running a new MacBookPro with OS 10.6.x and Parallels 5.0 to emulate Windows 7. I am trying to figure out if I can sync my Blackberry to my Outlook email, calendar and address book on the Windows side, as it is tied to my office Exchange Server. The issue is that the company has not subscribed to Microsoft's "Enterprise Server", which means that my connections would be through the USB... and RIM states that they don't support connections through a virtual USB (virtual machine).
I'm sure someone out there has figured out how to do it. Right now, I can connect, see the Blackberry and even did a sync of sorts, but it keeps crashing midway through the calendar sync and throwihg an error: 0x80040fb3.
Any ideas are appreciated!

Questions regarding Parallels should be posted on the Parallels forums:
http://forums.parallels.com

Creating InfoObjects using program and assignment under InfoObject Catalog

Hi All,
There is a FM BAPI_IOBJ_CREATE which can create an Infoobject but the problem is it is not having provisions to get assigned to a particular " Infoobject Catalog".
Is there any other program or some way by which we can do it using the same FM.
Thanks in advance

To assign your Infoobject you must use a separate BAPI:
BAPI_IOBC_CHANGE
This function module changes an existing InfoObject catalog. Enter all the InfoObject catalog properties in the DETAILS parameter
If the Catalog doesn't exist you have another BAPI:
BAPI_IOBC_CREATE
This function module creates a new InfoObject catalog. You have to give all the InfoObject catalog properties in the DETAILS parameter
Regards,
Sergio

Using DHCP and assigning to hardware MAC-address

Similar Messages

Maybe you are looking for