Hooking to network

I just plugged my new mac in.  I am trying to network it with 2 servers.  I keep getting an error that there was a problem connecting to the server.  The version of the server you are trying to connect to is not supported.  Is there a way to fix get these macs hooked up without buying 2 new servers?
Thanks!

I know I keep reading (don't use) how Lion (and seems every new OS changed the rules).
Lot of good tips and hits:
http://www.bing.com/search?q=mac+os+x+lion+connect+to+server+with+afp%3A%2F%2F+n ot+smb
As previously mentioned, OS X Lion does not support logging into NAS boxes running Samba or AFP servers that employ the DHCAST128 authentication method. Apple documented this as a security update, in which they outright disabled DHCAST128 in Lion.
http://frankleng.me/2011/07/21/connect-to-a-freenas-samba-or-afp-share-on-lion-w orkaround/
Lion's broken connectivity to NAS and AFP servers
TIP: Workaround for Lion older AFP servers, including NAS, Novell
Lion issue with SMB Windows share in column view; an AD issue
TIP: Workaround to Lion bug in mounting DFS shares
QNAP announces Lion-compatible NAS firmware
Lion problems with SMB network scanning and printing
http://www.macwindows.com/lion-filesharing.html
The Solution
The solution to the problem was actually incredibly simple.  Basically, you just open up Terminal and manually tell the computer to mount the drive.
http://fatwalr.us/2011/08/solution-to-my-smb-connection-problem-in-lion/
http://trick77.com/2011/02/25/afp-broken-linux-based-nas-mac-os-x-lion-10-7/
OS X LION connection error with AFP
at the Apple Developer Forum. Apple disables support for the “DHCAST128″ in OS X 10.7 LION , which is commonly used by NAS boxes. Apple thinks is it insufficiently secure. So all the Vendors must work with Apple for Lion compatibility.
http://www.alexanderwilde.com/2011/04/os-x-lion-connection-error-with-afp-and-wo rkaround/
Lion's broken connectivity to NAS and AFP servers 
Friday, August 5, 2011
It seems like any new release of Mac OS X breaks some aspect of file sharing with non-Apple devices. This was true for Leopard, and Snow Leopard had (and still has) problems with SMB file sharing. With Lion, Apple replaced the under-the-hood workings of both SMB (Samba) and the Apple Filing Protocol (AFP). Almost immediately, users discovered that Mac OS X 10.7.0 has an incompatibility with many network attached storage (NAS) devices using AFP as well as other AFP file servers. Most NAS devices support both AFP and SMB, but Mac OS X's Time Machine backup software requires AFP.
For users, the Apple-provided workaround can prove tricky to work around than it first appeared. Readers have reported by success and failure with the procedure. Lion users who try to access some AFP devices get the error message:
The version of the server you are trying to connect to is not supported. Please contact your system administrator to resolve the problem.
The problem is with the Apple Filing Protocol (AFP) and applies to NAS devices and other AFP servers, including Novell servers. (Group Logic's ExtremeZ-IP is not affected.) Time Machine, Lion's backup software, uses AFP to connect to NAS devices. NAS devices that use SMB file sharing are not affected by this problem. There are also reports around the Internet that the problem affects Mac OS X Server 10.6.
The issue incompatibility arises from Apple dropping support for most authentication types, including the widely used DHX (DHCAST128) and clear text. Lion now uses only DHX2 authentication. Apple's workaround is to use the command line in Terminal to turn on other authentication methods. (More specifically, to remove the older authentication methods from a disabled list.)
Apple says the reason for the change is that DHX2 is more secure than other versions. That could be, but there is more than authentication that's different. Lion is now using a more recent version of Netatalk, v 2.2, which is the AFP client/server file sharing software used in Mac OS X and many NAS devices. Netatalk 2.2, in tern supports AFP 3.3. Most NAS devices are not using the new version of Netatalk, and will have to update their firmware. Several have announced that they are doing just that.
http://www.macwindows.com/Lion-broke-NAS-and-AFP-servers-.html

Similar Messages

  • Hooks to networked image database.

    I am looking for a workaround that might let me use lightroom as a "feeder" application to a larger image database that can also accept CMYK image files.
    I have many thousands of corporate images many of which must be in CMYK format because my printers do not do a good job of RGB conversion.
    Until some future version of Lightroom that might be network and CMYK aware, I would love to use lightroom to help me select new images from cameras, do color correction and create "initial" keywording that would accessible for new images within lightroom.
    Then I could use lightroom for new images and also import these images into another program that would also let me see the legacy CMYK images and their keywords.
    I know this would be duplication in many ways but until lightroom matures into a DAM (if ever) that can also handle CMYK it would be a workaround.
    Any ideas?

    In this book ( Application Developer's Guide - Fundamentals Contents / Search / Index / PDF ) you can find that information:
    Representing Large Data Types
    In times gone by, the way to represent large data objects in the database was to use the LONG, RAW, and LONG RAW types. Oracle recommends that current applications use the various LOB types, such as CLOB, BLOB and BFILE, for this data.
    See the Oracle9i Application Developer's Guide - Large Objects (LOBs) , for information about LOB datatypes.
    http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adfnstyp.htm#430288
    Joel Pérez
    http://otn.oracle.com/experts

  • Network Stream Fails Before Timeout

    Is there any reason why a network stream would fail before the timeout?  I was using streams on an sbRIO-9632 and all throughout testing I had no problems.  But, when I hooked the network up to NASA's dedicated network cable (which goes through one or two switches to eventually connect to my router, the same one used for testing; at NASA's Lunabotics Mining Competition; I think they said it was a virtual network), the streams, as far as I could tell, were failing between immediately and the 15 second timeout.  If I recall correctly, it rarely made it beyond the timeout value.
    Unfortunately, I did not have the time to successfully debug the system while connected to that network cable and switches so I was not able to get the exact error that was occuring.  I do know that the error was originating from the sbRIO because on my computer it was showing that the network streams were closed.
    If you are curious about the architecture being used, it was very similar to "Teleop - Host Acquisition" in the robotics module project wizard.

    Unfortunately, I've been unable to recreate the issue without being connected to the NASA setup (something I won't be able to do for the next year).  The best that I can tell you is that the "fix" that I implemented was to simply re-establish the network stream and prevent it from stopping the rest of the program using a simple state machine for each end of each stream.  It was able to re-connect fairly quickly so I never lost the connection for an appreciable amount of time (which would be required to see a loss in connection in MAX I'm assuming; maybe I'm wrong assuming this?).
    Anyways, because I cannot replicate the issue and therefore test it again, I will try to not take up too much of your time on this one.  I was just hoping to find out if there was any known circumstance that would cause the stream to fail/timeout prematurely. 

  • Network switch

    I'm trying to bypass the security on the Apple Time capsule to some devices. If I where to hook a network switch to WAN port, would this allow it, and what type would I need for the speeds I get. I currently have the AC model and my ISP speeds are 130 down and 25 up. I'm having issues with my Apple Time Capsule communicating with the ADT security gateway and hopping a network switch would solve this problem since I only have one port on modem and can't connect directly to that. I've already messed with ports on router and that didn't help.

    Not sure what you mean about the "security" in the Time Capsule.  A wireless connection uses a type of security called WPA2, but this is standard industry setting that virtually any modem device will use.
    Other than that, there are no "security" settings on a Time Capsule.
    My guess would be that you are trying to say that the ADT gateway is designed to work with a router that provides a feature known as Universal Plug and Play, or UPnP, which is a service that automatically opens the correct ports for devices that are connecting to the Internet.
    Unfortunately, Apple routers do not support UPnP, so your statement that you are going to have to purchase a new router may be correct.
    Apples does provide a function called NAT-PMP, which allows a user to manually enter the port settings that the ADT gateway might require, but this is not always successful, since it is not the same as UPnP.
    If it were me, I would ask ADT support what brand or model of router that they recommend for use with their gateway.

  • Need Help on complex XML loading into ODI

    Hi,
    I have a requirement in which i have to create xml mapping in ODI which should load 30 to 40 million message per day with file size of 30 MB. I have created xml connection in topology manager and have provided xsd path of unix server and it's working but when I try to reverse xml structure into Designer model then it gave me error " java.sql.SQLException: No DTD found and no XML file provided: the XML schema cannot be created". I have used below xml connection detail in topology manager.
    JDBC Driver: com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
    jdbc:snps:xml?f=/odi_rep/sita_meg_bi/etl_metadata/&stypex.xsd&re=TYPEX&ro=true&case_sens=true
    We are using 10.1.3.6 ODI version in this project.I have given below xsd and xml file format. FYI...we recevie multiple message with same strucutre in xml source file.
    XSD File:
    XML File :
    <tns1:MessageTraceEvent xmlns_tns1="http://www.sita.aero/csbu/tools/v1/namespace" timeStamp="2011-07-13T00:01:09Z" priority="3" envelopeMessageID="xs-atl-xs2011-07-13t00:01:09.525:519160" mes
    sageType="TYPEX" messageTotalSize="6506" systemID="bgtxjao">
         <tns1:SitaIdentifiers>
              <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
              <tns1:TransactionID>dzA5Arb0QZyOOq9NqgrQ2Q</tns1:TransactionID>
         </tns1:SitaIdentifiers>
         <tns1:previousSitaIdentifiers>
              <tns1:sitaUID>xPreg1D3RF2tGbF9iUPReA</tns1:sitaUID>
              <tns1:TransactionID>zrL7EtGpTVSYeLpb+2W1NQ</tns1:TransactionID>
         </tns1:previousSitaIdentifiers>
         <tns1:Addresses>
              <tns1:Originator>XS-ATL-XS</tns1:Originator>
              <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
              <tns1:Recipient>AF-QVI-BP</tns1:Recipient>
         </tns1:Addresses>
         <tns1:RemoteSystem>
              <tns1:Source>
                   <tns1:NodeID>AF-QVI-BP</tns1:NodeID>
                   <tns1:MiscData>BadgerID: XS-ATL-XS-1310515269-9.1</tns1:MiscData>
                   <tns1:isCustomer>false</tns1:isCustomer>
              </tns1:Source>
         </tns1:RemoteSystem>
         <tns1:AdditionalData>
              <tns1:TypeXData subject="No message"/>
         </tns1:AdditionalData>
         <tns1:Payload payloadType="MessageData">PHR4bWU6VFhNX0VudmVsb3BlIHhtbG5zOnR4bWU9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2VudmVsb3BlIiB4bWxuczp0eG1zPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9zZXNzaW9
    uIiB4bWxuczp0eG1tPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9tc2doZWFkZXIiIHhtbG5zOnR4bWM9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL2NvbW1hbmQiIHhtbG5zOnR4bXg9Imh0dHA6Ly93d3cuaWF0YS5vcmcvdHhtL3hhdGFwIiB4bWxucz
    p0eG1mPSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9mYXVsdCIgeG1sbnM6dHhtcj0iaHR0cDovL3d3dy5pYXRhLm9yZy90eG0vcmVwb3J0IiB4bWxuczp0eG11PSJodHRwOi8vd3d3LmlhdGEub3JnL3R4bS9hdXRoIiB4bWxuczp0eG1hPSJodHRwOi8vd
    3d3LmlhdGEub3JnL3R4bS9hdHRh
    pc3Rvcnk+PC93dHI6QklSX0RlbGF5ZWRCYWdSZWNvcmQ+CgkJPC90eG1lOlRYTV9QYXlsb2FkPgoJPC90eG1lOlRYTV9Cb2R5Pgo8L3R4bWU6VFhNX0VudmVsb3BlPgo=</tns1:Payload>
    </tns1:MessageTraceEvent>
    Edited by: user13544580 on Jul 18, 2011 6:27 AM

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- edited with XMLSpy v2010 rel. 3 sp1 (http://www.altova.com) by SITA (SITA) -->
    XSD File :
    <xs:schema xmlns:tns1="http://www.sita.aero/csbu/tools/v1/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.sita.aero/csbu/tools/v1" targetNamespace="http://www.sita.aero/csbu/tools/v1/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified" version="version 1.0">
         <xs:element name="MessageTraceEvent">
              <xs:annotation>
                   <xs:documentation>version 1.0</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="SitaIdentifiers" type="tns1:SitaIdType">
                             <xs:annotation>
                                  <xs:documentation>Container for Sita Unique ID and Transaction ID</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="previousSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Container for previous Sita Unique IDs and Transaction IDs</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="relatedSitaIdentifiers" type="tns1:SitaIdType" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Container for related Sita Unique IDs and Transaction IDs which a delivery report is reporting</xs:documentation>
                             </xs:annotation>
                        </xs:element>
                        <xs:element name="Addresses">
                             <xs:annotation>
                                  <xs:documentation>Container for Sender and Recipient addresses</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:sequence>
                                       <xs:element name="Originator" type="tns1:AddressType" minOccurs="0"/>
                                       <xs:element name="Recipient" type="tns1:AddressType" minOccurs="0" maxOccurs="unbounded"/>
                                  </xs:sequence>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="RemoteSystem">
                             <xs:annotation>
                                  <xs:documentation>Container for Source or Destination system information</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice>
                                       <xs:element name="Source" type="tns1:HostType"/>
                                       <xs:element name="Destination" type="tns1:HostType"/>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="AdditionalData" minOccurs="0">
                             <xs:annotation>
                                  <xs:documentation>Service or Billing specific information</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:choice>
                                       <xs:element name="AFTNData" type="tns1:AFTNDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Addintinal data gathered on NTS </xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="TypeBData" type="tns1:TypeBDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on MegaSwitch, Sitex or Badgers</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="TypeXData" type="tns1:TypeXDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on Badgers</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="SMTPData" type="tns1:SMTPDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on SMTP systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="FAXData" type="tns1:FAXDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on Fax systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                       <xs:element name="OmhData" type="tns1:OmhDataType" minOccurs="0">
                                            <xs:annotation>
                                                 <xs:documentation>Additional data gathered on OmhData systems</xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:choice>
                             </xs:complexType>
                        </xs:element>
                        <xs:element name="Payload" minOccurs="0" maxOccurs="unbounded">
                             <xs:annotation>
                                  <xs:documentation>Used to save the full message as received from customer, it can help us avoid re-transforming it back to original message or be used for debugging</xs:documentation>
                             </xs:annotation>
                             <xs:complexType>
                                  <xs:simpleContent>
                                       <xs:extension base="xs:base64Binary">
                                            <xs:attribute name="payloadType">
                                                 <xs:simpleType>
                                                      <xs:restriction base="xs:string">
                                                           <xs:enumeration value="MessageData"/>
                                                           <xs:enumeration value="EnvelopeData"/>
                                                      </xs:restriction>
                                                 </xs:simpleType>
                                            </xs:attribute>
                                       </xs:extension>
                                  </xs:simpleContent>
                             </xs:complexType>
                        </xs:element>
                   </xs:sequence>
                   <xs:attribute name="timeStamp" type="xs:dateTime" use="required"/>
                   <xs:attribute name="priority" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>Priority defines precedence in sending the messages through to destination</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="bodyMessageID" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>The Message ID in the body, as received from or sent to the customer.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="envelopeMessageID" type="xs:string" use="optional">
                        <xs:annotation>
                             <xs:documentation>The Message ID in the envelope, as received from or sent to the customer.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="isReport" type="xs:boolean" use="optional" default="false">
                        <xs:annotation>
                             <xs:documentation>Is it a delivery or acknowledge report? If so, set it true</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageType" type="tns1:MessageType" use="required">
                        <xs:annotation>
                             <xs:documentation>The type of message, e.g. TYPEB, TYPEX, SMS, etc.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="previousMessageType" type="tns1:MessageType" use="optional">
                        <xs:annotation>
                             <xs:documentation>The logical message type, where this is different from the physical type. For example a TYPEB message sent to SMTP would have a messageType of SMTP, but previousMessageType of TYPEB.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageBodySize" type="xs:string" use="optional"/>
                   <xs:attribute name="messageHeadSize" type="xs:string" use="optional"/>
                   <xs:attribute name="messageTotalSize" type="xs:string" use="optional"/>
                   <xs:attribute name="PDM" type="xs:boolean" use="optional">
                        <xs:annotation>
                             <xs:documentation>True if it is a PDM message.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messsageArchive" type="xs:boolean" use="optional">
                        <xs:annotation>
                             <xs:documentation>True if the message has been flagged for archiving.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="messageArchiveDays" type="xs:int" use="optional">
                        <xs:annotation>
                             <xs:documentation>The number of days to archive, if known.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
                   <xs:attribute name="systemID" type="xs:string" use="required">
                        <xs:annotation>
                             <xs:documentation>The unique identifier for the system executing the transaction, e.g. BADGERX, JAOMSW, etc.</xs:documentation>
                        </xs:annotation>
                   </xs:attribute>
              </xs:complexType>
         </xs:element>
         <xs:simpleType name="MessageType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="AFTN"/>
                   <xs:enumeration value="FAX"/>
                   <xs:enumeration value="SMTP"/>
                   <xs:enumeration value="TYPEC"/>
                   <xs:enumeration value="TYPEB"/>
                   <xs:enumeration value="TYPEX"/>
                   <xs:enumeration value="SMS"/>
                   <xs:enumeration value="X400"/>
                   <xs:enumeration value="SKYFAX"/>
                   <xs:enumeration value="OTHER"/>
                   <xs:enumeration value="TELEX"/>
                   <xs:enumeration value="URI"/>
                   <xs:enumeration value="EDI"/>
                   <xs:enumeration value="EDI-X12"/>
                   <xs:enumeration value="EDI-EDIFACT"/>
                   <xs:enumeration value="EDI-BINARY"/>
                   <xs:enumeration value="EDI-XML"/>
                   <xs:enumeration value="SPEC2000"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="EventType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="MessageAccepted"/>
                   <xs:enumeration value="MessageDispatched"/>
                   <xs:enumeration value="MessageRejected"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="TypeBPriority">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="AF"/>
                   <xs:enumeration value="NO"/>
                   <xs:enumeration value="OK"/>
                   <xs:enumeration value="QA"/>
                   <xs:enumeration value="QB"/>
                   <xs:enumeration value="QC"/>
                   <xs:enumeration value="QD"/>
                   <xs:enumeration value="QK"/>
                   <xs:enumeration value="QN"/>
                   <xs:enumeration value="QP"/>
                   <xs:enumeration value="QQ"/>
                   <xs:enumeration value="QU"/>
                   <xs:enumeration value="QX"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="FaxServiceName">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="IPFax"/>
                   <xs:enumeration value="BFax"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="MessageStatusType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value="failed"/>
                   <xs:enumeration value="relayed"/>
                   <xs:enumeration value="received"/>
                   <xs:enumeration value="delivered"/>
                   <xs:enumeration value="rejected"/>
                   <xs:enumeration value="re-injected"/>
                   <xs:enumeration value="intercepted"/>
                   <xs:enumeration value="drained"/>
                   <xs:enumeration value="op-dropped">
                        <xs:annotation>
                             <xs:documentation>message dropped by an operator</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="sys-dropped">
                        <xs:annotation>
                             <xs:documentation>message dropped by the messaging system</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="odmci">
                        <xs:annotation>
                             <xs:documentation>out of date message cancellation input</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="odmco">
                        <xs:annotation>
                             <xs:documentation>out of date message cancellation output</xs:documentation>
                        </xs:annotation>
                   </xs:enumeration>
                   <xs:enumeration value="other"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="AFTNDataType">
              <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="SMI" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ISN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The ISN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="TypeBDataType">
              <xs:attribute name="isDataCollect" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>To determine a Type B traffic chargeable</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="SMI" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Standard message identifier for Type B messages</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="eopt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>eopt is 10 numeric characters long and the value is always 0000000000, Eric indicated his team does not populate any value in this field. </xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
              <xs:attribute name="subject" type="xs:string" use="optional"/>
              <xs:attribute name="charSet" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The character set of a message body</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ISN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The ISN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="cnxType" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The connection Type of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="Location" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The location of a connection coming from</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="SMTPDataType">
              <xs:attribute name="subject" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="rule" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="resend" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="TypeXDataType">
              <xs:attribute name="messageIdentifier" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="documentConversion" type="xs:boolean" use="optional"/>
              <xs:attribute name="subject" type="xs:string" use="optional"/>
              <xs:attribute name="XATAPSN" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The XATAPSN number of a message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="BadgerId" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The BadgerId to a Type X message is what ISN to a Type B message</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="FAXDataType">
              <xs:attribute name="errorCode" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Error code for the request. 0=success.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="errorString" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The error message, if any.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="serviceName" type="tns1:FaxServiceName" use="optional">
                   <xs:annotation>
                        <xs:documentation>Enum value in FaxServiceType</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="channelNumber" type="xs:int" use="optional">
                   <xs:annotation>
                        <xs:documentation>The fax channel on the server.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="receivedSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The size of the received message, including headers.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="convertedSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The size of the message after conversion for fax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalSentSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the bytes sent, including cover pages and retries.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalConnectTime" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of time connected to a fax receiver for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalDuration" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the off-hook, or network time, for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="nbrFaxPages" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The number of pages in the message, including the cover sheet.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="totalPages" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The sum of the pages sent for all attempts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="recvCSID" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The CSID received from the remote fax system.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="tries" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The number of fax attmpts.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="subject" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="acknow" type="xs:string" use="optional"/>
              <xs:attribute name="cod" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="referenceNumber" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The UFAX MSG_ID for the message.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="distID" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The UFAX MSG_RQ_ID for the message.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="fineResolution" type="xs:boolean" use="optional">
                   <xs:annotation>
                        <xs:documentation>True for Fine resolution, false for Coarse resolution.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="baudRate" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The connection speed for the fax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="sitaReceiveTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the message is received into SITA's network.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="ufaxReceiveTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when UFAX receives the message, when it is delivered to the UFAX inbox.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="startConversionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the Converter starts processing a message. If it takes more than one attempt to convert the message, this will be the time of the first attempt.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="endConversionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the Converter completes the conversion process. If it takes more than one attempt to convert the message, this will be the time of the last attempt.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="tfaTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time of the first call attempt for the message. If UFAX is already calling the fax number for a different message, then this will be the time the message was queued for calling.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="completionTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the fax has been completed, either because the fax was delivered or it reached the maximum error threshold.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="reportTime" type="xs:dateTime" use="optional">
                   <xs:annotation>
                        <xs:documentation>The time when the delivery report is sent. Not used if a report isn't sent.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="doubleSignature" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>For BFax, the Double Signature for the message if any.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="userConfigType" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>Legacy bit-mapped field for BFax.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="networkAccessPoint" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation>The network access point where the channel was connected.</xs:documentation>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="OmhDataType">
              <xs:attribute name="msgIdent" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="sysMsgIdent" type="xs:string" use="required">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
                        <xs:attribute name="inMsgFmt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="outMsgFmt" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="toDirection" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="fromDirection" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="inMsgSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
                        <xs:attribute name="outMsgSize" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="compCode" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
              <xs:attribute name="applicationId" type="xs:string" use="optional">
                   <xs:annotation>
                        <xs:documentation/>
                   </xs:annotation>
              </xs:attribute>
         </xs:complexType>
         <xs:complexType name="AddressType">
              <xs:annotation>
                   <xs:documentation>This is a generic address object</xs:documentation>
              </xs:annotation>
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="responsible" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>Used to denote whether the address should be delivered or not, is the node responsible for delivery of this address</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="typeOfAddress" type="tns1:MessageType" use="optional">
                             <xs:annotation>
                                  <xs:documentation>Type of the address we are given</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="mapped" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>Used to denote whether the address is mapped or not</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="masqueraded" type="xs:boolean" use="optional" default="false">
                             <xs:annotation>
                                  <xs:documentation>used to denote if the address is masqueraded, this happens often when messages are pushed through gateways.</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                        <xs:attribute name="masqueradedID" type="xs:string" use="optional">
                             <xs:annotation>
                                  <xs:documentation>If the address is masqueraded than this is the place where I can carry the original address</xs:documentation>
                             </xs:annotation>
                        </xs:attribute>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="HostType">
              <xs:annotation>
                   <xs:documentation>This is a generic host object</xs:documentation>
              </xs:annotation>
              <xs:sequence>
                   <xs:element name="HostName" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Hostname of the server</xs:documentation>
                        </xs:annotation>
                        <xs:complexType>
                             <xs:simpleContent>
                                  <xs:extension base="xs:string">
                                       <xs:attribute name="hostType" type="tns1:MessageType" use="optional">
                                            <xs:annotation>
                                                 <xs:documentation>Type of the host such as MQ, JMS, SMTP etc</xs:documentation>
                                            </xs:annotation>
                                       </xs:attribute>
                                  </xs:extension>
                             </xs:simpleContent>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="NodeID" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Optional NODE ID goes here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostIP" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Service or host IP address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostPort" type="xs:integer" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Port address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="url" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>URL address of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="HostChannel" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>Channel name of the service</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="ConnectionNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>the connection number that host is connecttng to.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="CircuitNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>This is SITA's CNR</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="DestinationNumber" type="xs:string" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>This is SITA's DNR</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="X25DNA" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>This is SITA's X25 dan numbers</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:positiveInteger"/>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="MessageStatus" type="tns1:MessageStatusType" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>Users can put anything they want here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="MiscData" type="xs:string" minOccurs="0" maxOccurs="unbounded">
                        <xs:annotation>
                             <xs:documentation>Users can put anything they want here</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="isCustomer" type="xs:boolean">
                        <xs:annotation>
                             <xs:documentation>False if the sender/receiver is a SITA system</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="SitaIdType">
              <xs:sequence>
                   <xs:element name="sitaUID" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>The unique ID assigned to the message by the first receiving system. This ID must be contained in the message.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="TransactionID" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>An identifier assigned or created for this event. This must be a unique identifier for this message, i.e. the combination of the SitaUID and transaction ID must be unique. This ID must be contained in the message.</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>

  • Printer prints but no ink comes out

    have all in one printer 8500. my  printer prints but no ink comes out. put new ink in and cleaned printer heads. did printer head cleaning 3 levels and still not printing, no error messages. running xp on main computer. hooked in network through router.

    Hi there,
    Welcome to the HP Forums!
    I noticed that your HP 8500 will print but no ink comes out, and I am happy to help you!
    I am  also glad that you had already put new ink in, and cleaned the printheads.
    For further assistance, I will need to know your printer's Product/Model number. As there are multiple HP 8500 printers. To find your printer's Product/Model Number follow instructions in this link. Finding Your HP Product Model Number.
    Hope to hear from you soon, and thank you for posting!
    RnRMusicMan
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" to say “Thanks” for helping!

  • File and printer sharing using Airport Express, usb HP Deskjet 3620 printer

    I have a general question, and other forum users might have a good resolution for it - but if not, here's what i'm dealing with..
    I have an Airport Express that I bought a couple of years back, it has all the necessary firmware upgrades, i'm running 2 Windows XP boxes going through a combination of Ethernet on 1 directly to the 2 Wire Home Portal 2701HG-B, and I also have an additional Netgear WGR614 v7. All firmware upgrades on all devices is installed and functioning after reset.. I've tried using a combination of the Windows XP built-in networking software, Apple Airport Utility, as well as Bonjour to get things configured and working right over the network. I've also installed the AT&T software, one is running the Mcafee security suite, and mine (the Etnernet box) is running the diagnostic utility.
    I've tried defaulting all the firewall settings in either/or/all routers i've tried setting the Airport up with, and there still seems to be problems getting file and printer sharing to work right on all computers, and still remain safe behind the firewall. All the network hardware is set up with wpa2/psk authentication, and appears to be configured correctly.
    The only version of the Apple Airport Utility that will run successfully on the systems, is the original version that came on the CD with the Airport. Both systems are completely up-to-date from Windows update, and are both running XP service pack 3.
    I know for a fact, that the Airport is working just fine, as I've troubleshot all possible known hardware issues with it individually, hooked up to 1 pc (with current updates installed and running). Wireless works fine, i'm actually running the Airport utility on my main system in the living room, that's hooked up hardwired to the router. Both systems get online and surf without a problem going through either/or router as well. I've also tried dissabling the Windows firewall on both systems, and trying to set up file and printer sharing manually using the wizard, and that don't seem to resolve the issues either. However, both systems (wheather hooked up networked, OR individually), have both been experiencing some odd "quirks". The Ethernet box i'm on, has overwritten my primary HD, as "Athena" and made it unusable. The wireless box, has been giving simular "boot-up" related errors as well. I've checked the Cmos/DOS settings on both, and performed the suggested "boot-up" priority related tasks, and both systems are still experiencing problems. The Mcafee suite is up-to-date, and has caught several potentially dangrous programs running on the wireless box, hooked up to the Airport Express, INCLUDING the bundled HP diagnostic software.. However file and printer sharing still remains elusive...
    Are there any suggestions about settings to check on the devices, or in the computers, to make sure it's all configured correctly?

    ...Also file/printer sharing just flat out over the network is NOT a problem, as it's been configured before over ethernet through my Netgear router and file/printer sharing worked just fine.
    The main problem seems to be in the Airport Express' settings, it will "get configured" and then lock me out of the utility to where I can't get back in..
    The main Airport password has not been changed, and the wireless network encryption is the same for all wireless devices running on the network.
    The main problem, just seems to be with the Airport.
    Even the Home Portal has detected the Netgear router (unless it having my Netgear router saved in it's settings might be causing a conflict)... Suggestions?
    I've contacted AT&T Home Networking for help already about the Home Portal, unfortunately they can not help me with other network related issues, since i'm not using the 2 wire wireless adapters offered by AT&T...
    Message was edited by: okwolffcub

  • Comcast, Vonage, Airport

    I'm trying to figure out why using the telephone on Vonage is dropping my wireless connection forcing me to relogin my wireless connection.
    Currently I have an RCA modem plugged in my WAN port of my Apple Airport Extreme 802.11n base station.
    I have the Vonage box hooked up via one LAN port.
    I have a Windows XP SP 2 Dell in a second LAN port.
    and I have a MacBook Pro 10.4.11 Core2Duo 2.2 Ghz hooked up via wireless.
    I'm hoping the upgrade to version 7.3.1 of the airport software will fix the problem, but if it doesn't, does it really matter if the Vonage box is hooked up between the RCA modem and the WAN port, or if it is on a LAN port of the airport base station?

    Aha! Interference robustness in the airport menu when unchecked solved the problem. I saw that every time I took the phone off the hook the network completely dropped, only to come back up when the phone was put back on the hook. Turned off interference robustness, and that cleared everything up.

  • Printer in wireless router

    I have brought home a HP Laser Jet 2300DN printer from our office and have hooked the network cable into the back of your wireless router WRT54GL and into the printer.
    I have tried to connect to the HP printer using the desktop computer with out any success.
    The wireless computers and the desktop computers all connect to the internet, but none of them can connect to the HP printer. 
    What would you suggest should be done so the printer can be used?
    Thank you.

    You need to install the printer driver (or an entire "printer software package" ) on each computer that will be using this printer. 
    Each printer driver has its own setup method.  Some printer drivers will require that you first establish a USB connection between the printer and one of your computers, and then later, disconnect the USB cable and wire the printer to your router.  Other printer drivers will install directly, with the printer and computer already connected to the router.  Follow the manufacturer's directions carefully.   Get the printer working first with a computer that will be wired to the router.  Then do your wireless computers.  
    Note that some printer drivers are smarter than others.   If the printer is getting its LAN IP address from the DHCP server in the router  (the same way your computers probably get their address) ,  then the LAN IP address of the printer can sometimes change.  Some printer drivers can handle this address change, and continue printing normally.  Others cannot.  If your driver cannot handle this, then you will need to assign your printer a fixed LAN IP address.  This address is typically assigned in the printer (not in the router) .  With Linksys routers, a fixed LAN IP address must be outside the DHCP server range, and it cannot end in 0, 1, or 255.   If you need to give your printer a fixed LAN IP address, then you will also need the Subnet Mask 255.255.255.0 , Default Gateway 192.168.1.1 , and DNS server 192.168.1.1 .

  • Pairing Airports Now that WDS is being replaced.

    From disucssions with a level 2 Airport network support rep earlier this year, it is my understanding that WDS is being phased out.  There is a new method for pairing Airport base stations in a particular order.  However, for the life of me, I forget how to do it and can find nothing in the manuals reflecting the new methodology.
    I have three Airport Extremes at work in a two level office.  Our main base station connects to the Internet at 20 Mbps down/5 Mbps up.  That base station should be handing off the connection to another base station directly on the floor above.  I've checked (using speed test sites), and that second ("middle") base station reflects no drop in accessing the Internet at same 20 Mbps down/5Mbps up.  The third ("furthest") base station is approximately 20 feet from and on the same floor as the second (middle) base station.  Until recently, it, too, was reaching the same speeds exhibited by the other two Extremes.  However, in the past week, the third (furthest) base station is reaching download and upload speeds roughly half of the other two. 
    Nothing has changed in our office in the past week or so to cause this slowdown.  I have power cycled all involved devices but no improvement.  I have also tried to reset the third (furthest) base station in an attempt to make sure it is trying to connect to the second (middle and closest) base station rather than the main base station on the floor below, but I cannot remmeber how to access the hidden menu in Airport Utility/Airport Setup that allowed me to dictate which base station another base station is to look to for extending the network.
    Any help would be greatly appreciated.  Thanks in advance.
    Respectfully,
    Law Office Admin
    P.S. All Airport Extremes are running firmware 7.5.2.  While only one base station is one of the newer ones sporting dual antenna (the "main" base station), all three are capable of running in 5GHz mode.  To make sure I get the best range and optimally penetrate walls and falls, I am running the second (middle) and third (furthest) base stations at 2.4 Ghz.

    It was my understanding that the 2.4 GHz band is the only band I'm extending presently, as the upstairs base stations are single band only and thus set to 2.4 GHz.  Right now, I can see from pretty much anywhere in the offices that there are two networks available: "network abc" and "network abc (5 GHz)".  Again, I tell people to only hook to "network abc (5 GHz)" when they are within eyeshot of the lone, dual band base station.  I'm going to assume there is nothing magical to this particular naming scenario and leave it as is unless you say otherwise.
    Oops, you are correct.
    Don't worry about the Correct Answer vs. Helpful. I'm not here for the points, but thanks anyway for the thought.
    In your original post you mentioned that you didn't find any references to how to configure for an extended network using the newer "dynamic" WDS or as Apple calls it, an Extended network ... so here are the basic steps for future reference. Apple also does provide an excellent reference where you can download from here: Apple AirPort Networks
    AEBSn - Extending a wireless network Setup
    If practical, place the base stations in near proximity to each other during the setup phase. Once done, move them to their desired locations.
    Open AirPort Utility and select the base station that will connect to the Internet.
    Choose Manual Setup from the Base Station menu, or double-click the base station to open the configuration in a separate window. Enter the base station password if necessary.
    Click AirPort in the toolbar, and then click Wireless.
    Choose “Create a wireless network” from the Wireless Mode pop-up menu, and then select the “Allow this network to be extended” checkbox.
    Next, select the base station that will extend this network, and choose Manual Setup from the Base Station menu, or double-click the base station to open its configuration in a separate window. Enter the base station password if necessary.
    Choose “Extend a wireless network” from the Wireless Mode pop-up menu, and then choose the network you want to extend from the Network Name pop-up menu.
    Enter the base station network and base station password is necessary.
    Click Update to update the base station with new network settings.
    Repeat the last four steps for each additional base station that will be used to extend the network.

  • WAG120N and RE1000

    Hi i have a network with a modem/router Wag120n but the wireless not cover my entire building so i have buy a Re1000 .
    I configure re1000 throught wireless, so connect this device to elettrical outlet and connect it with my ssid wireless.
    The problem is that re1000 dosen't hook immediately my network and often or almost always don't hook my wirless network.
    To hook my network i am forced to turn off and turn on the device many times until that hook my network.
    What could be the problem?
    Is it a problem of configuration of my network?

    Hello,
    Go to google and search for "v=nqIdNEYIn7w", play the first youtube link and listen carefully (CARE-FULLY)  , and you're back to happiness if you're quite lucky !
    You can see my comment atop the comments in the video, if you'd like a POC

  • Applications that Run - Pleasant Surprises

    I just got my new iMac yesterday and was totally surpised to find that Timbuktu and my scanner software seem to run fine. I was expecting normal apps to work, but Timbuktu has a contexual menu and pretty deep hooks into networking. Canoscan Toolbox isn't a very pretty app, but it started up and scanned just like on a PowerPC based machine. Woo hoo!
    iMac Dual Core   Mac OS X (10.4.4)  

    Am I misunderstanding what "Hide" is for?
    No. The Hide function does not work on some applications in Mac OS X 10.4, such as Mail.
    if not, I'd appreciate any ideas on [how] to fix this.
    Open the Script Editor in the /Applications/AppleScript/ folder and enter the following:
    tell application "Mail" to run
    delay 1
    tell application "System Events" to set visible of process "Mail" to false
    Save the script as an application, add it to the list of login items, and then remove the existing Mail application from the list.
    (17856)

  • I am trying to connect a Windows 7 / 64 bit to an Epson printer on my Mac.  The printer is hooked into the Mac via USB; the Mac is networked to a Linksys wireless router with an ethernet cable, as is the Windows box. Any tips on how to do this?

    I am trying to connect a Windows 7 / 64 bit to an Epson printer on my Mac.  The printer is hooked into the Mac via USB; the Mac is networked to a Linksys wireless router with an ethernet cable, as is the Windows box. I installed the current Bonjour printer services software on the Windows machine, and separately installed the driver software for the Epson printer on the WIndows machine.  Running the bonjour wizard, I get an alert saying 'I don't have sufficient access to my computer to connect to the selected printer'.
    The printer has 'sharing' turned on from the Mac end; this works with a Powerbook via the wireless connection.  Sharing is also turned on in the Windows printer control panel for this printer (under properties).  The Mac is a G5 running 10.5.8.  When I try to print a page from the Windows machine it gets hung in the print queue.
    Any advice how to proceed would be appreciated!
    thx,

    I am trying to connect a Windows 7 / 64 bit to an Epson printer on my Mac.  The printer is hooked into the Mac via USB; the Mac is networked to a Linksys wireless router with an ethernet cable, as is the Windows box. I installed the current Bonjour printer services software on the Windows machine, and separately installed the driver software for the Epson printer on the WIndows machine.  Running the bonjour wizard, I get an alert saying 'I don't have sufficient access to my computer to connect to the selected printer'.
    The printer has 'sharing' turned on from the Mac end; this works with a Powerbook via the wireless connection.  Sharing is also turned on in the Windows printer control panel for this printer (under properties).  The Mac is a G5 running 10.5.8.  When I try to print a page from the Windows machine it gets hung in the print queue.
    Any advice how to proceed would be appreciated!
    thx,

  • How do i get my laptop to access the itunes library on my external drive hooked up to my desktop via my home network?

    How do i get my laptop to access the itunes library on my external drive hooked up to my desktop via my home network?

    If you are willing to pay $24.99 per year for iTunes Match you can put your library in the cloud provided you don't have more than 25,000 tracks.
    iCloud- iTunes Match
    iTunes in the Cloud and iTunes Match Availability
    iTunes Store- Troubleshooting iTunes Match
    iTunes- How to add a computer or iOS device to iTunes Match

  • When I replaced my PC desktop with a Mac Mini and hooked up my HP printer to it, I discovered my other computers on the Wi-Fi network could no longer access the printer.  The manual says Maverick OS will not allow PC's to access the printer. Any thoughts?

    When I replaced my PC desktop with a Mac Mini and hooked up my HP printer to it, I discovered that my other computers on the Wi-Fi network could no longer access the printer.  The manual says Maverick OS will not allow PC's to share the printer. Does anyone else have this problem?  My printer does not have on-board Wi-Fi but, otherwise, works fine.  I shouldn't have to buy a new one.  Is there a OS patch out there that would open the printer port for my PC computers?

    I'm assuming that on the Mac, the System Preferences -> Sharing -> Printer Sharing -> [X] HP printer -> Everyone can print is selected?  That is to say, the Mac will allow anyone to print using the printer, and that you did not try to restrict who can print.
    How is your network configured?  Bonjour as a protocol will NOT cross a router boundary.  If you have 2 or more subnets active with the PCs on one subnet and the Mac on another, that would block the PCs from seeing the Mac.
    You could have multiple subnets if you have more than one router, such as an ISP provided broadband modem/router and another WiFi Router.  If the PCs are talking to one router and the Mac is talking to another, that could be a 2 subnet situation.  The additional routers must be put into bridge mode, which is done differently depending on the router.  But the basics are to diable DHCP and NAT services on the secondary router(s) having just one active router on the network.
    Also, using Bonjour Browser on my Mac, it is showing me that the printer is being advertised as using Internet Printing Protocol, so if that is something selectable on Windows, maybe you can bypass Bonjour on Windows.

Maybe you are looking for

  • Reverse a clearing Document

    Hi All,    I did F-30 transaction for clearing a Document.  How can I cancel my changes that I did by clearing. Regards, Philip

  • Basic question on Adobe document services

    Hi    We have a ECC50 instance - the basis component of which has been given to us from our headquarters that has stripped off the J2EE server ( i.e given a WAS640 with just the ABAP runtime installed ). Now, we are planning to use Adobe Interactive

  • Can Illustrator really make use of 8GB RAM?

    Hello, I'm thinking of upgrading my 17" 2010 Core i7 Macbook Pro from the curretn 4GB of RAM to 8GB or RAM as the prices have come down considerably. (around £40.00). I've already posted a thread on a mac forum, but I thought that posting in on here

  • Steps to create STO using ME21N transaction

    Hi, Can anyone give me the steps to follow to create STO using ME21N transaction. When i try to create it, i am getting the error message : Not possible to determine shipping data for material 3863... Please guide me... Thanks in Advance, Phani Kumar

  • Using BAPI_ACC_INVOICE_RECEIPT_POST to create Invoice Receipt

    Hi, I'm using the above BAPI to create invoice receipts (to mimic MIRO) but if I enter the OBJ_TYPE RMRP it gives me an error: 'Incorrect entry in field OBJ_TYPE: RMRP' I've checked table TTYP and this object type does exist.  Has anyone come across