On Fri, 2005-03-04 at 12:34, Rick Stevens wrote: > Scot L. Harris wrote: > > > > Could this be an issue with NetworkManager? Been using that for awhile > > mainly with the wireless connection. I noticed this problem when I > > traveled to another site and connected up using a wired connection. I > > have since reproduced the problem here. I think when I first brought > > the system up I used the wired connection. But installed NetworkManager > > to get the wireless working. > > If "NetworkManager" is the same as system-config-network, I've never > trusted it. My network stuff is set up by hand (I'm old-school...well, > maybe just old). However, I don't run VPNs here for any of my stuff > so I really can't speak to the difficulty of setting up VPNs manually. > > > Is it possible to extract NetworkManager completely from a system? I > > may try that next just to see if I can get the wired connection working. > > Someone else would have to tackle that one. I don't use > "system-config-network" and I'm not sure if that's what you call Network > Manager or not. Rick, NetworkManager is a new widget that is suppose to manage your network connections. Appears to be geared more toward laptop type users. It is very different from the system-config-network tool. I came across a message that seemed to indicate that NetworkManager munges some of the files and leaves that that way when it is removed. I am going to try this weekend to experiment with removing NetworkManager and setting up the wired NIC manually to see if the VPN will resolve names correctly in that setup. I think I did that when initially setup the laptop since I had trouble getting the wireless to work. Wireless worked after using NetworkManager. It still needs some work IMHO. So by Sunday I hope to have some additional data points on this problem. -- Scot L. Harris webid@xxxxxxxxxx FORTUNE PROVIDES QUESTIONS FOR THE GREAT ANSWERS: #15 A: The Royal Canadian Mounted Police. Q: What was the greatest achievement in taxidermy?
