08-22-2008
1,
0
Join Date: Aug 2008
Last Activity: 1 September 2008, 10:02 PM EDT
Posts: 1
Thanks Given: 0
Thanked 0 Times in 0 Posts
How do I connect a hpux10.x os machine to "the internet" via a WinXP client?
I am wondering how can I cross this technical border of my ignorance for quite sometime, 6 months to be more exact, and just don't get it quite.
I did read some newbies' literatures on UNIX OS but could not find the key to unlock the HP workstations (OS dated 1997 maybe because the man page shown this date) that intranetted via a router, to the www, through this WinXP client which have a network card (ethernet?) installed and connected via network cable at the same router. This WinXP based machine (which I am typing on) is connected to www through another company network via network cable to the broadband ISP which may have some firewall setting which I am not very sure of. I will have to key in my id and password in order to access the www when the browser popped-up first with a id and password prompt.
So, I tried to ftp and telnet from the UNIX end to this XP machine but failed miserably, I can however ping from the UNIX to this XP. I assumed the preset IP address of the ethernet adapter local area connection shown while I run ipconfig at the DOS prompt represent this XP machine.
I can ftp the UNIX from this XP, but when I "put" a 195b txt file into the UNIX machine, a warning of
"226-WARNING! 14 bare linefeeds received in ASCII mode
File may not have transferred correctly."
is shown at the ftp prompt.
I knew something is not right, but I don't know what is that "something" in particular to solve the problem of connect the UNIX to www via this XP. I tried to run sam on the UNIX workstation and added a host with the XP machine ip address and that is not of help neither, in fact the sam cautioned me that I should refer to NIS documentation because the system is configured to use NIS (Network Information Service) and SAM does not support the configuration of NIS.
Beat me because I am poorly literate in the networks acronyms and lost in frustration, hence this new thread seeking for guidance.