Well, I'm thoughly perplexed. I set up a US Robotics modem on a RHEL5 server a while back using the Redhat doc-7217 cheat sheet. I was able to dial in to the server each time I tested it (about 10 times) but when I actually was off site and tried to dial in, the modem would not answer the phone.

Back on site, I have been unable to get the modem to respond to wvdialconf (gives ttyS0<Info>: Device or resource busy
Port Scan<*1>: S0 error). I have tried moving the modem to ttyS1, but then I get the "device busy" message on that port. 'Tried fiddling about with the interrups... still same results. So it seems that when the getty is initialized, any port specified becomes "busy".

I thought it might be the modem thowing a fit, so I bought a new serial modem (Zoom this time) and am having the same issue. I moved the modem(s) to different servers, thinking that the serial port(s) were foobar, but am having the same results on any RHEL5 box I move modems to (works fine from an XP RAS server.)

The question is this... "Why did it work, albeit briefly, when I first did the install and, why can't I get it to work now on any machine I hook the modems to?

I use dialin to access my server farm from remote locations when power has taken down the external network link and badly need the connection and don't want to have to rely on an XP box.

Any ideas would be greatly appreciated.

Thanks in advance!

-l-