Help design 6224 Vlan stack config

Similar Questions

• PowerConnect 6224 VLAN config / default gateway

  Hello

  I am new to configuring a VLAN and work with DELL going on so please forgive my ignorance.

  I joined a small agency that currently has a flat structure networking including 1 6224 linked to two 5548 one is connected to three 3548 (access), and the other is connected to a server. The 6224 connects to a proxy (default gateway), and then on the Web. All devices are currently on a 192.168.78.0 24 network with ip default gateway 192.168.80.1

  We want to segment the network using two VLAN initially. VLAN 1 user "80" and vlan 1 safety '70' and I want to clarify a few things before that I try:

  1. can you stay the ip on the network switch for vlan user ex: 192.168.80.123 or should I create a vlan separate management?

  2. I know in order for the inter - vlan, the ip of the gateway routing vlan must be on the 6224 and I then have to configure a default route to the proxy. The proxy must be on one VLAN separate or could I leave on VLAN 80 and change the ip address another que.1?

  Thanks in advance.

  I did it several times myself.  You can do almost an infinite number of ways, but it will be better to stick to certain typical networking practices.  Here is the version digest readers of what would be preferable to do so.

  1 enable routing on the switch stack.

  2. make a 80 VLAN for your network 24.80.  Assign the IP 192.168.80.1 to this VLAN.  In this way, customers will now be a ".". 1' default to the network gateway, they are on.

  3 make an another VLAN 70 for your network 24.70.  Assign the IP 192.168.70.1 to this VLAN.  This will be the default gateway for the network.  Repeat for however many VLANS / networks you want to.

  4. create a separate VLAN for his own 'bubble' network between the switch and the upstream proxy server.  (Lets call him a dummy VLAN 100 with an IP range x.x.100.x 29.  It can be just a little/29 block or something or 24 if this is confusing. Configuring the ports a few ports 'access' for this VLAN for that no marked traffic pass over this network.  Set x.x.100.1 to your Proxy Server and x.x.100.2 to your switch, then make sure you have directions on both sides about where traffic should go.

  5. save your configuration so that you have to rebuild it after a reboot.  :-)

  It will be best to set your expecations about it.  You want realistic during a weekend/maintenance window.  ARP cache and other issues can make for some downtime.  In addition, there are certainly other ways to do it, but that may be hurtful on the road when you need to increase or scale.  Two years on the road someone wondered why a default gateway is on a few eccentric IP, or there are errors of routing intermentent, etc..

  Powerconnect worldwide, just be clear what is the difference between a port of "access" to the port of 'general', and are a port 'trunk '.  Conditions may be different from the Lim to make, and if one comes to tell the world of Cisco, this may be a little different.

  Finally, don't forget to come up with a good procedure for this during your maintenance window.  Come up with a good plan documented and so well thought out, when run you it, it will be nothing more than a task in office project.

• Connect 6224 VLAN routing and management VLAN

  Happy holidays all the world-

  I read several posts here and elsewhere on the inability of the 6224 to deliver its own management interface. OK, enough, I get it. But what I don't understand is a practical solution to what seems to be a huge problem if you want to use the network to connect to the device to manage (instead of the serial console port).

  Let's say I want to have three networks A, B, and C on the 6224 and configure it to route between any combination of them. Let's call them VLANS 1, 2, and 3. Three ethernet cables will connect to three ports on the 6224. for the network A, b and C. Let's just ignore shifts and redundant connections to do this.

  The management VLAN can not be assigned to one of these networks, right? He said in the documentation, and it turns out if you try to do it on the configuration of the switch. It doesn't let you do.

  So, how do you reach the 6224 for management? Create a fourth network, VLAN 4? This seems to be the general theme of the answers to questions like that, but how do you reach this seemingly isolated network? By definition, it cannot be routed. Any computer that you normally use on A, B or C, can not reach D.

  So what then? A dedicated computer for D who cannot reach the other thing than the switch management port? What about another completely separate router (I have a Cisco ASA with some ports to spare, or a hint of irony, an another 6224!) to provide a connection between D and a networks normally used? This is crazy.

  Of course, missing me something here. I can't believe that the answer is, 'If you enable routing, the management interface is essentially unusable"but that's what it looks like, from my possibly twisted point of view. I want to have my laptop computer and any other computer, sitting on a network that can be put to rout by the 6224, and for that same laptop also be able to reach this same 6224 management interface.

  Someone please help me understand this?

  Thank you

  Chris

  PS: I have an email address. It is almost unique on the entire planet. I use it to connect to this forum. But Dell, like so many others, insists on ignoring these facts and let me create an another unique identifier while playing a game of 20 questions. That's why my remarkably stupid random username.

  Thanks again, and I hope that someone gets at least a good laugh over this.

  Vlan management can be considered as a port OOB. If the intention is that it be separated from the rest of the traffic and on its own dedicated network. However, you are not limited to manage the switch through just the interface vlan management. Each VLAN with an IP address can be used by customers in this vlan to manage the switch.

  For example, if you assign a VLAN 2 address and ip 192.168.2.1. Customers in VLAN 2 with and the 192.168.2.x subnet ip address can access 192.168.2.1 to manage the switch, while being able to communicate with clients in other VLANs.

  I hope this helps some, let me know if you need help on your config, or to specify anything.

  Thank you

• Pwerconnect 6224: vlan client computers do not receive the ip address of DHCP server on a different VLAN

  Hello

  I have a prolem routing dhcp requests between the vlan management where DHCP server resides and the other VLANs.

  I have the scenario of base with three VLANS: vlan 10 (management vlan), 20, 30, configured on a Powerconnect 6224 switch L2 mode. This switch is connected to a pfsense router. The router is configured at the package of road between the VLANS and it does it well.

  In Vlan 10, I have a configured DHCP server to use the ip addresses of all the VLANS (10, 20, 30). VLAN 10 client computers receive ip address but not others from other VLANs.

  When I put the ip address in the appropriate range of VLANs manually on computers, I ping the server and I have connectivity.

  This suggests that the problem is with the dhcp package.

  The following is the configuration of the switch:

  Configure
  database of VLAN
  VLAN 10,20,30
  VLAN 1 1 routing
  VLAN 20 2 routing
  VLAN 30 3 routing
  output
  SNTP server time.nist.gov
  clock timezone 1 minutes 0
  battery
  1 1 member
  2 2 Member
  output
  DHCP IP address
  IP address vlan 10
  name of the IP-server 172.16.10.1

  bootpdhcprelay cidridoptmode
  interface vlan 1
  Routing
  IP 172.16.1.1 255.255.255.0
  output
  interface vlan 20
  Routing
  address 172.16.20.1 IP 255.255.255.0
  output
  interface vlan 30
  Routing
  IP 172.16.30.1 255.255.255.0
  output
  level of 20fc49459a1898b923ed3ec7b3e81276 user name 'admin' password encrypted 15
  No spanning tree
  spanning tree priority 0
  l2relay DHCP
  DHCP l2relay VLANs 10, 20-30
  DHCP l2relay circuit-id VLANs 10, 20-30
  !
  interface ethernet 1/g2

  l2relay DHCP
  switchport access vlan 20
  output
  !
  interface ethernet 1/g3
  l2relay DHCP
  switchport access vlan 30
  output
  !
  interface ethernet 1/g21
  switchport access vlan 10
  output
  !
  interface ethernet 1/g22
  switchport access vlan 10
  output
  !
  interface ethernet 1/g23
  switchport access vlan 10
  output
  !

  interface ethernet 1/g24
  switchport mode trunk
  switchport trunk allowed vlan add 10,20,30
  output
  Server SNMP community EyesOfNetwork ro
  SNMP-server community public ro
  output

  I followed the instructions in the powerconnect 6224 user guide, but no progress on this issue.

  Any help will be be grateful.

  Thank you

  Zoubeir

  The DHCP server stores information that could be useful? May need to configure monitoring ports and something as wireshark to monitor DHCP packets. This would help determine where the package is stopping.

  example:

  Console (config) #monitor session 1 source interface 1/g8

  Console (config) #monitor session 1 destination interface 1/g10

  session mode 1 #monitor console (config)

  right now I don't see anything in the config of the switch that stands out. If the DHCP server is configured for option 82, then you will need to include the following command on the switch.

  Example:

  Trust l2relay console #dhcp (config-if-1/g1)

  But I don't think that's our scenario here.

• PowerConnect 6224 VLAN created, but impossible to do a ping between customers

  1 created vlan 2 with two ports 17.19 with ip 10.0.1.2/24

  2 created vlan 3 with two ports 13.15 with ip 10.0.2.2/24

  attempt to create inter routing vlan

  1 pc windows connected with ip 10.0.1.3/24 and a gateway to port 17 10.0.1.2

  2 connected windows pc with ip 10.0.2.3/24 and a gateway 10.0.2.2 to port 15

  Unable to get the Ping between two clients any help would be much appreciated, thank you in advance and running config pasted below

  coresw1 #show running-config
  ! Current configuration:
  ! Description of the system "PowerConnect 6224, 3.3.7.3, VxWorks 6.5.
  ! 3.3.7.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2-3, 5
  VLAN 2 1 routing
  VLAN 3 2 routing
  output
  location of SNMP Server "Data Center"
  contact SNMP Server «»
  hostname "coresw1".
  unicast SNTP client enable
  10.0.0.1 SNTP server
  clock timezone 5 minutes 30 zone 'IST '.
  battery
  1 1 member
  output
  IP 10.0.0.193 255.255.255.0

  by default-gateway IP 10.0.0.1
  IP - peekaygroup.com domain name
  name-server IP 10.0.0.1
  without enabling ipv6
  IP routing
  interface vlan 2
  name "LAN1.
  Routing
  10.0.1.2 IP address 255.255.255.0
  bandwidth 10000
  IP mtu 1500
  output
  interface vlan 3
  name "LAN2.
  Routing
  IP 10.0.2.2 255.255.255.0
  bandwidth 10000
  IP mtu 1500
  output
  interface vlan 5
  name "RIL Internet"

  output
  level of 8a9f2a72d65baf40b48108874cd50592 user name 'admin' password encrypted 15
  !
  interface ethernet 1/g13
  switchport access vlan 3
  output
  !
  interface ethernet 1/g15
  switchport access vlan 3
  output
  !
  interface ethernet 1/g17
  switchport access vlan 2
  output
  !
  interface ethernet 1/g19
  switchport access vlan 2
  output
  !
  interface ethernet 1/g20
  switchport access vlan 5

  output
  !
  interface ethernet 1/g22
  switchport access vlan 5
  output
  SNMP-server community public rw
  output

  This blog does a good job of showing the different firewall rules to add. You said that you have already tweaked the firewall some, I would just check the measures taken.

  http://www.sysprobs.com/enable-ping-reply-Windows-7

  If there is no antivirus software installed, try a break/disabling it to test and see if it makes a difference.

  I don't see anything on the config which would prevent pings happen.

• Help with the VLAN routing

  I'm pretty green when I just went and routing configurations please bear with me.  I'm available what I want to achieve and what I could do until now (although it may be completely wrong).

  I have an office where we run low on IP addresses for our local network, the obvious answer is to get VOIP phones on their own subnet.  So, I have a switch PC6224 I want to use to create the second subnet.

  Existing Workstation LAN = 172.22.144.0 (255.255.255.0)

  Default GW for the LAN = 172.22.144.1 for all devices on that subnet

  I would like to create an IPPhone = 172.22.145.0 (255.255.255.0) subnet

  Here's what I have "Achieved" so far:

  Currently, I can ping from a client on 172.22.145.x to the 172.22.144.12 (VLAN 3 ip interface) but cannot ping any other 172.22.144.x that is not directly connected to the 6224 switch device.  Trying to ping the network 172.22.145.x device leave a device plugged into the 172.22.144.x VLAN on the switch of packets results was sent to the default gateway for the network (172.22.144.1) who does not know what to do with them.

  Here is my config of 6224 switch operation:

  Console execution #show
  ! Current configuration:
  ! Description of the system "PowerConnect 6224, 3.3.6.4, VxWorks 6.5.
  ! 3.3.6.4 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2-3
  VLAN 2 1 routing
  VLAN 3 2 routing
  subnet of VLAN association 172.22.144.0 255.255.255.0 3
  subnet of VLAN association 172.22.145.0 255.255.255.0 2
  output
  battery
  1 1 member
  output
  IP address no
  IP routing
  IP route 0.0.0.0 0.0.0.0 172.22.144.1
  interface vlan 2
  name "IPPhone.
  Routing
  IP 172.22.145.1 255.255.255.0
  output
  interface vlan 3
  name "TWLAN".
  Routing
  IP 172.22.144.12 255.255.255.0
  output
  level of 746f7a78621059d80fdc538acc40cbf2 user name 'admin' password encrypted 15
  !
  interface ethernet 1/g3
  switchport access vlan 3
  output
  !
  interface ethernet 1/g4
  switchport access vlan 3
  output
  !
  interface ethernet 1/g5
  switchport access vlan 2
  output

  !
  interface ethernet 1/g6
  switchport access vlan 2
  output
  !
  interface ethernet 1/g7
  switchport access vlan 2
  output
  !
  interface ethernet 1/g8
  switchport access vlan 2
  output
  !
  interface ethernet 1/g9
  switchport access vlan 2
  output
  !
  interface ethernet 1/g10
  switchport access vlan 2
  output
  !

  interface ethernet 1/g11
  switchport access vlan 2
  output
  !
  interface ethernet 1/g12
  switchport access vlan 2
  output
  !
  interface ethernet 1/g13
  switchport access vlan 2
  output
  !
  interface ethernet 1/g14
  switchport access vlan 2
  output
  !
  interface ethernet 1/g15
  switchport access vlan 2
  output
  !
  interface ethernet 1/g16

  switchport access vlan 2
  output
  !
  interface ethernet 1/g17
  switchport access vlan 2
  output
  !
  interface ethernet 1/g18
  switchport access vlan 2
  output
  !
  interface ethernet 1/g19
  switchport access vlan 2
  output
  !
  interface ethernet 1/g20
  switchport access vlan 2
  output
  !
  interface ethernet 1/g21
  switchport access vlan 2

  output
  !
  interface ethernet 1/g22
  switchport access vlan 2
  output
  !
  interface ethernet 1/g23
  switchport access vlan 2
  output
  !
  interface ethernet 1/g24
  switchport access vlan 2
  output
  output

  Console #.

  Any help would be greatly appreciated.

  Thanks, Grant

  What port connects to 172.22.144.1 the jump according to the internet?

  What should happen is we need a VLAN 'remote' separate just for the connection between the 6224 and your 172.22.144.1 jump following the internet device.

  If 172.22.144.1 remains the same, then you must create another local network VIRTUAL to "TWLAN".  Eventually, VLAN 4 with a range of ip addresses of 172.22.146.1 - 254 255.255.255.0.  Where the VLAN 4 interface has an IP address defined as 172.22.146.1.  Once that all connected devices again VLAN 4 that were in the VLAN 3 need to change there IPs and gateway 172.22.146.1

  So the only port that has configuration of VLAN 3 is the connection to 172.22.144.1 port next to the internet break.  The IP address defined on the interface VLAN 3 should be in the same subnet as 172.22.144.1 range.

  Here is a diagram that can help you to see the whole upward.  VLAN 100 in the diagram represent VLAN 3 in your case.  Switch 2 would represent your device from the internet of next hop.

  

• PowerConnect 6224 VLAN Routing, unable to connect out of VLAN but able to connect by entering.

  To set up a new VIRTUAL local network to separate the common workstation network and obtain new DHCP scope, I had a few questions and found advice in the post of http://en.community.dell.com/support-forums/network-switches/f/866/t/19370806.aspx?PageIndex=3 but now I find that my traffic is not going through properly so I'm starting a new thread to get help shows all of working.

  Current primary network 192.168.1.0/24 (192.168.1.200 DHCP server). Adding new perspectives to the server for 192.168.3.0/24 active.

  Gateway default 192.168.1.0/24 is 192.168.1.254 (Cisco ASA, it was set up like that when I arrived and no room to insert the dedicated router). Adding route to 192.168.3.0/24 > 192.168.1.253 (PC6224 and VLAN 1 management interface). I also added exceptions NAT asa for the 192.168.3.0 network.

  I was still having some problems of scathing to the 192.168.3.0 network from the DHCP server and I added a static route on the server for this network, bypassing the ASA for routing to the switch.

  From the DHCP server, I am able to ping 192.168.1.253, 192.168.3.254 but not a laptop that runs Windows XP configured with 192.168.3.1 address connected to port 22 of the 6224.

  The XP laptop, I am able to ping 192.168.3.254 but not 192.168.1.253 or any other address in the 192.168.1.0 network.

  The switch CLI, I am able to ping on both networks destinations.

  Here is my config of switch. I have it set to scrape factory reset so there is no buried old ACL inside.

  console #show run
  ! Current configuration:
  ! Description of the system «PowerConnect 6224P, 3.3.5.5, VxWorks 6.5»
  ! 3.3.5.5 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2
  VLAN 2 1 routing
  output

  IP 192.168.1.253 255.255.255.0
  by default-gateway IP 192.168.1.254
  IP - domain.local domain name
  name-server IP 192.168.1.11
  name-server IP 192.168.1.200
  IP routing
  IP helper-address 192.168.1.200 dhcp

  interface vlan 2
  name 'common '.
  Routing
  192.168.3.254 IP address 255.255.255.0
  IP netdirbcast
  bandwidth 10000
  business assistance-address IP 192.168.1.11
  field of IP helper-address 192.168.1.200
  IP helper-address 192.168.1.200 dhcp
  IP mtu 1500
  output

  l2relay DHCP
  DHCP l2relay vlan 2
  !
  interface ethernet 1/g21
  switchport access vlan 2
  output
  !
  interface ethernet 1/g22
  switchport access vlan 2
  output
  !
  interface ethernet 1/g23
  switchport access vlan 2
  output
  !
  interface ethernet 1/g24
  switchport access vlan 2
  output

  
  

• PowerConnect 6224 VLAN down?

  I just created a new 51 VLAN on my core 6224 switch.

  I have assigned an IP address, configured routing, he attributed to multiple trunks, and I attributed to a port of access to him as well. VLAN 8, I'll set up, have had no problems with others.

  Here's what I see when I show ip interface vlan 51

  PHX_Core_Switch #show ip interface vlan 51

  State of the Routing Interface... Down
  Primary IP address... 10.200.51.1/255.255.255.0
  Routing mode... Enable
  Administrative mode... Enable
  NET before realized emissions... Disable
  Proxy ARP...................................... Enable
  Local Proxy ARP... Disable
  Statement of assets... Inactive
  MAC address... 5C26.0AF9.9E8C
  Type of encapsulation... Ethernet
  IP MTU......................................... 1500
  Bandwidth...................................... 10000 Kbps
  Destination unreachable... Activated
  ICMP redirects... Activated

  Why the interface is down? Help? I'm going nuts here!

  Just got off the phone with Dell technical support. They could not understand either, we have created a new 60 VLANS and it came fine and worked exactly as planned.

  Maybe it's a bug in the Firmware 3.3.3.3.

• Help create a VLAN for domestic use.

  I use Cisco SG300 and SG200 series switch. I put my home network as attach photo.

  I want to configure VLANS with these condition

  1. all ports can connect to the internet via ADSL router.

  2.VLAN10 (home alarm and IP camera) can access residential, access point and PC file server to connect

  3. each port can connect to PC file server

  I am new to network and do not try to install myself and understand not static route.

  Thank you.

  Diego

  [email protected] / * /.

  Hi paylo,.

  Are you sure you want to do this on the switch instead of the router? Will you use static IP addresses for VLANs, or do you want your router to deliver DHCP?

  To continue using the switch for routing inter - vlan, make sure the SG300 is mode layer 3.

  1. If you are currently in mode layer 2, open a CLI connection and issue command:

  router adjustment system mode

  Take note that this will delete your current config and the switch will reboot.

  2. create the VLANS on your switch under management VLAN-> create a vlan

  3. go to IP Configuration-> interface ipv4 and assign each vlan a static IP address for the switch in the subnet for the new LAN virtual

  4. vlan management-> the Interface settings. I leave all ports as trunk ports, or change the Trunk ports, if you have already changed their.

  5. vlan Management-> Port VLAN membership. Assign your VLAN ports appropriate.

  6. when everything is all connected, you should be able to see the switch of the static routes for you already created under static Configuration of the IP-> IPV4 routes. Make sure all your subnets are there and demonstrate local range type

  7. you may need to add a route for example 0.0.0.0 with the next hop is your router

  At this point, you should be up and running, with all them VLAN connected to each other and to the internet.

  If you want to restrict access between them VLAN, you will need to create access control lists.

  You must first create an ACL (Access control-> ACL based IPV4) and give it a name. then move on IPV4 based ACE where you put real access control rules.

  This is a sample set of rules that I did, it will block all access between two subnets (each vlan that you created above should be its own subnet) and allow certain traffic like 3389 - remote desktop, etc. You will need to customize according to your needs and IP subnet. So for ex, to enable the Xbox access the file server, rather than all - everything, you put the xbox or IPs specific subnet as the source, the file server as destination, and the ports as source ports. Don't forget to do the reverse of the rule as well.

  

  Then go to-> links ACL access control and bind the list control access to ports there.

  Hope that helps, good luck with your game to the top.

  Best,

  David

  Don't forget to note useful messages and identify the right answers.

• Help design a trigger for an analog voltage signal

  Hello guys,.

  I have a real problem one design trigger for an application, what I do is to power a motor and measure consumption current and voltage during each operation. What I would do is to begin to acquire the signal once the voltage rises to a certain value and finish when it falls to a certain value. The equipment I use is a cDAQ 9178 with a NI9205 and 9221 modules.

  Any help / samples / detailed explanation will be really appreciated. I have no idea on how to work with the outbreak of the vi in Labview.

  Concerning

  SergeArmz

  Finally after a lot of research, tests and many developments, this is a VI that I developed and who is able to do what I was looking for. Thanks to the guys who helped me out to understand how solve my problem.

  For all those who may have the same problem I had, I enclose the VI.

  And of course if you can improve on what I did will be great, I think it's the purpose of this forum

  See you soon!

  SergeArmz

• Help with the VLAN on SG200-18 and two switches SG200-08

  Hello world. My apologies, but I'm only average at best with my CISCO skills. I have simple installation running some network devices connected via 3 CISCO switches. It is small office and two bedrooms - one with the servers and the other with the printer and pc. Each room has 8 ports SG200-08 pass.

  Router / firewall is Sonicwall TZ215 and manages the internal routing between VIRTUAL networks. Each SG200-08 was directly connected to TZ215 (no SG200-18 again) and VLAN worked perfectly. Please see diagram below...

  Problems started when I added in the Center SG200-18 more to handle additional devices. Everything that I'm doing wrong, but I can't do VLAN longer works. Something I won't set up correctly in SG200-18.

  Please help me to Setup VLAN here - tag, unidentified, PVID, trunk... I am completely lost and already had to reset SG200-18 twice.

  My work without port switch 18 Setup was like that.

  SG200-08 (1)
  G1 1 trunk 1U, 100 t
  G2 1 trunk 1U
  G3 1 trunk 1U
  G4 1 trunk 1U
  G5 1 trunk 1U
  G6 1 trunk 1U SERVER3
  G7 trunk 100 100U SERVER1
  G8 trunk 100 100U Server2

  SG200-08 (2)
  G1 1 trunk 1U, 50 t, 200 t
  G2 1 trunk 1U
  G3 1 trunk 1U
  G4 1 trunk 1U PC1A
  G5 1 trunk 1U PC1B
  G6 trunk 50 50U PC2A
  Trunk PC2B 50 50U G7
  NETWORK PRINTER for the 200 trunk 200U G8

  Thank you in advance.

  VLAN.jpg

  

  Hello

  Oh I'm sorry. I understand that you have 3xSG200-08 and 2 of them with the same configuration :-). So no need to use this port for now.

  Kind regards

  Aleksandra

• Help with error in web.config for default Web Site on IIS 7.5 Windows 2008 R2

  I get the following error message when I want to run the default Web site on my browser to IIS Manager platform. I am to administer a new Server Windows server 2008 R2. I'm not IT literate appreciate the step by step help to get my default Web Site running and build a web site:

  Summary HTTP error 500.19 - internal error the requested page server is inaccessible because the configuration data of the page are not valid.
  Detailed error Information Module IIS Web Core Notification unknown manager not yet determined the error Configuration file Code 0x8007000d Config "\\?\C:\inetpub\wwwroot\web.config" does contain not a tag root \\?\C:\inetpub\wwwroot\web.config requested URL http://localhost Config file: 80 / physical logon method path not yet determined not yet determined user logon failed request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles Config Source 1 : 2 :

  Hello SemeNdzana,

  Microsoft Communities is consumer related questions about Windows 8, Windows 7, Windows Vista and Windows XP. Your question would be better asked in the IIS forum.
  Click here for a link to the IIS support forums application.

  They will be able to solve your problem.

  Thank you

  Marilyn

• I need someone to the split screen with me to help design a navigation scrolling Parallax!

  I need to design a navigation and footer page similar to www.astonmerrygold.com tonight and need help!

  You can use the full rectangle with menu as well as rollover effects and apply the scroll on the menu. To the same rectangle footer can be used with content grouped for social icons and pin them.

  Thank you

  Sanjit

• Need help: design problem

  Hi refugees,

  I'm new to OFA,

  I am facing problem with page design I have to display the list of options on the left and based on the selection, see the box above right more like

  in the list of EBS responsibilities and the corrosponding to the menu at the top right of most...

  I tried to understand the homepage, but I did not understand... Please... help me on this... What are the areas I have to choose...?

  Kind regards

  Jaya

  What is the error you get?

  Sushant-

• Converter Helper IP and VLAN

  I'm trying to convert a RHEL 5.0 in VM machine. In the IP Helper configuration, there is no place to define what VLAN support network should be in.

  The physical machine is the VLAN 20, the new virtual machine will be VLAN 30. The network is function tag VLAN only and we do not have a DHCP server on the network.

  Someone has any idea how to run it?

  Thank you

  The HelperVM works in the target VM, so it has the same network (VLAN 30 in your case).  The User Guide has a label explaining this as well.

  Since you have no service DHCP VLAN 30 you can configure a static IP address for the HelperVM.  It is an option in the 3rd page of the Converter Wizard.

  Remember that the HelperVM come into contact with the source via SSH, so you must have your routing and firewall configured for this purpose.