Sorry but I have to use pine via telnet to respond to the replies.
I expected to be re-directed to a startup web page when I tried to use the browser but that did not happen - nothing happened the first time. I couldn't get to any web pages or use telnet or ssh. Yet route -r showed there was some sort of connection and the indicator for the ethernet connection showed there was some sort of connection (it was flashing and packets were being sent and received). I guessed at the gateway and dns and was able to ping them but that was as far as I could go until I used a route command to specify a default route to the gateway. I can tell from resolv.conf that dhcp is specifying the dns (yet I wasn't originally able to surf web pages unles I specified the ip address).
An IT came up last night with his laptop (running Windows of course) and was immediately able to connect. It stays connected but for some reason the DNS gets lost and I have to repeatedly re-activate through the gui network interface.
How can I look at dhcp? When I used to type in all the commands manually to connect (either wired or wirelessly using ifconfig, iwconfig, dhclient) dhclient would give me info on the leases. But for some time it doesn't give me any indication of what is going on.
I'm going to try the service and dig example (but I wanted to send this first in case it causes any problems with connecting).
Thanks.
Rick B.
Rick Bilonick mailto:rab@nauticom.net http://www.nauticom.net/users/rab
RICHARD wrote:
Sorry but I have to use pine via telnet to respond to the replies.
I expected to be re-directed to a startup web page when I tried to use the browser but that did not happen - nothing happened the first time. I couldn't get to any web pages or use telnet or ssh. Yet route -r showed there was some sort of connection and the indicator for the ethernet connection showed there was some sort of connection (it was flashing and packets were being sent and received). I guessed at the gateway and dns and was able to ping them but that was as far as I could go until I used a route command to specify a default route to the gateway. I can tell from resolv.conf that dhcp is specifying the dns (yet I wasn't originally able to surf web pages unles I specified the ip address).
An IT came up last night with his laptop (running Windows of course) and was immediately able to connect. It stays connected but for some reason the DNS gets lost and I have to repeatedly re-activate through the gui network interface.
How can I look at dhcp? When I used to type in all the commands manually to connect (either wired or wirelessly using ifconfig, iwconfig, dhclient) dhclient would give me info on the leases. But for some time it doesn't give me any indication of what is going on.
I'm going to try the service and dig example (but I wanted to send this first in case it causes any problems with connecting).
Thanks.
Rick B.
Rick Bilonick mailto:rab@nauticom.net http://www.nauticom.net/users/rab
I wonder if they are using UPnP (Universal Plug-and-Play) to set things up? I don't think it is supported by default by Fedora. It is turned on by default under Windows XP. I am not sure about under Windows 98. In any case, it sounds like they are making use of some of the non-standard features of dhcp used by Windows.
You should take a look at your logs to see if there is any information about this...
Mikkel
On Mon, 2006-05-01 at 16:10 -0400, RICHARD wrote:
I expected to be re-directed to a startup web page when I tried to use the browser but that did not happen - nothing happened the first time.
I've seen that sort of thing with an ISP: If you get your logon credentials wrong you have no internet access, just their local webserver responding to all queries, with instructions for how you should fix things. However, it only worked with MSIE. It didn't work with Firefox, not even on Windows. I'm guessing some non-standard redirection technique is involved.
I guessed at the gateway and dns and was able to ping them but that was as far as I could go until I used a route command to specify a default route to the gateway. I can tell from resolv.conf that dhcp is specifying the dns (yet I wasn't originally able to surf web pages unles I specified the ip address).
If the gateway doesn't change, you could try specifying such details by hand, and using your own DNS server (if they don't prevent that by blocking the port). But you could still suffer another problem: If they use rapidly changing dynamic IPs, what you had for one moment might be assigned to someone else in a few minutes, and you can't have two different PCs trying to use the same IP concurrently.
One thing that springs to mind is that they may have a user jacked into their network that's running its own DHCP server and it's messing up networking for everyone else. If that's the case, you can configure your DHCP client to ignore DHCP servers from other addresses, but you'll have to read the man page about how to do it.