RE: Windows Domains? (was: getting a 3C905B network card
-Original Message- From: deFreese, Barry [mailto:[EMAIL PROTECTED]] Erik, In Windows, do an ipconfig /all and one of the options should say DHCP Enabled (Yes/No). Barry deFreese NTS Technology Servi Wow. It says DHCP Enabled: No. That's strange -- I thought that DHCP was used throughout the entire building. I'll have to check on this... thanks Barry. Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Windows Domains? (was: getting a 3C905B network card
Wow. It says DHCP Enabled: No. That's strange -- I thought that DHCP was used throughout the entire building. I'll have to check on this... thanks Barry. Erik Actually, that is good if you have a static IP. That means you can assign the same IP, Gateway, and DNS information to your Linux config. The only thing that may get hosed up on the Microsoft networking side is WINS if your company is using it. Barry deFreese NTS Technology Services Manager Nike Team Sports (949)-616-4005 [EMAIL PROTECTED] Technology doesn't make you less stupid; it just makes you stupid faster. Jerry Gregoire - Former CIO at Dell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Windows Domains? (was: getting a 3C905B network card
-Original Message- So then, what should I do from there? That's exactly what I did (except the /release /renew part) in the first place, but when I statically assigned myself that IP in Linux by writing it to /etc/network/interfaces, I had the problem. The ipconfig command by itself just reports what Windows believes is its current IP address. The /release tells Windows to tell the DHCP server that it no longer wants this address and the server can have it back to reallocate to whatever client needs one. The /renew tells Windows to ask the DHCP server for an address, and in many cases will result in the same IP being given back to the client. If the /renew doesn't work, there's something else at work on your network, such as a network switch getting confused (we had some similar problems a few years ago on our new ATM network). Generally, waiting 15 minutes or so allowed the glitch to clear up out of the network hardware. (Or alternatively we could move to a different network port and get going again.) Well, I was in Linux again today and I did a couple of things. Here is what I did and the response I got, can anyone comment on this? 1) I installed pump upon the recommendation of a co-worker (using apt-get install pump, from the CD-ROM). But executing pump -i eth0 --status yields the error message Operation failed. So I must need to configure it or something. 2) I changed the /etc/network/interfaces file to say auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp (without the indent) But then when I executed /etc/init.d/networking restart, it just hung for a while and said Done. No IP address was assigned, according to /sbin/ifconfig. 3) I went back into Windows and tried the /release and /renew arguments to ipconfig. Here is the response I got: H:\ipconfig /release Windows 2000 IP Configuration Error: No adapters bound to TCP/IP are enabled for DHCP H:\ipconfig /renew Windows 2000 IP Configuration Error: No adapters bound to TCP/IP are enabled for DHCP I'm pretty clueless at this point. Part (3) above suggests that DHCP isn't even being used here, but I'm pretty certain that DHCP is indeed being used by my company's network. What's the deal? Anyone have any advice? I appreciate it. Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Windows Domains? (was: getting a 3C905B network card
Erik, In Windows, do an ipconfig /all and one of the options should say DHCP Enabled (Yes/No). Barry deFreese NTS Technology Services Manager Nike Team Sports (949)-616-4005 [EMAIL PROTECTED] Technology doesn't make you less stupid; it just makes you stupid faster. Jerry Gregoire - Former CIO at Dell -Original Message- From: Price, Erik [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 10, 2002 1:34 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Windows Domains? (was: getting a 3C905B network card -Original Message- So then, what should I do from there? That's exactly what I did (except the /release /renew part) in the first place, but when I statically assigned myself that IP in Linux by writing it to /etc/network/interfaces, I had the problem. The ipconfig command by itself just reports what Windows believes is its current IP address. The /release tells Windows to tell the DHCP server that it no longer wants this address and the server can have it back to reallocate to whatever client needs one. The /renew tells Windows to ask the DHCP server for an address, and in many cases will result in the same IP being given back to the client. If the /renew doesn't work, there's something else at work on your network, such as a network switch getting confused (we had some similar problems a few years ago on our new ATM network). Generally, waiting 15 minutes or so allowed the glitch to clear up out of the network hardware. (Or alternatively we could move to a different network port and get going again.) Well, I was in Linux again today and I did a couple of things. Here is what I did and the response I got, can anyone comment on this? 1) I installed pump upon the recommendation of a co-worker (using apt-get install pump, from the CD-ROM). But executing pump -i eth0 --status yields the error message Operation failed. So I must need to configure it or something. 2) I changed the /etc/network/interfaces file to say auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp (without the indent) But then when I executed /etc/init.d/networking restart, it just hung for a while and said Done. No IP address was assigned, according to /sbin/ifconfig. 3) I went back into Windows and tried the /release and /renew arguments to ipconfig. Here is the response I got: H:\ipconfig /release Windows 2000 IP Configuration Error: No adapters bound to TCP/IP are enabled for DHCP H:\ipconfig /renew Windows 2000 IP Configuration Error: No adapters bound to TCP/IP are enabled for DHCP I'm pretty clueless at this point. Part (3) above suggests that DHCP isn't even being used here, but I'm pretty certain that DHCP is indeed being used by my company's network. What's the deal? Anyone have any advice? I appreciate it. Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Windows Domains? (was: getting a 3C905B network card
Sorry, this is from a failed delivery so I am re-forwarding -- please consider one quote level as my original message: --- Robert Ian Smit [EMAIL PROTECTED] wrote: * Erik Price [EMAIL PROTECTED] [04-10-2002 22:34]: argument), so what steps should I take to get DHCP to assign me an IP address? ifconfig eth0 address XXX.XX.X.XXX As you say DHCP assigns an address, with ifconfig you can manually add an address (and change other options) [...] You need to make sure that you have an IP-address, use ifconfig with no parameters to display. You need a default gateway. Check with route You need DNS. Check /etc/resolv.conf Okay, now I'm having a different problem entirely. I did everything you described, grabbing the network information from ipconfig in MS DOS and then entering it into the /etc/network/interfaces file with vi, and executing the /etc/init.d/networking restart script. It worked great. After creating a /etc/resolv.conf (Debian doesn't come with a blank one by default), I was able to fetch web pages and even use Lynx. I was so happy. So the next step was to paste the STDERR output from my failed startx commands. Unfortunately, I couldn't access my company email account from Linux, and using Lynx to access this freebie Yahoo account didn't work because Lynx doesn't yet support https. So I couldn't post the STDERR file! But this is the least of my problems. Because upon restarting the machine and booting back into Win2k, I discovered that I couldn't even log into the machine! It turns out that at my company, the login is controlled by something called a domain, which is some kind of network-based authentication system. I don't really understand it myself. I ended up having to call tech support and they managed to help me get it all online, apparently by forcing the machine to accept DHCP again. Does anyone know how to get Linux to work cooperatively alongside this MS domain business? In other words, I could boot right back into Linux and execute /etc/init.d/networking restart again, and be using the web from Linux, but then when I go back to Windows I'm going to have a problem. And I can't keep calling tech support for this. Surely there is another on this list who knows how to handle these domains. I am grateful for any advice. Erik PS: In case it's not obvious, I'm not a Windows guru. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com = Microsoft: Yes, we'll settle for a larger market share as punishment. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Windows Domains? (was: getting a 3C905B network card
Erik Price wrote: Unfortunately, I couldn't access my company email account from Linux, and using Lynx to access this freebie Yahoo account didn't work because Lynx doesn't yet support https. Check out lynx-ssl, or even links-ssl, from the non-US section of Debian. Because upon restarting the machine and booting back into Win2k, I discovered that I couldn't even log into the machine! It turns out that at my company, the login is controlled by something called a domain, which is some kind of network-based authentication system. I don't really understand it myself. I ended up having to call tech support and they managed to help me get it all online, apparently by forcing the machine to accept DHCP again. Does anyone know how to get Linux to work cooperatively alongside this MS domain business? In other words, I could boot right back into Linux and execute /etc/init.d/networking restart again, You shouldn't need to do this; '/etc/init.d/networking start' should be executed at startup. and be using the web from Linux, but then when I go back to Windows I'm going to have a problem. Why do you think this? Have you tried it? I don't see how the Windows network settings would affect Linux, or vice versa. Maybe this is all easier than you think. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Windows Domains? (was: getting a 3C905B network card
snip Does anyone know how to get Linux to work cooperatively alongside this MS domain business? In other words, I could boot right back into Linux and execute /etc/init.d/networking restart again, and be using the web from Linux, but then when I go back to Windows I'm going to have a problem. And I can't keep calling tech support for this. Surely there is another on this list who knows how to handle these domains. I am grateful for any advice. Erik PS: In case it's not obvious, I'm not a Windows guru. The windows domain should have nothing to do with any of your problems. After reading all of this I am still not quite sure what problem you are having? Are you saying that you copied your DHCP allocated IP address information from your Win2K and made it a static IP under Linux? You should be able to get a DHCP address from Linux utilizing the organizations DHCP server. If your company is running a WINS server, you may be having some issues since I assume that your Linux computer name is different than your Windows computer name. Just as an FYI, yes the Windows Domain controls authentication and authorization for network resources in a Microsoft network. In a Windows domain you must have at least one Primary Domain Controller (PDC) which is the server that all of the computers on the network authenticate against. Obviously I am oversimplifying quite a bit. Barry deFreese NTS Technology Services Manager Nike Team Sports (949)-616-4005 [EMAIL PROTECTED] Technology doesn't make you less stupid; it just makes you stupid faster. Jerry Gregoire - Former CIO at Dell -Original Message- From: Erik Price [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 09, 2002 6:01 AM To: [EMAIL PROTECTED] Subject: Windows Domains? (was: getting a 3C905B network card Sorry, this is from a failed delivery so I am re-forwarding -- please consider one quote level as my original message: --- Robert Ian Smit [EMAIL PROTECTED] wrote: * Erik Price [EMAIL PROTECTED] [04-10-2002 22:34]: argument), so what steps should I take to get DHCP to assign me an IP address? ifconfig eth0 address XXX.XX.X.XXX As you say DHCP assigns an address, with ifconfig you can manually add an address (and change other options) [...] You need to make sure that you have an IP-address, use ifconfig with no parameters to display. You need a default gateway. Check with route You need DNS. Check /etc/resolv.conf Okay, now I'm having a different problem entirely. I did everything you described, grabbing the network information from ipconfig in MS DOS and then entering it into the /etc/network/interfaces file with vi, and executing the /etc/init.d/networking restart script. It worked great. After creating a /etc/resolv.conf (Debian doesn't come with a blank one by default), I was able to fetch web pages and even use Lynx. I was so happy. So the next step was to paste the STDERR output from my failed startx commands. Unfortunately, I couldn't access my company email account from Linux, and using Lynx to access this freebie Yahoo account didn't work because Lynx doesn't yet support https. So I couldn't post the STDERR file! But this is the least of my problems. Because upon restarting the machine and booting back into Win2k, I discovered that I couldn't even log into the machine! It turns out that at my company, the login is controlled by something called a domain, which is some kind of network-based authentication system. I don't really understand it myself. I ended up having to call tech support and they managed to help me get it all online, apparently by forcing the machine to accept DHCP again. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com = Microsoft: Yes, we'll settle for a larger market share as punishment. __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Windows Domains? (was: getting a 3C905B network card
Erik Price wrote: Because upon restarting the machine and booting back into Win2k, I discovered that I couldn't even log into the machine! It turns out that at my company, the login is controlled by something called a domain, which is some kind of network-based authentication system. I don't really understand it myself. I ended up having to call tech support and they managed to help me get it all online, apparently by forcing the machine to accept DHCP again. Does anyone know how to get Linux to work cooperatively alongside this MS domain business? In other words, I could boot right back into Linux and execute /etc/init.d/networking restart again, and be using the web from Linux, but then when I go back to Windows I'm going to have a problem. And I can't keep calling tech support for this. Surely there is another on this list who knows how to handle these domains. In the domain model, the login athentication is not (usually) handled by the local Windows PC; rather, the local box passes the username/password to a domain controller (Primary Domain Controller (PDC) or Backup Domain Controller (BDC)) somewhere in the network. This Domain Controller (DC) is a server that the system administrators have set up somewhere on your network. The DC then checks to make sure you're an approved user and that your password is correct, then sends a signal back down to the local computer saying it's okay for the computer to let you log in and use that computer. It also manages such things as what rights you have to access certain network resources (shared directories, printers, etc). This way, instead of the tech support guys having to go to each machine that you might theoretically log into and add you as a valid user (and then go around and synch your password if you were to ever change it), they have a centralized database that keeps track of you and your password and your rights. Microsoft has moved from the Domain model to the Active Directory model, but much of the world has not yet made the transition. The same sort of thing can be done in a more standardized model with other tools, such as LDAP (of which Active Directory is supposedly compliant), but which method is used is determined by the system admins, not by the users, so you're stuck working in the Domain model. Nonetheless, that shouldn't be an issue. Your Windows side should be unaffected by anything you do on the Linux side, and your Linux side does not need to play with the Domain, inasmuch as you can set it up to let you log in locally, without authenticating through a centralized server. Of course, this means if you go to your neighbor's Linux box, you won't be able to log in there unless he has set you up to do so, whereas you could log into his Windows box, because he doesn't control that; the sys admins (via the domain) control it. Unless you gave the Linux box the same name as the Windows side, AND added it to the Windows domain (I'd guesstimate a 0.0002% chance that happened - in other words, it didn't), OR unless the Windows domain is doing something odd with the MAC address of your NIC (also highly unlikely), anything you do on the Linux side will have absolutely no affect on the Windows side. In other words, I can say with a high degree of confidence, your Windows problem was simply a coincidence. If it should happen again, I'll gladly retract this claim. Before trying it, add yourself a local account on the Windows box (assuming you're an Admin on the local box, and add your local account to the local Administrators group), so that if it does happen again, you can log in locally, bypassing the domain authentication. Then bring up a command prompt, and type ipconfig to see what your current IP settings are. If necessary, ipconfig /release followed by ipconfig /renew should renew your DHCP settings. (Depending on your version of Windows, it might be winipcfg instead of ipconfig.) Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Windows Domains? (was: getting a 3C905B network card
--- Kent West [EMAIL PROTECTED] wrote: Nonetheless, that shouldn't be an issue. Your Windows side should be unaffected by anything you do on the Linux side, and your Linux side does not need to play with the Domain, inasmuch as you can set it up to let you log in locally, without authenticating through a centralized server. Of course, this means if you go to your neighbor's Linux box, you won't be able to log in there unless he has set you up to do so, whereas you could log into his Windows box, because he doesn't control that; the sys admins (via the domain) control it. Kent, Thanks very much for the explanation of how that works. I think that my problem happened because when I restarted the machine and booted into Linux, I manually assigned myself a static IP address that had been formerly provided for me by DHCP. So what I'm wondering is whether or not I will be able to use DHCP in Linux without Linux talking to the Domain Controllers. IOW, what I am wondering is whether or not the machine will still be assigned a dynamic IP when it is booted into Linux. In Linux, I could not access the network until I did assign myself a static IP, which is possibly what caused the problem, but this may be because I didn't set up the right services to allow my Linux box to be assigned a dynamic IP. So, in short, I won't override DHCP again, because I'm afraid that's what fudged up my network connection, keeping me from logging into the box via the domain. Before trying it, add yourself a local account on the Windows box (assuming you're an Admin on the local box, and add your local account to the local Administrators group), so that if it does happen again, you can log in locally, bypassing the domain authentication. Good idea. I didn't know I could do this. Then bring up a command prompt, and type ipconfig to see what your current IP settings are. If necessary, ipconfig /release followed by ipconfig /renew should renew your DHCP settings. (Depending on your version of Windows, it might be winipcfg instead of ipconfig.) So then, what should I do from there? That's exactly what I did (except the /release /renew part) in the first place, but when I statically assigned myself that IP in Linux by writing it to /etc/network/interfaces, I had the problem. Thanks again for the explanations of how this works. I look forward to solving this problem. Erik __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Windows Domains? (was: getting a 3C905B network card
Erik Price wrote: Thanks very much for the explanation of how that works. I think that my problem happened because when I restarted the machine and booted into Linux, I manually assigned myself a static IP address that had been formerly provided for me by DHCP. Still shouldn't have mattered. Giving yourself a static IP address on your Linux box that is the same number as what your Windows side had shouldn't prevent your Windows box from getting a valid DHCP address next time it booted. However, since Linux didn't register with the DHCP server, the DHCP server might have given out the same address to another Windows (or other DHCP client) box on the network. In such a case, there'd be two machines on the network with the same IP. After that, your network admins (or perhaps some automated response system) may have done something to break your Windows network, but I seriously doubt it. I'm still thinking it was just a coincidence that Windows lost its networking (after all, it *is* Windows . . .). But at any rate, you don't want to assign a static IP address to your Linux box unless your network admins have given you a static IP address. Conflicts might occur, as mentioned above. So what I'm wondering is whether or not I will be able to use DHCP in Linux without Linux talking to the Domain Controllers. Yes. IOW, what I am wondering is whether or not the machine will still be assigned a dynamic IP when it is booted into Linux. Yes, if you configure it properly. Make your /etc/networking/interfaces file look something like: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # automatically added when upgrading auto eth0 #iface eth0 inet static #address 150.252.xxx.yyy #network 150.252.xxx.yyy #netmask 255.255.xxx.yyy #broadcast 150.252.xxx.yyy #gateway 150.252..xxx.yyy iface eth0 inet dhcp Notice I've commented out the static entries and replaced them with the one line for dhcp. Then just restart networking and you should be good to go. In Linux, I could not access the network until I did assign myself a static IP, which is possibly what caused the problem, but this may be because I didn't set up the right services to allow my Linux box to be assigned a dynamic IP. So, in short, I won't override DHCP again, because I'm afraid that's what fudged up my network connection, keeping me from logging into the box via the domain. Again, I can't think of any way that it would have fudge up your network connection from Windows. Then bring up a command prompt, and type ipconfig to see what your current IP settings are. If necessary, ipconfig /release followed by ipconfig /renew should renew your DHCP settings. (Depending on your version of Windows, it might be winipcfg instead of ipconfig.) So then, what should I do from there? That's exactly what I did (except the /release /renew part) in the first place, but when I statically assigned myself that IP in Linux by writing it to /etc/network/interfaces, I had the problem. The ipconfig command by itself just reports what Windows believes is its current IP address. The /release tells Windows to tell the DHCP server that it no longer wants this address and the server can have it back to reallocate to whatever client needs one. The /renew tells Windows to ask the DHCP server for an address, and in many cases will result in the same IP being given back to the client. If the /renew doesn't work, there's something else at work on your network, such as a network switch getting confused (we had some similar problems a few years ago on our new ATM network). Generally, waiting 15 minutes or so allowed the glitch to clear up out of the network hardware. (Or alternatively we could move to a different network port and get going again.) Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
