Unable to wake emacs across subnets

We have several emac labs w/ ard active on them, however, we are unable to wake them up from our central office location. If the client is available we can observe, control and just about anything else we need to do to them. Our biggest issue is that we can't wake them up across subnets. We also have a mini running server 10.4.7 as a task server out there...any ideas

First, make sure that "wake on network administrator access" is active in the Energy Saver -> Options on your clients.
If it is, try WakeOnLan or WakeOnMac and see if either of those work. If those don't work either, then the routers on your network are probably not correctly passing the necessary packet.
Hope this helps.

Similar Messages

Wake on LAN across subnets

Is there a way to get Zenwork's wake-on-lan feature to work across subnets?
I am not a LAN administrator so pardon any ignorance you see in my
question.
Zenwork's wake-on-lan function won't work on our LAN because our switches
are set to not allow forwarding of subnet-oriented broadcasts, which is a
generic requirment for zenworks wake-on-lan function to work. Our security
folks say enabling this on the switches is not an option because it
introduce a security vulnerbility. I find it strange that there wouldn't
be a solution for this by Novell/Zenworks considering that multiple
subnets, switches, and security considerations are usually a component of
all networks which zenworks is specifically targeted for in the first
place.
Thanks

Originally Posted by Marcus Breiden
On Thu, 07 Sep 2006 22:52:59 GMT, [email protected] wrote:
[color=blue]
it is the only way though.. that's how any WOL software works.. they can
limit the packets comming from either your c1 wks or the zenworks server
though.. otherwise you would require one server per subnet
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
Edu-Magic.net, deceased
Exactly, and this is the best choice. Make "Replication Servers" in each subnet, is very simple. U can use a Windows machine or SuSE, both without installing zenworks. Only registering them as servers satellites. You must install the agent (logically, hehe).

TS1367 My MacBook Pro when in sleep mode display turns black unable to wake. When using the mouse it goes across screen like using an eraser and finding the middle of screen to get to the password area to turn back on.

really have a hard time when leaving the computer on when attending other matters in the house. When returning, the screen is completely black and unable to wake(?) by touching the mouse or touch pad to put my password and be able to use the computer. When I move the mouse pad looks like I am using the eraser like in photoshop and it clears the screen little by little. Now I am able to point to the middle of the screen and erase the area where the password is in order to get to the screen and use the computer again. Anyone else having this problem? Took the laptop to the apple store near home and they told me there is nothing that can be done and I have to wait untile the new operating system, Mountain Lion comes out and supposedly this will fix the problem. HELP!!!!

I was so frustrated I call the Apple Tech Support and they walked me through. It has been doing great. The screen still turns black but now, when I touch the mouse or touch pad, I get the password prompt. The Apple Store did not help but talking the the Apple Tech has helped a lot. Thank you.

Unable to ping across subnet

hi
i have a solaris system
hostname sun
router (IP) 10.xx.xx.1
IP 10.xx.xx.20
network id 10.xx.xx.0
mask 255.255.255.0
where problem is
i can't ping from solaris machine(sun) to any PC across the subnet ( with IP as well as name).
resolution
--> /etc/defaultrouter is in order
--> network card is properly setup and running
--> can ping any system on local subnet including router(with IP ! DNS is across the subnet).
--> can ping from other PC's(win) on same subnet to systems across subnet using same default gateway settings
( that is routing settings at router are okay) .
--> netstat -r (shows following output )
sun% netstat -r
Routing Table:
Destination Gateway Flags Ref Use Interface
10.xx.xx.0 sun U 3 2460 hme0
224.0.0.0 sun U 3 0 hme0
default 10.xx.xx.1 UG 0 37756
localhost localhost UH 0 6502 lo0
sun%
--> /etc/netmasks
10.0.0.0 255.255.255.0
--> it takes unreasonably long time to set default interface for multicast during boot.
any suggestions where the problem could be.
thnx
garry

Hi garry
Yes you cannot ping with name unless you dont include that system's name and ip in the host file.
Due to the following reasons, you cannot ping ip across the subnet :
1. The pinging ip may be in a different vlan for which you dont have any access.
2. The default gatway has to be added which is accessable to other subnet also.
To over come your problem :
sample diagram of your problem
sub net 1- - - - - - - - - - - - - - - -
you are here |
sub net 2 - - - - - - - - - - - - route - - - - -dns / internet
|
sub net 3- - - - - - - - - - - - - - - -
is this n/w diag ok.
still you have any problem check the ACL of the router.
Regards
Sridhar M

Connect mac client to mac printer share across subnets

I need to share printers from a Mac. I need to connect
Mac clients on different subnets to the Mac shared printers. I installed
a Mac mini, connected to printers via HP JetDirect Socket (port 9100), and
shared them. I was able to print from the Mac mini, and connect Mac
clients on the same subnet to the shared printers with Bonjour and print.
I moved the Mac mini to its intended location on another subnet. I
immediately learned that Bonjour does not publish services across
subnets. I could not find documentation on how to connect to a Mac shared
printer across subnets, but I did find some third party documentation (only some incomplete
documentation from Apple) on how to implement DNS-SD Service Discovery. I
enabled DNS-SD and was able to publish the printer shares across subnets, but I
was still unable to connect to the printer shares from a Mac client. I
found some third party documentation (none from Apple) on how to manually connect to a Mac
printer share by specifying the IP address of the server, specifying the CUPS
default IPP protocol, and the print queue name. I was unable to connect
to the shared printers. I receive ping replies from my Mac mini, and port
scan reveals that port 631 for IPP, CUPS default, is open. Printer
sharing is configured so everyone can print. I am able to connect to the Mac
mini with VNC Screen Sharing. I don’t see how this can be a network
issue.
Macs don’t seem to like to connect to our Windows
shared printers because of our PaperCut software, and connecting Mac clients to
Windows printer shares and authentication is beyond the average user,
exacerbated by Macs not behaving the same as Windows when bound to an Active
Directory domain.
I called Apple support, they escalated to Apple Enterprise
support. Apple Enterprise support said they couldn’t help me beyond a
single network with no subnets, but Apple Engineering might be able to solve
the problem for $695.
Why do I need to pay $695 to learn how to connect Mac
clients to Mac shared printers, something that should be easy and intuitive and
have documentation readily available? Windows printer sharing is easy and
intuitive and documentation is readily available, and services are published
across subnets without have to implement DNS-SD.

Thank you for your reply. I followed the instructions in the sybaspot.com site and in some of the included references to set up DNS-SD. DNS-SD worked, but I couldn't connect the Mac client to the Mac shared printers.
I also found http://www.papercut.com/products/ng/manual/ch-mac-printing-10-8-9.html#ch-mac-pr inting-10-8-9-sharing-printers.
I expanded my search and found this: http://support.apple.com/kb/PH13940, last modified May 8, 2014. I started work on my project February 2014. Apple Support could have told me about this document.
PH13940 says: "The computers must be on the same local network as your Mac". Apple must not consider multiple subnets one network.
PH13940 says: "Printer sharing is for printers attached directly to your Mac. You don’t need to share network printers, because they are already shared on the network."
Apple must define "network printers" as any printer with a network interface. Microsoft defines network printers as printers shared by another computer. TCP/IP ports are local ports on a Windows computer, so TCP/IP connected printers are local printers that can be shared. Multiple users on a Mac all see the same connected printers. Multiple users on Windows all see the same local printers, but network printer connections can be different for each user.
Apple must not see any value in accounting for printing and assigning the cost to the user or department. We need to account for printing and cannot have any users bypassing the system by printing directly to printers. I have created Access Control lists on the printers to limit connections to the specific IP addresses of our print servers.
The documents about setting up DNS-SD and IPP connections must have assumed USB connected printers on a Mac. The odd thing is that I was able to share a network printer from the Mac mini when the client Mac was on the same subnet. Is PH13940 wrong?
I am Microsoft Certified Systems Engineer 1999 and Apple Certified Technical Coordinator 2013.

Problem With PXE Across Subnets

I'm having a problem with PXE across subnets. The workstation boots,
finds the dhcp server, finds the tftp server, downloads linux.1 and
linux.2 with no problem. It is unable to download linux3.tgz, however.
I've tried two different zen servers. I can tftp the file from either
zen server in windows with no problem. I can tftp it from maintenance
mode if I use a workstation as a tftp server. I can tftp it in PXE on
the same subnet with no problems.
A packet trace on the workstation shows that it gets so far into the
download and then begins getting ICMP 'destination unreacable' packets
from the server with the 'port unreachable' flag set.
It sounds as if the server is closing the conversation on that port.
Can anyone shed any light on this for me?
Dave Thomas
Rivercrest Technologies, Inc.

Could you send me that trace? I would like to have a quick look
Ron
[email protected]
<[email protected]> wrote in message
news:iNOie.234$[email protected]..
> The source address is the zen server. I'm relatively certain there is
> not routing issue because I can tftp the file from windows with no issues
> etc. Also there are a lot of other services crossing the subnets that
> would fail if there is a routing issue.
>
> The 'port unreachable' flag seems to indicate that the zen server has
> stopped listening on the port that is being used for the transfer.
>
> Dave Thomas
>
> > Where do these ICMP "destination unreacable" come from? could there be a
> > routing issue to get to the imaging server?
> >
> > Ron
> >
> > <[email protected]> wrote in message
> > news:[email protected] oups.com...
> > > I'm having a problem with PXE across subnets. The workstation boots,
> > > finds the dhcp server, finds the tftp server, downloads linux.1 and
> > > linux.2 with no problem. It is unable to download linux3.tgz,
> however.
> > >
> > >
> > > I've tried two different zen servers. I can tftp the file from either
> > > zen server in windows with no problem. I can tftp it from maintenance
> > > mode if I use a workstation as a tftp server. I can tftp it in PXE on
> > > the same subnet with no problems.
> > >
> > > A packet trace on the workstation shows that it gets so far into the
> > > download and then begins getting ICMP 'destination unreacable' packets
> > > from the server with the 'port unreachable' flag set.
> > >
> > > It sounds as if the server is closing the conversation on that port.
> > >
> > > Can anyone shed any light on this for me?
> > >
> > > Dave Thomas
> > > Rivercrest Technologies, Inc.
> > >
> >
> >
>

Manage machines across subnets?

What steps do I need to take to be able to manage clients across subnets? I need to be able to wake clients that are not on my local subnet (my office is in one subnet and the clients are distributed all over a university campus with subnets that correspond to buildings). Is there anything that I can do to make that happen? My admin machine is using ARD 2.2 on Tiger.2 and the clients are ARD 2.2 Client on Tiger.2. I used to be able to wake the machines to gain access in the 2.0 version of ARD, but not anymore... Help! Please!!!
Thanx in advance!

Waking a system requires that the router(s) pass Directed Broadcast, something most network administrators don't want to allow. If Directed Broadcast is blocked, there's no way any software can get the packet through to wake a sleeping system. Perhaps the network admins have made some changes that now block Directed Broadcast.
If so, and you can't get your network admins to turn that on, the only solution will be to set your systems not to go to sleep except for the monitors.

Unable to wake screen using magic mouse or trackpad after installing magic mouse

Dear Everyone,
I am using mbp 15 inch early 2011 with 2 GHZ intel i7 processor and a 4gb ram. I would like to tell you that i have installed the mac os x lion and quite happy with the improvement. however, there are same changes which i am not sure whether it is that my mac that causeing theproblem or the bug from the lion itself. i am unable to wake my mbp screen using my magic mouse or trackpad after installing lion. i believe that my mbp has not really enter sleep mode as i dont see the sleep indicator at the bottom right corner flickering. i also believe that it is only the screen that goes to sleep while the hard disk is not. Normally a single swing of the magic mouse or a single swipe of the trackpad will normally wake the screen. in order to wake the screen now is only to click on the magic mouse or trackpad. furthermore, scrolliing page using magic mouse also become unusual after installing the lion. does any of u happen to come across these problems as well? Is there any other way to downgrade to snow leopard back? (i ask this in case that this issue really cannot be fixed). Please help me on this issue. Thank you very much for taking your time to read and reply this thread.
Moonbasher (henry)

First, Lion does not wake on mouse or trackpad movement, only clicks or keyboard presses. This is presumably to avoid waking the computer from display or full sleep accidentally, and is just how Lion works. It's going to take some getting used to, personally, but I've noticed my mac hasn't woken up on it's own. Apparently moving about my apartment moves the mouse enough that Snow Leopard used to wake the iMac. This is not a glitch, and unfortunately, a downgrade is a complicated matter, involving erasing the HD entirely, and restoring from a backup created in Snow Leopard and not used with Lion at all, or manually importing important bits of data, as libraries upgraded by new versions of Mail, iCal, etc will not be compatible with the old versions.
In terms of your mouse scrolling, describe it in a bit more detail; Lion introduces "natural" scrolling, where instead of the mouse wheel moving the "window" over the contents, it moves the contents through the window, like scrolling on an iPhone or iPad. In other words, think of your finger on the mouse as pressing on the page you're looking at and dragging it upward through the field of view. I remember long ago thinking my very first scrolling mouse was backwards, and then adjusting to "down is down, up is up". If this is the behavior you're experiencing, this also is the way Lion works. This, however, can be changed in the mouse or trackpad preference pane in system preferences. Simply deselect "natural" scrolling.
In a more general sense, its usually not a good idea to do a major software upgrade on your primary machine unless you're willing to deal with some zero-day glitches. It sounds like the issues you're having aren't actually glitches, and you should be happy for that, but in the future, you might want to wait a few weeks for other users with more experience with major OS launches to find those bugs and point them out to the community for Apple to fix. In terms of an OS launch, I think this has been absolutely one of the best. I'm seeing very few major glitches resulting in lost data, few things that would really destroy my personal workflows, and compatiblity issues with other products seems to be well documented or negligible. It's also a bit hasty to assume that mere hours after launch Apple would have any ability to fix ACTUAL problems with the OS. My recommendation would be to get used to the change; having to click the mouse at least means you'll never accidentally wake your machine bumping against your desk.

Wireless keyboard/mouse unable to wake imac

I am currently using a iMac G4, D-Link DBT-120 vers B3 and have been unable to wake computer using wireless keyboard or mouse. Once computer is awake (using wired mouse) keyboard is fine. I have tried updating bluetoothversion but am told it is current, firmware tells me it has errors and to try again. In bluetooth preferences allow to bluetooth device to wake is light grey. I have followed advice in reference article about this issue and downloaded update of 10.4.6. Since the update I have not discarded .plist as suggested in anearlier discussion. Any thoughts or am I to have some wires across my desk for the mouse?
Thanks
Mheader

Hi again, Mheader —
Please accept a (belated) welcome to Apple Discussions.
Sorry for not responding to your post in diga's "Bluetooth Keyboard - Wake Up Powerbook doesn't work anymore" thread. I appreciate your initiating a new thread, so we can focus on your situation. "Any thoughts or am I to have some wires across my desk for the mouse?"Let's hope we can make some progress toward a solution...
(1) When you say, "... firmware tells me it has errors and to try again" —— I think it's likely that this is the problem, or part of it. I don't have a D-Link DBT-120 adapter (your is one of the correct models), so I have to depend on the experience of others about (part of) this issue. Here are the steps for updating its Bluetooth firmware:
(a) Download Bluetooth Firmware Updater 1.2 [11/23/04]. Note that — as with any software installation — it's very important that the process isn't interrupted; don't work on any other activities while it runs, ensure an uninterrupted power supply, and make sure that Energy Saver is set to Sleep = "Never" while the installer is running. The download will place a file named BluetoothFWUpdate1.2.dmg into your Downloads folder or wherever your browser is set to save downloads.
(b) When you open this, and double-click to "launch" the enclosed BluetoothFirmwareUpdate1.2.pkg, it acts a little differently than many software update installations — there's an extra step. This (the installer actually runs) creates a file in your /Applications/Utilities/ folder named Bluetooth Firmware Updater. At this point, you're done with the .dmg image and can dismount it.
(c) Now double-click to "launch" the Bluetooth Firmware Updater application that I've just described. This begins the actual upgrade process = "flashing" the Firmware. (The Apple Installer runs again.) Since you're using a D-Link DBT-120 Rev. B3 adapter because Bluetooth isn't "built-in," the adapter needs to be plugged directly into one of the USB ports on your iMac (not a hub). Since the Firmware Update is only "flashing" the module or adapter, you should "disconnect" your mouse and keyboard during the process. The installer itself may provide an alert and do this for you. (It did this when I updated my internal module's firmware.) Follow on-screen instructions from here.
(d) As I understand it, installing the firmware on an adapter may take a very long time — I've even seen it suggested that you let it run overnight.
(e) You should clearly be able to see that the update has been successful: if an alert that the device wasn't updated appears, the process wasn't successful. If this occurs, participants with a lot of experience with adapters suggest "try, try again." (Here's an example.)
(2) You may want to read through Wake This Computer Option Is Shaded and Wake This Computer Option Is Shaded, Part 2 — which are examples where several folks were able to solve similar problems using this approach.
If the firmware update is successful, but this problem remains...
(3) Try USB device troubleshooting: USB controller problems caused by some non-compliant devices can sometimes cause the problem you're experiencing.
I hope this helps!
Please post back to share how it goes.
Regards,
Dean
[2,258 ⊥ 3,635]

Solution to use Airprint across subnets wired/wireless

A lot of companies are trying to figure out how to setup airprint to print
in the workplace, wired+wireless across subnets.
We finally figured it out with some DNS magic and a CUPS server.
I have documented the solution at a live document hosted at
http://sites.google.com/site/iwastepaper/
Hopefully it helps a few folks.
<Edited by Host>

You will want to make sure your APs can route from where ever you install them to the WLC managment address.
How APs find the controller can happen a few different ways:
1) DNS A record
2) Layer 2 broadcast (which you seen already)
3) IP Route Forward
4) DHCP Option 43
5) Manual Prime the AP
Most folks lead with option 43.
http://www.my80211.com/cisco-wlc-labs/2009/7/4/cisco-dhcp-option-43-configuration-nugget.html
if you check the config guide you will explain the other processes.

NetBoot across subnets with a bootpd relay

Hello Apple Community!
I've got 4 subnets at my school, each with various Macs around campus. I have a Mavericks server on each subnet currently, each with their own NetBoot images. It's a pain to keep everything updated. I can get a single client Mac (pre-2011) to boot across subnets using the bless command, but that's not really a viable solution for us to run a bless command on each client every single time we want to netboot. So far, the solution has been just to have dedicated netboot servers on each subnet, but I know there has to be a better way.
This article (OS X Server: How to use NetBoot across subnets - Apple Support) describes three different methods for netbooting across subnets, but two of them are not really viable for us. Those involve reconfiguring the network to allow BootP data to pass across subnets or configuring one server with multiple network connections, one for each subnet. However, option #2 describes configuring a bootpd relay. Based on my reading, this sounds like exactly what I need. However, I can't find any good documentation to walk me through setting it up.
I've thoroughly read the bootpd man page, which has had me editing the /etc/bootpd.plist on multiple servers. This hasn't gotten me very far. My clients still don't see the remote NetBoot server. It seems like the relay is supposed to redirect broadcasts from the remote Netboot server, through a local NetBoot server to the client. But I have no idea how to make this work.
Could someone please give me more guidance on what I'm supposed to be doing here? I'd like to host a single NetBoot server and have any client on any subnet be able to option-boot to see the NetBoot startup options (I have multiple NetBoot images, from Apple Service Toolkit to DeployStudio and Mavericks/Yosemite installers in between). Even if I could get it to just netboot to one default source (AST), I could deal with that. I'm also happy to host multiple NetBoot servers, but with all my NetBoot images in one location. I'm stumped in this multiple subnet environment and I need help. Please help.

Thanks again for your feedback. I had forgotten I left the "tftp://" on the IP address. Though, I've tried that multiple ways, starting with IP only. Also, per the bootpd man page (https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/bootpd.8.html), <allow/> and <deny/> are lists for MAC address allowances and when nothing is defined everything goes through. These are there by default, though I will remove them and see what happens. Also, according to the man page, bootp_enabled enables on all connections when a boolean is set rather than an array. Though I will still change this also and see what happens. The array that comes after the netboot_disabled key is auto-generated by NetInstall when you turn the service on in Server.app.
Essentially, that plist comes from a fresh activation of NetInstall. I deleted the previous .plist, rebooted the server and when I turned on NetInstall, that's what was created, plus my bootp modifications.
All that said, you said that you assumed I started the relay with the 'debug & logging' options enabled. I haven't started the relay in any active sense. So far, I've just been modifying this .plist, and rebooting a bunch of times, but that's where I seem to get lost. Is there a way to actively "start" the relay? I'd love to look at these 'debug & logging' options. As for the 'Startup Disk' prefs on the client Mac, they do not show any significant change. Basically, they just don't see the remote server as a startup option. I have not gleaned any pertinent info from console, though I'm not sure I know what I'm looking for.
On a side note, I had a wild hair to try something different. I set my local subnet's server to look at a NetBootSP0 folder that was actually a symlink to a NetBootSP0 folder that was mounted as a file share from the remote NetBoot server. This really looked like it might work. When you boot the client, it saw the startup volumes from the remote server. However, upon boot, it doesn't seem to make the connection and winds up booting back to the internal hard drive. It was worth a try...

Jumpstart across subnets

Hello
I am having trouble configuring my jet toolkit to boot across subnets.
It works fine in the same subnet but when it goes across subnets it seems to lose the default router for the client.
{0} ok boot net:dhcp - install
Resetting...
POST Sequence 01 CPU Check
POST Sequence 02 Banner
LSB#00 (XSB#00-0): POST 2.12.0 (2009/09/09 15:17)
POST Sequence 03 Fatal Check
POST Sequence 04 CPU Register
POST Sequence 05 STICK
POST Sequence 06 MMU
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory
POST Sequence 09 Raw UE In Cache
POST Sequence 0A Floating Point Unit
POST Sequence 0B SC
POST Sequence 0C Cacheable Instruction
POST Sequence 0D Softint
POST Sequence 0E CPU Cross Call
POST Sequence 0F CMU-CH
POST Sequence 10 PCI-CH
POST Sequence 11 Master Device
POST Sequence 12 DSCP
POST Sequence 13 SC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Error CPU Check
POST Sequence 17 System Configuration
POST Sequence 18 System Status Check
POST Sequence 19 System Status Check After Sync
POST Sequence 1A OpenBoot Start...
POST Sequence Complete.
Sun SPARC Enterprise M4000 Server, using Domain console
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights reserved.
OpenBoot 4.24.12, 32768 MB memory installed, Serial #91113890.
Ethernet address 0:21:28:6e:49:a2, Host ID: 856e49a2.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@0,600000/pci@0/pci@8/pci@0/network@2:dhcp File and args: - install
1000 Mbps full duplex Link up
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
I have entered the router info in the defaultrouters file
kenapps08g:global# cat defaultrouters
# You can use this file to allow templates to be auto-populated with additional
# default router settings, especially useful for managing large numbers o
# server templates.
# Format:
# <subnet> <mask> <default router>
# Example:
# 192.168.1.0 255.255.255.0 192.168.1.254
10.0.1.0 255.255.255.0 10.0.1.1
10.0.2.0 255.255.255.0 10.0.2.1
10.0.3.0 255.255.255.0 10.0.3.1
</opt/SUNWjet/etc>
kenapps08g:global# more dhcp.conf
# This file is used to control some of the options for the DHCP boot
# environment
# DHCPDIR: The replies sent out by DHCP are limited in length; we use
# this directory to create symlinks to the actual Solaris
# media dirs; the intention is to keep paths short!
# N.B. If you change this, please make sure the new area is
# properly shared in /etc/dfs/dfstab
DHCPDIR="/dhcp"
# DEBUG_DHCP keep temporary files around after client_allocate_pdhcp.SunOS
# has run. Non-null invokes debug
DEBUG_DHCP=""
# REMOTE_DHCP define the hostname of the Sun server running Sun's DHCP daemon
REMOTE_DHCP="kenapps08g"
# REMOTE_DHCP_METHOD define what method to use to propogate. ssh is currently
# supported and requires you set up a trust relationship
# between this server and it.
REMOTE_DHCP_METHOD="ssh"
# DHCP_FORMAT Which dhcp server type is supported. SUN is currently supported,
# however, ISC is still in development. If REMOTE_DHCP is set,
# you must set DHCP_FORMAT to SUN. Valid entries are "SUN"
# and "NOOP". NOOP can be used if you are manually setting
# up your own DHCP server with the required parameters.
DHCP_FORMAT="SUN"
kenapps08g:global# more dhcp_servers
# You can use this file to define the DHCP servers responsible
# for different subnets.
# This is only required if you have multiple DHCP servers.
# If a match is found, the settings in this file will be used,
# otherwise the DHCP server defined in dhcp.conf will be used.
# Format:
# <client network> <client mask> <dhcp-server-name> <dhcp-server-tyep> <method>#
# <dhcp-server-name> overrides the REMOTE_DHCP setting
# <dhcp-server-type> overrides the DHCP_FORMAT setting
# <method> overrides the REMOTE_DHCP_METHOD setting
# Example:
# 192.168.1.0 255.255.255.0 dhcpserver1 SUN ssh
10.0.1.210 255.255.255.0 kenapps08g SUN ssh
10.245.64.10 255.255.255.0 lisjump01g SUN ssh
kenapps08g:global# more jumpstart.conf
# This config file defines the jumpstart specific variables.
# Version: $Revision: 1.8 $
# Last Updated; $Date: 2009/04/15 12:41:29 $
# Location of the additional media for patches and packages:
# These paths should be URI form e.g. nfs://<serverip>/<path> or <path>
# Currently only PKG_DIR and PATCH_DIR can be on a remote NFS server.
# If they are just <path>, the appropriate address of the JumpStart server
# will be added.
# N.B. if the media location is on a different server, please ensure it is
# routable from the client !
# You can specify an alternative location for where the client can
# NFS mount the /opt/SUNWjet directory. Simply provide the IP address
# of the server or the IP address and path on the remote server
# in the JS_CFG_SVR variable. However, this MUST be mounted
# on the JET server in /opt/SUNWjet as well, and be rw by root.
# e.g. JS_CFG_SVR="nas_server1" or
# JS_CFG_SVR="nas_server1:/unixshare/SUNWjet"
# When using an NFS server for images, even though the JET server
# MUST have the boot media locally, it is possible to have the client
# net boot from the remote NFS server. By default, clients will boot from
# the JET server. To override this, set JS_CLIENT_BOOT to "remote".
JS_Default_Root_PW=M4JVhMPO9CaQw
JS_BUILD_DIR=/var/opt/sun/jet
JS_PKG_DIR=/vendor/jumpstart/pkgs
JS_PATCH_DIR=/vendor/jumpstart/patches
JS_CFG_SVR=
JS_SOLARIS_DIR=/vendor/jumpstart
#JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30"
JS_DHCP_VENDOR="SUNW.Sun-Fire-T1000 SUNW.Sun-Fire-V240 SUNW.SPARC-Enterprise"
#JS_CLIENT_MANAGEMENT="bootp"
JS_CLIENT_BOOT="local"
kenapps08g:global# more server_interfaces
# You can use this file to help JET determine the correct IP address to
# use when it is configured on multi-homed hosts. It is also used to
# define which servers on different subnets whcih can be used in conjnction
# with dhcp.
# As we don't know which side of the server clients will connect through,
# you can set things up here - especially useful if this server is not
# a router either.
# Format:
# <client network> <client mask> <our preferred ip address>
# Example:
# 192.168.1.0 255.255.255.0 10.0.0.1
10.245.64.0 255.255.255.0 10.0.1.210
10.0.3.0 255.255.255.0 10.0.1.210
It has to be a defaultrouter setting somewhere because I can ping the server during jumpstart only from its own subnet.
during the dhcp part it looks like the traffic is coming thru and it gets its offer then during the tftp part no traffic comes across anymore
I am stuck on this one.
thanks

this file is in place with the interfaces
kenapps08g:global# cat defaultrouters
# You can use this file to allow templates to be auto-populated with additional
# default router settings, especially useful for managing large numbers o
# server templates.
# Format:
# <subnet> <mask> <default router>
# Example:
# 192.168.1.0 255.255.255.0 192.168.1.254
10.0.1.0 255.255.255.0 10.0.1.1
10.0.3.0 255.255.255.0 10.0.3.1
183.1.2.0 255.255.255.0 183.1.2.209
</opt/SUNWjet/etc>
kenapps08g:global# cat server_interfaces
# You can use this file to help JET determine the correct IP address to
# use when it is configured on multi-homed hosts. It is also used to
# define which servers on different subnets whcih can be used in conjnction
# with dhcp.
# As we don't know which side of the server clients will connect through,
# you can set things up here - especially useful if this server is not
# a router either.
# Format:
# <client network> <client mask> <our preferred ip address>
# Example:
# 192.168.1.0 255.255.255.0 10.0.0.1
10.0.1.0 255.255.255.0 10.0.1.210
10.0.3.0 255.255.255.0 10.0.1.210
183.1.2.0 255.255.255.0 10.0.1.210

I've connected my macbook pro (os 10.6.8) to an external display, but it will not go into clam shell mode! When I close the lid the laptop goes to sleep, and I am unable to wake it using the external keyboard or mouse.

A rundown of what I've tried:
Adjusting energy settings to try to prevent sleep
Pluging the USB keyboard and wacom tablet directly into the laptop (as opposed to a usb hub)
My laptop's power cable is connected
My display (a Vizio TV) is recognized in the System Preferences panel
I'd been using this TV for about a year with my older Macbook Pro (OS 10.5.8), though using a different wireless keyboard and mouse
***Update: The issue seems to lie with the keyboard and wacom tablet. I am trying to use a wireless Case Logic keyboard (with dongal) and wired wacom tablet to wake the Macbook Pro in clamshell mode. To experiment, I tried using my Logitech wireless keyboard & mouse set (also dongal) that I had been using before and it wakes the computer without any problems! However, I really need to be able to use my wacom tablet. If I switch to the tablet after waking the computer using the Logitech keyboard & mouse it works, but once the computer sleeps it won't work anymore. I could keep switching back and forth I suppose, but it's sort of a pain. There has to be an easier way! Any ideas why the wired wacom tablet is unable to wake the computer in clamshell mode?
Thanks!

So your keyboard or mouse won't wake the Mac when you close the lid correct? Try resetting the SMC and pram
Shut down the computer.
Disconnect the MagSafe power adapter from the computer, if it's connected.
Remove the battery.
Press and hold the power button for 5 seconds.
Release the power button.
Reconnect the battery and MagSafe power adapter.
Press the power button to turn on the computer.
Resetting NVRAM / PRAM
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.

Not able to use Apple tv across subnet

Hi Guys,
I have made a test setup which contain an cisco 2600 router, apple tv and Macbook pro with 10.9.2 OSX. Its pretty simple setup. One interface(Fa0/0) of the cisco router is connected to apple TV via ethernet cable in an network 10.0.1.0/24 and another interface (Fa0/1) is connected to Macbook pro in network 10.0.2.0/24 via ethernet cable. Apple TV network ip is 10.0.1.2 whereas macook ip is 10.0.2.2. I am able to succesfully ping from macbook to apple tv, but not able to discover apple tv at all on my macbook. I tried every method, allowed udp port 5353 on router for bonjour discovery , but still no luck. Can any gentleman help me on this?

Yes, we can mirror it across subnet. Thats what I am trying to figure out. People had done this eariler.

CUPS printer sharing across subnets?

I am trying to set up my local network printer so that everyone in the house can print from it. However I have two subnets in the house and I don't see how to connect to the Linux server through a Windows 7 client.
My network is like so:
Upstairs: [Modem] <=eth0=> [Router 1] Subnet of 192.168.0.*
[Router 1] <=wlan0 client mode=> Downstairs: [Router 2 with dd-wrt firmware] Subnet of 192.168.1.*
[Router 2] <=eth0=> CUPS server/PC with USB printer attached IP address of 192.168.1.1XX
This works: [Router 2] <=ath0.1 virtual wireless ESSID=> Windows 7 Laptop
This doesn't: [Router 1] <=wlan0=> Windows 7 Laptop
I tried
sudo cupsctl --share-printers --remote-any && sudo systemctl restart cups
on the host PC, but the W7 clients can't connect across subnets. Is there anyway to set it up so it can? They can easily connect to the ath0.1 network and then print, but it's inconvenient for them. The Windows users spend most of the time upstairs, and not downstairs, so they are usually connected to the wlan0 network.
I have the option of putting [Router 2] into client bridged mode so it shares the same subnet of [Router 1], however I can't seem to set it up properly and I run into problems. It is important to have the ath0.1 network downstairs, and I am unsure that client (bridged) mode will allow for the virtual interface.
I do not have Samba installed but I am considering trying that, but a simpler solution would be appreciated.
*Edited for further clarification & error fixing.
Last edited by felixculpa (2012-12-27 20:03:51)

DiverDoc wrote:
if I can share a printer between an XP system and a Win 7 system?
Before I enter all the system data, I just wondered if someone already knew the answer to this one. I was successsfully sharing a non network printer plugged into an XP machine via USB and printing to it via Network Magic from my Vista machine, but since I upgraded Vista to Win 7, I cannot. Everytime I try to install the remote printer or access it in any way from my Win 7 machine, I get the Windows message: " Windows cannot connect to the printer". This also occurs form within the Network Magic Map if I try to Complete Printer Setup. It shows up on my Win 7 machine when I want to ADD a Printer, but I cannot install it. It shows as Shared on the XP machine.
Thanks for any assistance!
S.
Hi S.,
You need to use Network and Sharing Center and open up your computer. You need to use the Public Profile and turn on Network Discovery. Not sitting in front of Windows 7 at the moment.
Otherwise, you need a Wireless Printer or All-In One Machine or a Printer that plugs into the Router using an Ethernet Port.
thecreator - Running Network Magic version -5.5..9195.0-Pure0 on Windows XP Home Edition SP 3
Running Network Magic version -5.5.9195.0-Pure0 on Wireless Computer with McAfee Personal Firewall Build 11.5.131 Wireless Computer has D-Link DWA-552 connecting to D-Link DIR-655 A3 Router.

Unable to wake emacs across subnets

Similar Messages

Maybe you are looking for