Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi,
I created two VLAN's.I have a RIS Server which is in VLAN 1 and all my workstations are in VLAN 2.When i am trying to boot through network for RIS.I am unable to boot itz showing the message as ARP timedout.But i am able to use RIS in VLAN 1.Plz give me some solution.
You're unable to boot, or unable to contact the RIS server?
These appear to be two separate issues and a booting issue is not likely to be network issue.
If you're getting an ARP timeout this could be a DNS issue. If not DNS you'll want to check the routing tables on your router.
If you don't mind me asking, why would you have your RIS server on one VLAN and your workstations on another? To me this doesn't make a lot of sense. Since you use RIS to install, it should be on the same network as the workstations.
0 
"If you're getting an ARP timeout this could be a DNS issue" - Not clear on this.
ARP associates MAC addresses to IP addresses.
DNS associates domain names to IP addresses.
So how are you relating an ARP timeout to a DNS issue?
Anyway. You didn't seem to mention anything about how you're routing between your VLANs...you do know you have to route between VLANs? Which would explain alot...i.e. why you have RIS operational in the same VLAN but not in two different VLANs.
D
0
What is the definition of ARP and what all does ARP do? Read this information on ARP and what all it does, and how it does it and you'll understand why I mentioned ARP first.
No, I didn't mention anything about how I route between VLAN's. I'm not the one with problems with his VLAN's am I? All 20+ VLAN's on my network are working just fine thank you very much.
Dealing with only the information given in the original post, those seemed like the two most likely causes of such a problem.
0
Actually, that was the wrong article (it's late, I'm tired). Try this link to a search on Microsoft's site for more ARP information. Read several of the articles. ARP works along side DNS. If you're getting ARP timeout, you're not getting resolution. That relates to both ARP and DNS.
0
Curt you got issues...if you have to use some obscure set of articles then your obviously complicating a matter that's simple and fishing to justify a wrong answer rather than admit your leading them down the wrong path.
I could careless about the state of your VLAN I was responding to the posting, and the error with your troubleshooting skills...if you want to blame it on being sleepy then go to sleep but give the folks on the post a chance to get some real tangible rather than the fair tale your giving. Night Night.
D
0
Yes, you're right, I have issues *eyeroll*
I already addressed your questions about ARP, not my fault if you don't know how ARP figures into resolution on a network. As for obscure articles. There are several good ones on the second link that explain how it works within a domain environment. Not my fault if you don't understand.
Here's the rest of your original postl:
Anyway. You didn't seem to mention anything about how you're routing between your VLANs...you do know you have to route between VLANs? Which would explain alot...i.e. why you have RIS operational in the same VLAN but not in two different VLANs.
As I said before, I didn't mention how we route between VLAN's, it's a moot point. But just for you this one time I'll tell you, we us a router
*duh*!
Obviously, I do know you have to route between VLAN's or I wouldn't have mentioned that in the first place (you're really on the ball aren't you!).
The rest of your paragraph basically just makes my original point. It would make more sense for them to have their RIS server on the same VLAN as the workstations since they need it. I must point out though that properly configured VLAN's would route correctly and the originall poster wouldn't be having this problem if theirs were routing correctly....which is why I mentioned routing in the first place.
All in all, you didn't once in either of your posts offer any help to anyone. All you did was attack me.
I've wasted all of my valuable time that I'm willing to on a person like you so don't bother replying as I won't be back to read it anyhow.
0
Unable to contact DHCP server with RIS boot disk
View products that this article applies to.
Article ID : 255952
Last Review : October 12, 2005
Revision : 3.3
This article was previously published under Q255952
SYMPTOMS
When you start a Remote Install Service (RIS) client by using the Remote Install boot disk you created with the Remote Boot Floppy Generator (Rbfg.exe), you may receive the following error message:
Error: Can't resolve IP address address of the DHCP server
Press a key to reboot system.
CAUSE
This problem can occur in either of the following circumstances:The default gateway (router), defined in the Dynamic Host Configuration Protocol (DHCP) lease (option 3) is unavailable.
-or-
The Remote Boot Floppy Generator client is ignoring the subnet mask. This may cause the client to not be able to reach the RIS server when the RIS server is on another subnet in a subnetted environment, or when the RIS server is on the same network in a supernetted environment.
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
------------------------
6-Dec-2001 21:26 2.0.0.19 299,008 Rbfg.exe
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
MORE INFORMATION
The RIS client disk always communicates through the default gateway (if the default gateway is configured) to connect to RIS. This occurs even if the RIS and DHCP server are on the same subnet that the computer is on.However, this is not true for computers that support Preboot Execution Environment (PXE) in BIOS or Boot ROM.
Only certain PCI-based network adapters are supported currently and they are listed in the Rbfg.exe utility that creates the boot disk. This utility is in the %Systemroot%\System32\Reminst folder. Click Rbfg.exe, and then click the adapter list button in the Remote Boot Disk Generator screen to see the supported adapters.
You cannot add additional network adapters to the RIS Boot disk. Microsoft adds additional network adapters over time and makes the updates in the Rbfg.exe tool available through typical distribution channels, such as the Internet, Windows Update, and future service pack or feature pack updates.
For additional information about related topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
