search for: currend

For when is scheduled to have the xen-install-fc5 available. FC5 is now the currend Fedora Core release. Thans in advance _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...re of related to > correct name > resolution (because that was what I found that the error I receive is > related to on the web). > The only interesting thing i found is that running "host -t SRV > _kerberos._udp.example.corp" on faiserver.example.corp prints only the > currend DC while running it on location-000001.example.corp > prints both DCs > ...never the less I am not sure if this might be a cause or > is just another > bad result of the one way sync. > Maybe someone has an idea? > > Attached you can find two files (one for each DC) with all...

...ady checked all topics I am aware of related to correct name resolution (because that was what I found that the error I receive is related to on the web). The only interesting thing i found is that running "host -t SRV _kerberos._udp.example.corp" on faiserver.example.corp prints only the currend DC while running it on location-000001.example.corp prints both DCs ...never the less I am not sure if this might be a cause or is just another bad result of the one way sync. Maybe someone has an idea? Attached you can find two files (one for each DC) with all information that I found could be re...

...rrect name > > resolution (because that was what I found that the error I receive is > > related to on the web). > > The only interesting thing i found is that running "host -t SRV > > _kerberos._udp.example.corp" on faiserver.example.corp prints only the > > currend DC while running it on location-000001.example.corp > > prints both DCs > > ...never the less I am not sure if this might be a cause or > > is just another > > bad result of the one way sync. > > Maybe someone has an idea? > > > > Attached you can find two...

...re of related to > correct name > resolution (because that was what I found that the error I receive is > related to on the web). > The only interesting thing i found is that running "host -t SRV > _kerberos._udp.example.corp" on faiserver.example.corp prints only the > currend DC while running it on location-000001.example.corp > prints both DCs > ...never the less I am not sure if this might be a cause or > is just another > bad result of the one way sync. > Maybe someone has an idea? > > Attached you can find two files (one for each DC) with all...

...re of related to > correct name > resolution (because that was what I found that the error I receive is > related to on the web). > The only interesting thing i found is that running "host -t SRV > _kerberos._udp.example.corp" on faiserver.example.corp prints only the > currend DC while running it on location-000001.example.corp > prints both DCs > ...never the less I am not sure if this might be a cause or > is just another > bad result of the one way sync. > Maybe someone has an idea? > > Attached you can find two files (one for each DC) with all...

...re of related to > correct name > resolution (because that was what I found that the error I receive is > related to on the web). > The only interesting thing i found is that running "host -t SRV > _kerberos._udp.example.corp" on faiserver.example.corp prints only the > currend DC while running it on location-000001.example.corp > prints both DCs > ...never the less I am not sure if this might be a cause or > is just another > bad result of the one way sync. > Maybe someone has an idea? > > Attached you can find two files (one for each DC) with all...