Set system services web-management http interface ge-0/0/0.0 Set system root-authentication encrypted-password "$1$MZSDeWoR$.e1KicC9QzerG.7NWwg8w/" I have two Firefly 12.1x47-D15.4 virtual machines with this configuration: Hi mans, can you help me with similar problem. What am I missing, or is this just not possible on the SRX? Set security zones security-zone trust interfaces lo0.0 host-inbound-traffic system-services all Set security zones security-zone trust interfaces vlan.1 host-inbound-traffic protocols ospf Set security zones security-zone trust interfaces vlan.1 host-inbound-traffic system-services all Set security policies from-zone trust to-zone trust policy trust-to-trust then permit Set security policies from-zone trust to-zone trust policy trust-to-trust match application any Set security policies from-zone trust to-zone trust policy trust-to-trust match destination-address any Set security policies from-zone trust to-zone trust policy trust-to-trust match source-address any Set protocols ospf area 0.0.0.0 interface lo0.0 passive Set protocols ospf area 0.0.0.0 interface vlan.1 priority 1 Set interfaces vlan unit 1 family inet address 10.10.10.2/24 Set interfaces vlan unit 1 description trust Set interfaces lo0 unit 0 family inet address 10.10.10.1/32 Set interfaces lo0 unit 0 description loopback Set interfaces fe-0/0/2 unit 0 family ethernet-switching vlan members vlan1 Set interfaces fe-0/0/2 unit 0 description trust Set system services dhcp propagate-settings vlan.1 I have intra zone traffic in the zone enabled and can confirm that I can reach the loopback address from a layer 3 hop, but it's not working over a layer 2. But one or the other will be needed in windows PE if servers other than the ghost server are to be accessed.I am unable to ping my loopback address from a connected host in the same zone. Or set all your mapped drives to map to the IP of the server and then the need to update the lmhost with correct name to IP info won't be needed. Scroll down in the lmhosts file and add an IP and then windows computer name of the share you are trying to map to by name simular to the following To update the lmhost to include additional server names open the boot disk creator and locate your boot package that you would like to edit. You will need to either put additional entries in from with in the boot disk creator or map your drives to the IP so that you don't need DNS and or name resolution to be functional. When you build your boot environment there is a host entry that is put in the automation/windows pe environment that is used since widnows PE doesn't do name resolution the way production windows does. Are you saying that when booted to automation and in windows PE you can't ping the server? When you say you can't ping the server from the ghost command prompt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |