On 07/02/2012 10:49 PM, Christopher A. Williams wrote:
>> I'm always happy to try and recreate the failure. Just so happens I can't
>> at the
>> > moment. Post the bugzilla And try my system You may find
>> > something
>> > interesting.
> Happy to give this a shot as well. I'll send
On Mon, 2012-07-02 at 22:35 +0800, Ed Greshko wrote:
> Cute.
>
> Going to have a "I've been to more places than you have" contest? :-)
>
> I guess that means it is my turn to recount the adventures I had in India with
> satellite links and trying to do LDAP directory replication to Kenya.
On 07/02/2012 10:43 PM, Lawrence Graves wrote:
> I would greatly appreciate it if we would not get personal about this
> problem. If
> we spend more energy on solving the problem more people will benifit. Keep it
> real,
> please.
I've not see anyone getting personal. All in fun...
But, if yo
resolve all DNS host names as expected.
RDP sessions still fail however. They either connect and hang after a
few seconds, or they simply don't connect at all. It's exactly the same
symptoms as when connected via the VPN. Clearly, there's some sort of
issue with both gnome-rdp and R
names as expected.
> >
> > RDP sessions still fail however. They either connect and hang after a
> > few seconds, or they simply don't connect at all. It's exactly the same
> > symptoms as when connected via the VPN. Clearly, there's some sort of
> > issue
On 07/02/2012 10:24 PM, Christopher A. Williams wrote:
> On Mon, 2012-07-02 at 22:04 +0800, Ed Greshko wrote:
>> On 07/02/2012 09:23 PM, Ed Greshko wrote:
>>> Good luck
>> Oh, one more thing.
>>
>> I am sure this is not impressive. But, I'm located in Taiwan. I have a
>> vpn
>> accou
On Mon, 2012-07-02 at 22:04 +0800, Ed Greshko wrote:
> On 07/02/2012 09:23 PM, Ed Greshko wrote:
> > Good luck
>
> Oh, one more thing.
>
> I am sure this is not impressive. But, I'm located in Taiwan. I have a
> vpn
> account which places my system in Los Angles, CA.
>
You're rig
On 07/02/2012 08:33 PM, Christopher A. Williams wrote:
> Thanks for trying...
Since you can't get it to work properly for you in any situation you've tried.
And I
seem unable to get it to fail. I'll offer you the chance to connect to my
Win2008
server over the internet if you like.
Just conta
On 07/02/2012 09:23 PM, Ed Greshko wrote:
> Good luck
Oh, one more thing.
I am sure this is not impressive. But, I'm located in Taiwan. I have a vpn
account which places my system in Los Angles, CA.
I connected to the VPN using OpenVPN and NetworkManager (I've not had any
problems
r a
> few seconds, or they simply don't connect at all. It's exactly the same
> symptoms as when connected via the VPN. Clearly, there's some sort of
> issue with both gnome-rdp and Reminna.
If two separate apps are experience the same problem, then that tells me
it's n
On 07/02/2012 08:33 PM, Christopher A. Williams wrote:
> On Mon, 2012-07-02 at 13:15 +0800, Ed Greshko wrote:
>> On 07/02/2012 10:08 AM, Ed Greshko wrote:
>>> I can also tell you that I have installed Window 2003 Server and added the
>>> role of
>>> "Terminal Server". The Windows 2003 is running
irms a configuration issue at your end.
I must respectfully disagree. You confirmed that you can connect at
least briefly to a Windows Server VM from inside a network, with no vpn
in the picture.
Based on what I've found, I am now 100% certain there is an issue with
gnome-rdp / Reminna AND wit
On 07/02/2012 10:08 AM, Ed Greshko wrote:
> I can also tell you that I have installed Window 2003 Server and added the
> role of
> "Terminal Server". The Windows 2003 is running in a Virtual Box VM with the
> VM
> network adapter *Bridged* to the network adapter of meimei (F16).
OK I have
ed Remmina on meimei and very successfully connected to winserv and got a
remote
desktop. No problems at all.
>
> RDP sessions still fail however. They either connect and hang after a
> few seconds, or they simply don't connect at all. It's exactly the same
> symptoms as when con
On 07/01/2012 02:43 PM, Christopher A. Williams wrote:
It's
specifically Network Manager and gnome-rdp / Reminna that are having
issues.
Do you need NM running, or can you turn it off and use the older network
service? My experience with NM has been that unless I need WiFi, I'm
On Sun, 2012-07-01 at 22:58 +0800, Ed Greshko wrote:
> On 07/01/2012 10:56 PM, Ed Greshko wrote:
> > When you say the ping works from the Linux system you are using the IP
> > address, right?
>
> That was a dumb thing for me to say since I showed you could use the hostname
> if you
> have it in
N. Clearly, there's some sort of
issue with both gnome-rdp and Reminna.
> OK When you say the ping works from the Linux system you are using the IP
> address, right? I say that since you say the "hostnames are not resolved".
> Are you
> expecting the hostna
On 07/01/2012 10:56 PM, Ed Greshko wrote:
> When you say the ping works from the Linux system you are using the IP
> address, right?
That was a dumb thing for me to say since I showed you could use the hostname
if you
have it in the hosts file.
Sue me It is late here in Taiwan. :-)
ross
> the board is yes. We can ping, use Remote Desktop, and use all Web
> services on the inside network. We can also use the VI Client from
> VMware to remotely administer the system and all additional feature
> work.
>
> When using the vpnc client and Network Manager, the answers a
ote administration purposes.
All of these boxes are actually VMs running in a VMware vSphere based
virtual environment (not necessary to the conversation, but so you have
the full picture).
> First you establish a VPN connection from OUT to the Cisco. Then, you want
> to use
> t
#x27;ll call them IN and OUT with the following IP addresses.
IN=192.168.0.20
OUT=192.168.1.20
First you establish a VPN connection from OUT to the Cisco. Then, you want to
use
the Gnome-rdp client or Remmina client to obtain a remote desktop connection.
Is that correct so far? If it is, could y
domain is added to the domain search list as a part of
connecting to the VPN.
What we are having trouble with is that gnome-rdp simply dies when
trying to connect. Even when successful, the VPN connection appears to
just hang after a few seconds.
Conversely, I can run a Windows 7 virtual machine o
to the VPN.
What we are having trouble with is that gnome-rdp simply dies when
trying to connect. Even when successful, the VPN connection appears to
just hang after a few seconds.
Conversely, I can run a Windows 7 virtual machine on the same physical
computer that's having trouble with vpnc/
On Wed, Jun 27, 2012 at 02:45:15PM -0700, Joe Zeff wrote:
> On 06/27/2012 02:34 PM, Lawrence Graves wrote:
> >192.168.1.84 israel.risingstar.local
>
> That's on a non-routable subnet. Considering that nslookup is a
> program to query Internet domain name servers, there's no way in the
> world tha
On Wed, Jun 27, 2012 at 03:31:15PM -0600, Lawrence Graves wrote:
> >What hostname are you trying to find? Maybe there's something
> >wrong with the name, or the way you're specifying it. Is it fully
> >qualified, as mine is?
>
> server can't find risingstar: NXDOMAIN This the results of nslookup.
On Wed, Jun 27, 2012 at 02:44:04PM -0600, Lawrence Graves wrote:
> >Dude, replace "[hostname]" with the hostname for the machine you're
> >trying to access.
>
> Thanks for the help. I don't care what I put in the brackets it
> still comes back to what you see in this post.
Go back and read what I
On 06/27/2012 09:52 PM, Ed Greshko wrote:
> On 06/28/2012 09:50 AM, Kevin Martin wrote:
>> nslookup (or some versions of it) used to honor the /etc/nsswitch.conf file
>> so if hosts was defined
>>
>> hosts: dns file
>>
>> in /etc/nsswitch.conf, "nslookup risingstar" would return the address (*if*
On Thu, 2012-06-28 at 10:52 +0800, Ed Greshko wrote:
> In all my years I can't recall ever coming across that behaviorand
> it doesn't make much sense to me that a utility/tool meant to query
> the DNS would do this. dig also doesn't.
>
> If you can recall what version did this I'd be intere
On 06/28/2012 09:50 AM, Kevin Martin wrote:
> nslookup (or some versions of it) used to honor the /etc/nsswitch.conf file
> so if hosts was defined
>
> hosts: dns file
>
> in /etc/nsswitch.conf, "nslookup risingstar" would return the address (*if*
> /etc/hosts had "192.168.0.18
I could find no
On 06/27/2012 07:07 PM, Ed Greshko wrote:
> On 06/28/2012 05:34 AM, Lawrence Graves wrote:
>> 192.168.1.84 israel.risingstar.local
>
> Ahhh That is in your /etc/hosts file And you said you were doing
>
> nslookup risingstar ??
>
> If that is so, you have 2 problems.
>
> 1. nslo
On 06/28/2012 05:34 AM, Lawrence Graves wrote:
> 192.168.1.84 israel.risingstar.local
Ahhh That is in your /etc/hosts file And you said you were doing
nslookup risingstar ??
If that is so, you have 2 problems.
1. nslookup doesn't reference data in the hosts file. It only does
On 06/27/2012 02:54 PM, Steve Searle wrote:
I didn't see the start of this thread but couldn't he be running his own
DNS? I do, and nsloolup will find my own machines.
That, of course, would be different. However, if he were doing that,
he'd probably know enough not to put the arguments for n
Around 10:45pm on Wednesday, June 27, 2012 (UK time), Joe Zeff scrawled:
> On 06/27/2012 02:34 PM, Lawrence Graves wrote:
> >192.168.1.84 israel.risingstar.local
>
> That's on a non-routable subnet. Considering that nslookup is a program
> to query Internet domain name servers, there's no way i
On 06/27/2012 02:34 PM, Lawrence Graves wrote:
192.168.1.84 israel.risingstar.local
That's on a non-routable subnet. Considering that nslookup is a program
to query Internet domain name servers, there's no way in the world that
they'd know its address. (And a good thing, too! Do you have a
On 06/27/2012 03:39 PM, Joe Zeff wrote:
On 06/27/2012 02:31 PM, Lawrence Graves wrote:
server can't find risingstar: NXDOMAIN This the results of nslookup. Yes
it is fully qualified. This problem only came when I went from Fedora 16
to 17.
Are you using just risingstar, or are you using risin
On 06/27/2012 02:31 PM, Lawrence Graves wrote:
server can't find risingstar: NXDOMAIN This the results of nslookup. Yes
it is fully qualified. This problem only came when I went from Fedora 16
to 17.
Are you using just risingstar, or are you using risingstar.x.y? The
first, of course, won't w
On 06/27/2012 03:26 PM, Joe Zeff wrote:
On 06/27/2012 02:07 PM, Lawrence Graves wrote:
On 06/27/2012 03:01 PM, Joe Zeff wrote:
On 06/27/2012 01:44 PM, Lawrence Graves wrote:
Thanks for the help. I don't care what I put in the brackets it still
comes back to what you see in this post.
Well,
On 06/27/2012 03:26 PM, Joe Zeff wrote:
On 06/27/2012 02:07 PM, Lawrence Graves wrote:
On 06/27/2012 03:01 PM, Joe Zeff wrote:
On 06/27/2012 01:44 PM, Lawrence Graves wrote:
Thanks for the help. I don't care what I put in the brackets it still
comes back to what you see in this post.
Well,
On 06/27/2012 02:07 PM, Lawrence Graves wrote:
On 06/27/2012 03:01 PM, Joe Zeff wrote:
On 06/27/2012 01:44 PM, Lawrence Graves wrote:
Thanks for the help. I don't care what I put in the brackets it still
comes back to what you see in this post.
Well, then, stop putting it in brackets.
[joe@
On 06/27/2012 03:01 PM, Joe Zeff wrote:
On 06/27/2012 01:44 PM, Lawrence Graves wrote:
Thanks for the help. I don't care what I put in the brackets it still
comes back to what you see in this post.
Well, then, stop putting it in brackets.
[joe@khorlia Desktop]$ nslookup khorlia.zeff.us
Serve
On 06/27/2012 01:44 PM, Lawrence Graves wrote:
Thanks for the help. I don't care what I put in the brackets it still
comes back to what you see in this post.
Well, then, stop putting it in brackets.
[joe@khorlia Desktop]$ nslookup khorlia.zeff.us
Server: 207.217.77.82
Address:2
On 06/27/2012 02:20 PM, Darryl L. Pierce wrote:
On Tue, Jun 26, 2012 at 07:42:24AM -0600, Lawrence Graves wrote:
On 06/26/2012 07:39 AM, Darryl L. Pierce wrote:
nslookup [hostname]
Password:
[root@Jehovah ~]# nslookup [hostname]
Server:192.168.1.1
Address:192.168.1.1#53
** server
On Tue, Jun 26, 2012 at 07:42:24AM -0600, Lawrence Graves wrote:
>
> On 06/26/2012 07:39 AM, Darryl L. Pierce wrote:
> >nslookup [hostname]
> Password:
> [root@Jehovah ~]# nslookup [hostname]
> Server:192.168.1.1
> Address:192.168.1.1#53
>
> ** server can't find [hostname]: NXDOMAIN
>
On 06/27/2012 12:14 AM, Lawrence Graves wrote:
> I am very sorry but certainly appreciate your help. Now go to bed. I will
> live if I
> don't get it working. I am up pretty late.
OK Well I may turn in nowit is just past midnight.
Let everyone know the results of your testing in detail
On 06/26/2012 10:11 AM, Ed Greshko wrote:
On 06/27/2012 12:08 AM, Ed Greshko wrote:
This confirms that there is a "server" running on 192.168.0.198
Sorry about all the duplicate lines.. Getting late here in Taiwan and past
my
bed time :-)
I am very sorry but certainly appreciate yo
On 06/27/2012 12:08 AM, Ed Greshko wrote:
> This confirms that there is a "server" running on 192.168.0.198
Sorry about all the duplicate lines.. Getting late here in Taiwan and past
my
bed time :-)
--
Never be afraid to laugh at yourself, after all, you could be missing out on
the j
On 06/26/2012 11:59 PM, Lawrence Graves wrote:
> I am still not able to connect.
Can you be a bit more specific?
OKlet me tell you my setup.
I have a server that I want to connect with using Remmina.
The IP address of the server side is 192.168.0.198
The IP address of the client side i
On 06/26/2012 09:48 AM, Ed Greshko wrote:
On 06/26/2012 11:41 PM, Lawrence Graves wrote:
This is where I get confused. I don't understand or know how to get to where the
client side is located.
The "client" side is the "remote" side. In other wordsit is the side where
you
are running Rem
On 06/26/2012 11:41 PM, Lawrence Graves wrote:
> This is where I get confused. I don't understand or know how to get to where
> the
> client side is located.
The "client" side is the "remote" side. In other wordsit is the side where
you
are running Remmina. Remmina is "client" software.
On 06/26/2012 09:09 AM, Ed Greshko wrote:
On 06/26/2012 10:59 PM, Lawrence Graves wrote:
I tried all that was given and I still am not able to connect. I tried Remmina
and
Gnome-rdp. Unless I am putting the information in the wrong areas, this is
confusing. I believe I have all information
On 06/26/2012 11:09 PM, Ed Greshko wrote:
> And then on the client side
>
> 1. telnet clientIP 3389
Duh
Of course I meant
1. telnet serverIP 3389
--
Never be afraid to laugh at yourself, after all, you could be missing out on
the joke
of the century. -- Dame Edna Everage
--
us
On 06/26/2012 10:59 PM, Lawrence Graves wrote:
> I tried all that was given and I still am not able to connect. I tried
> Remmina and
> Gnome-rdp. Unless I am putting the information in the wrong areas, this is
> confusing. I believe I have all information needed to insert would som
tried all that was given and I still am not able to connect. I tried
Remmina and Gnome-rdp. Unless I am putting the information in the wrong
areas, this is confusing. I believe I have all information needed to
insert would someone take me step by step in the inserting of this
information.
-
On 06/25/2012 09:25 AM, Lawrence Graves wrote:
> I made some adjustments with the firewall and I am still receiving the
> message/
> ERROR: gettaddrinfo: name or server unknown
Why not just use the IP addresses until you get things running?
--
Never be afraid to laugh at yourself, after all, y
On 06/26/2012 08:42 AM, Lawrence Graves wrote:
>
> On 06/26/2012 07:39 AM, Darryl L. Pierce wrote:
>> nslookup [hostname]
> Password:
> [root@Jehovah ~]# nslookup [hostname]
> Server:192.168.1.1
> Address:192.168.1.1#53
>
> ** server can't find [hostname]: NXDOMAIN
>
> This is what c
On 06/26/2012 07:39 AM, Darryl L. Pierce wrote:
nslookup [hostname]
Password:
[root@Jehovah ~]# nslookup [hostname]
Server:192.168.1.1
Address:192.168.1.1#53
** server can't find [hostname]: NXDOMAIN
This is what came back.
--
All things are workable but don't all things work. Pro
On Sun, Jun 24, 2012 at 07:25:26PM -0600, Lawrence Graves wrote:
> I made some adjustments with the firewall and I am still receiving
> the message/ ERROR: gettaddrinfo: name or server unknown
What do you see when you type:
nslookup [hostname]
with the hostname for the machine you're trying to a
On 06/25/2012 09:50 AM, Lawrence Graves wrote:
> I gave you the wrong information about the server. I am using RDP and all the
> ports
> of open.
I don't use xrdp. However, I believe it listens on port 3389.
You can test to make sure your server is running simply by doing something like
this.
On 06/24/2012 07:26 PM, Ed Greshko wrote:
On 06/25/2012 09:16 AM, Lawrence Graves wrote:
I am using tigervnc-server and what adjustments have to be made to the firewall?
By default the vncservers start listening on port 5901 for display :1.
So, you need to open port 5901 on the server side to
On 06/25/2012 09:16 AM, Lawrence Graves wrote:
> I am using tigervnc-server and what adjustments have to be made to the
> firewall?
By default the vncservers start listening on port 5901 for display :1.
So, you need to open port 5901 on the server side to accept connections.
--
Never be afrai
I made some adjustments with the firewall and I am still receiving the
message/ ERROR: gettaddrinfo: name or server unknown
--
All things are workable but don't all things work. Prov.3:5 & 6
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https:/
On 06/24/2012 07:09 PM, Ed Greshko wrote:
On 06/25/2012 08:58 AM, Lawrence Graves wrote:
I can't make gnome-rdp work not can I get remmina to work either. Please give me
some information concerning this problem.
I work on computers remotely and so this is a major concern for me. Thanking
On 06/25/2012 08:58 AM, Lawrence Graves wrote:
> I can't make gnome-rdp work not can I get remmina to work either. Please give
> me
> some information concerning this problem.
> I work on computers remotely and so this is a major concern for me. Thanking
> you in
> ad
I can't make gnome-rdp work not can I get remmina to work either. Please
give me some information concerning this problem.
I work on computers remotely and so this is a major concern for me.
Thanking you in advance for all your help.
--
All things are workable but don't all things wo
64 matches
Mail list logo
