Ghost Error 33 Unable To Bind
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT http://www.symantec.com/connect/forums/ghost-boot-disk-error-33-unable-bind Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise https://community.hpe.com/t5/General/problem-with-Network-Boot-Disk-from-Symantec-Ghost-7-5-Corporate/td-p/3372548 Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Govern
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft http://arstechnica.com/civis/viewtopic.php?t=665628 OS & Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed http://www.tek-tips.com/viewthread.cfm?qid=987998&page=83 Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries Ghost for an onboard NIC 13 posts Metzen Ars Scholae Palatinae Tribus: Calgary Registered: Aug ghost error 28, 2000Posts: 1040 Posted: Mon Jun 30, 2003 11:51 pm Ok, I'm looking for a Norton Ghost solution. My current problem is I have lots of computers with on-board NIC's that need to have a master Ghost image placed on them. The problem is I haven't been able to install/find a driver that works with the onboard NIC. The motherboard with the on-board NIC is a Micro-Star motherboard with a Intel Pro 1000 ghost error 33 CT on-board NIC.I was able to find the drivers at Micro-Stars web site (I know these are the correct drivers because the version number and dates matched up), but the DOS drivers appear to be only allow for a Novell-type of installation or some other.I also went to Intel's site and searched for a driver for the Intel Pro 1000 CT and they don't support it because it's integrated and instruct me to go to the manufacturer of the motherboard (whom don't actually support a DOS boot).Does anyone know what kind of action I could take so that I don't have to go to every single computer, rip open the case, add a Ghost compliant NIC, Ghost, remove it, and move to the next machine? Gyro77 Ars Tribunus Militum Registered: Jun 27, 2000Posts: 1778 Posted: Tue Jul 01, 2003 1:53 am I think what you are really saying is that you don't have a DOS boot disk that you can get setup to work with the onboard nic and then launch Ghost correct?If so, the DOS drivers are included in the driver file you linked to, you just have to create a bootdisk to use them. Or use something like this:Bart's Network Boot DiskAnd follow the instructions to include the following driver package:E1000 DriverHopefully that points y
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. DNS/BIND/DHCP/WINS Issues Forum at Tek-Tips HomeForumsMIS/ITDNS / BIND / DHCP IssuesDNS/BIND/DHCP/WINS Issues Forum error: 33 unable to bind thread950-987998 Forum Search FAQs Links MVPs error: 33 unable to bind error: 33 unable to bind Wendell6910 (MIS) (OP) 19 Jan 05 15:27 I am using Ghost 8 to make a image of a home built pc using a ASUS A7N8X motherboard with a nforce MCP nic.I have downloaded the dos driver and used the boot wizard to make a bootdisk (2 disks).When booting I get the error:33 unable to bind.Have tried a static IP and DHCP.Need to use the GhostCast Server option.Anyone able to provide some info on the error message? RE: error: 33 unable to bind segment (ISP) 19 Jan 05 17:26 According to a previous thread:solution (Visitor)Sep 24, 2001Just write everything in the protocol.ini lower case, because the entries are case-sensitive. it worked for me... Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free f