06-25-2009
Unable to connect to Internet
thanks for your replies..I re-installed sxde 1/08 into my machine..its working fine now
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I running HPUX 11.0,
Netscape gives me an error "Unable to locate Server" when using a www.something.com address.
If I use an IP address I get past the router and onto the Internet.
My workstation can get to the Router @ 192.168.0.1 and also it's local APACHE server.
I have DHCP enabled... (8 Replies)
Discussion started by: johnalt
8 Replies
2. Solaris
i have just installed solaris 10 on a 60 gb hard drive. now im trying to install my nic driver but when i put in the floppy disk for the nic card it cant read it, so then i found that i have to mount the floppy drive and i tried putting in the mount command but i dont know where to mount it and if... (38 Replies)
Discussion started by: vutty81
38 Replies
3. Solaris
Hi I installed solaris developer edition 1/08 today.I want to connect to Broadband internet through my ADSL 2+ Modem/Router with a username and password.
plz help in this case,I am new to sun solaris:confused:
the modem itself is a router it worked well on ubuntu and red hat (3 Replies)
Discussion started by: santugvd
3 Replies
4. Linux
HI,
Am using GPRS ( MOB # 3230 ) internet connection in windows
Hw to use internet r connect in linux.. ( Red Hat Linux Ver.10 )
Please help me..
Thanks in adv.. (1 Reply)
Discussion started by: bharath raja
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
Iam using BSNL broad band connection and i have installed two OS Xp & Sun solaris -x86 on my machine.Iam able to use INTERNET on windows Xp but not able to do it on solaris x86.
I have tried using DHCP concept as well as sys-unconfig command in solaris but no results.
When i use... (5 Replies)
Discussion started by: jayaprakash
5 Replies
6. Solaris
Dear freinds...
I downloaded solaris for x86 and was able to configure the lan correctly.. I can ping and share with other destops through lan... but still I can't connect to internet ? can you please help..
I put my default gateway which is 192.168.1.1 to /etc/defaultrouter but with no use..... (13 Replies)
Discussion started by: yahyaaa
13 Replies
7. Virtualization and Cloud Computing
I have installed Oracle VM virtual box on Windows 7 and using LINUX (backtrack 5) as my virtual OS. The problem is i'm unable to connect to internet from my virtual OS. i'm using USB dongle (mobile broad band) to connect to internet from my host OS windows 7.
I tried setting NAT in VM settings... (0 Replies)
Discussion started by: Arun_Linux
0 Replies
8. IP Networking
Hi,
I have a wired internet connection of hathway provider. I would like to use the connection on my desktop as well as my laptop. My desktop pc has windows 7 and yesterday I installed slackware 14.1 (full installation) on my lenovo 3000 n100 laptop.
Previously I had slacko puppy 5.7... (7 Replies)
Discussion started by: pinakbheed
7 Replies
9. Red Hat
Hello,
I just installed CentOS 7 (Server with GUI) and guess what I could install Virtual Box Guest additions without installing any extra package/software which is great news !
Now bad news or not so great news.
My Host OS is Windows 10, Virtual Box is the virtualization software. CentOS7-1... (0 Replies)
Discussion started by: bluemind2005
0 Replies
10. Linux
Hello, I installed FreeBSD 10.3 on AQEMU. I can't connect to internet in none
of the modes of "Default, User-Mode Networking" and "TUN/TAP Networking".
I am able to ping my host in the TAP networking mode (192.168.1.33 which is my
IP addr in guest), but getting 'no route to host' for any... (1 Reply)
Discussion started by: temp-usr
1 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)